Access / detection problemProfessional help recommended

Drive Shows the Wrong Capacity

A disk reporting 0 B, a few megabytes, or a capacity far smaller than expected is an addressing or translation symptom—not evidence that the missing data area was erased.

First decision

Before attempting repair, determine whether the storage source is identified consistently, reports the expected capacity and can be read without severe errors, stalls or disconnects. If not, treat acquisition as the first problem.

What wrong capacity can mean

Capacity is reported through several layers: the device firmware, controller, USB/SATA/NVMe bridge, storage enclosure and operating system. A 2 TB drive suddenly appearing as 3.86 GB or 0 B may be exposing a firmware or controller failure, an incomplete device state, a bridge limitation, or an unusual configuration. A normal physical capacity with only a small partition visible is a different problem and belongs closer to partition recovery.

What to check safely

Compare the model number and physical capacity reported by BIOS/UEFI, the storage controller and the operating system. Distinguish “disk capacity” from “volume size”: a 4 TB disk with a 100 MB visible partition is not the same as a disk whose device itself reports 100 MB. Note any recent enclosure change, USB adapter, controller replacement, firmware event or RAID migration. Save screenshots rather than repeatedly probing an unstable device.

Why the distinction matters

File-system recovery software works inside the address space the device exposes. If a controller reports only a tiny fraction of the real media, a scan cannot magically read LBAs that are not addressable. Conversely, if the full disk capacity is correct and only partition boundaries are wrong, the underlying sectors may be completely accessible and the problem may be logical.

Recovery paths

With correct physical capacity and stable reads, image the source and investigate partition/file-system structures. With incorrect device-level capacity, first preserve the original hardware context and identify whether the limitation comes from the drive, enclosure or controller. HDD firmware faults and SSD translation-layer failures can require specialist access methods. Avoid commands that alter HPA/DCO, firmware, namespace or RAID metadata unless the exact cause and original configuration are known.

What not to infer

Wrong capacity does not by itself tell you that platters, NAND or files are damaged. It also does not justify repartitioning to “restore” the missing space. Creating a new partition table only describes a new logical layout inside whatever address space is currently visible; it does not repair the reason the device reports the wrong size.

Preserve the source

Do not save recovered files, install software, create partitions, format, initialize or run write-capable repair tools on the only copy of the affected data. When practical, work from a verified image or another preserved copy.

This page describes the general situation, not a guaranteed fix for a specific case. If the source is unstable or the data is irreplaceable, consider a professional evaluation before further attempts.