An Asus laptop that stopped booting, with the SSD appearing in the BIOS as a one-megabyte device. Alarming to see, and far better news than it looks — because no drive is 1MB, and the number is the controller telling you something specific.
This is a scenario, not a case study. It describes a failure pattern we handle regularly and how it is approached, written from the technical work rather than from one client's job. Our documented case files are here.
An SSD that worked yesterday now appears in the BIOS or Disk Management as a device of 1 MB, 2 MB or 8 MB. It is detected, it responds, and it reports a capacity it plainly does not have.
This is not a random misreading. Several controller families deliberately present a tiny capacity when they detect that their own internal state is inconsistent — a corrupt translation table, a failed self-test, firmware that will not load cleanly.
The reasoning is protective. Rather than presenting a full-size device and returning wrong data, the controller presents something obviously invalid, which prevents an operating system writing over user data it can no longer correctly address.
So the drive is working exactly as designed. It has decided it cannot safely present your data, and it is saying so in the only way it can.
An SSD does not store data where the operating system thinks it does. A translation layer maps logical addresses to physical NAND blocks, and that map is constantly rewritten as wear levelling moves data around. It is held in the controller's own metadata area.
When that map is damaged, the flash beneath it is untouched. Every byte is still present in a physical block somewhere; what has been lost is the index describing which block belongs where.
Recovery means either repairing the translation layer through the manufacturer's vendor mode, or reading the NAND directly and reconstructing the mapping externally — reversing the wear levelling, interleaving and scrambling the controller was applying.
Do not run a firmware update or a secure erase. Both are offered as fixes for this symptom and both write to the drive. A secure erase in particular does exactly what it says, and on a drive in safe mode it is the one action that makes the data genuinely unrecoverable.
Various sequences of powering the drive for set intervals circulate online. Some controllers do clear safe mode this way. Others use the opportunity to run housekeeping that discards the damaged map.
Flashing firmware to a controller that cannot load its own metadata can complete partially, leaving the drive in a worse condition than safe mode.
Presented by several vendor utilities as the remedy for a drive reporting the wrong size. It is, and it also erases everything.