Why an SSD Reports 0 Bytes
When an SSD reports 0 bytes in the operating system's disk management tool, it means the controller is not presenting any storage capacity to the host. The drive may appear in the BIOS or device manager with its correct model number, but it shows 0 bytes or no usable partitions. This symptom has three distinct causes at the hardware/firmware level, each requiring a different diagnostic and recovery approach.
Three Causes of the 0-Byte Symptom
| Cause | What Happened | BIOS Behavior | Recovery Path |
|---|---|---|---|
| Controller failure | The controller chip cannot execute firmware due to hardware damage | Drive may not appear at all, or appears with wrong/generic model name | Controller repair or replacement (with encryption key considerations) |
| FTL corruption | The mapping table between logical addresses and physical NAND is damaged | Drive appears with correct model name but shows 0 capacity | FTL rebuild via vendor-specific diagnostic tools (PC-3000 SSD) |
| NAND degradation | NAND cells have exceeded endurance or developed widespread read errors | Drive may initialize slowly or intermittently; capacity may fluctuate | Raw NAND reads with error correction; partial recovery possible |
Controller Failure
The SSD controller is a system-on-chip that runs the drive's firmware, manages the NAND interface, handles encryption, and communicates with the host over SATA or NVMe. If the controller sustains damage (from power surges, thermal failure, or silicon defects), it cannot execute the firmware needed to present the drive's capacity to the host.
Controller failures manifest differently depending on the failure mode. A complete failure means the drive does not respond to the host at all. A partial failure may allow the drive to appear in the BIOS with a generic or garbled model name (because the controller's ROM is accessible but the firmware cannot fully initialize). Some controllers enter a "safe mode" that identifies the drive but blocks data access until the firmware issue is resolved.
Recovery from a controller failure depends on the encryption status. If the controller uses always-on encryption (Samsung, Silicon Motion, Marvell controllers), the media encryption key (MEK) is stored in the controller silicon. Replacing the controller loses the key unless it can be transferred. PC-3000 SSD supports key extraction from certain controller families before replacement.
FTL Corruption
FTL corruption is the most common cause of the 0-byte symptom, particularly after power loss. The Flash Translation Layer maintains the mapping table between logical block addresses and physical NAND locations. This table is cached in DRAM and periodically flushed to NAND. If power is lost during a flush, the mapping table in NAND may be incomplete or inconsistent.
When the controller boots and finds a corrupted FTL, it cannot reconstruct the logical view of the drive's storage. The controller reports 0 capacity because it has no valid mapping to present. The data is still in the NAND cells in the physical pages where it was last written; only the index to find it is damaged.
Some controllers attempt automatic FTL repair on boot. If this succeeds, the drive initializes normally (possibly with some data loss from the incomplete flush). If auto-repair fails, the controller enters a diagnostic mode. PC-3000 SSD can access this mode and manually rebuild the FTL by scanning NAND pages for embedded metadata (LBA stamps and sequence numbers).
NAND Degradation
NAND cells wear out after a finite number of program/erase cycles. As cells degrade, the bit error rate increases. When the errors exceed the ECC engine's correction capability, blocks become unreadable. If enough metadata blocks (those storing the FTL mapping table, bad block tables, or controller configuration) become unreadable, the drive cannot initialize.
NAND degradation differs from FTL corruption in that the data itself may be damaged, not just the map to find it. Worn cells may have lost charge, flipping bits in the stored data. Recovery from NAND degradation involves reading raw NAND pages and applying maximum-strength ECC decoding, sometimes with adjusted read reference voltages (voltage threshold shifting) to optimize bit accuracy on worn cells.
Software cannot distinguish these three causes.
Consumer recovery software and operating system disk management tools see the same symptom (0 bytes, no accessible partition) for all three causes. They cannot differentiate between a controller that is not responding, an FTL that is corrupted, and NAND that is degraded. Diagnosis requires hardware-level tools that communicate with the controller through vendor-specific diagnostic commands.
How Lab-Level Diagnosis Distinguishes the Causes
- Physical inspection. Check for burned components, damaged solder joints, or swollen capacitors on the PCB. Visible damage points to controller or power delivery failure.
- BIOS/UEFI detection. If the drive appears with its correct model name and serial number, the controller is functional and the issue is likely FTL corruption. If it appears with a generic name or does not appear at all, the controller is suspect.
- Vendor-specific diagnostic mode. PC-3000 SSD sends manufacturer-specific commands to query the controller's internal state: firmware version, FTL status, SMART data, NAND health counters. This reveals whether the FTL loaded, how many bad blocks exist, and whether the NAND is within endurance limits.
- Raw NAND sampling. Reading a small sample of NAND pages and checking the bit error rate indicates NAND health. A BER within ECC correction limits suggests FTL corruption (data intact, map damaged). A BER exceeding ECC limits suggests NAND degradation (data itself compromised).
Frequently Asked Questions
Can software fix an SSD showing 0 bytes?
Consumer recovery software cannot fix this issue because it operates above the firmware level. The drive is not presenting storage capacity to the OS, so there is no filesystem to scan. The cause is in the controller firmware, FTL mapping, or NAND hardware. Diagnosis requires vendor-specific diagnostic commands that consumer software does not support.
Is my data gone if my SSD shows 0 bytes?
Not necessarily. The NAND cells still contain whatever was last written. If the cause is FTL corruption (the most common scenario after power loss), the data is intact and recoverable by rebuilding the mapping table. If the cause is NAND degradation, some blocks may have uncorrectable errors.
If you are experiencing this issue, learn about our SSD recovery service.