Controller or firmware
The commonest serious fault by a distance. Gone from the BIOS, blank model string, or an impossible capacity like 1MB or 8MB — while the NAND behind it still holds everything.
Most likely
Counterintuitive, and it follows from how TRIM works: a drive that has stopped responding cannot erase anything, so failure preserves data that continued health would have destroyed. Here is what actually fails, and what can be read back.
TRIM genuinely erases the blocks behind deleted files, and quickly. It also cannot run on a drive that has stopped answering — so outright failure preserves exactly what routine deletion destroys.
The single most important difference between an SSD and a hard drive, and it changes how you should treat both.
A hard drive tells you it is dying. Reallocated sectors climb, transfers stall, something starts clicking. There is usually a period — often weeks — where the drive is deteriorating and still readable, and that window is where most of the value in monitoring sits.
SSDs give you almost none of that. SMART on solid-state storage reports flash wear reasonably well: percentage of rated life used, total bytes written, spare blocks remaining. What it barely reports is the health of the controller — and the controller is what fails catastrophically in most serious cases.
So a drive can show four percent wear and ninety-six percent life remaining on Monday, and be undetectable on Tuesday, with nothing in between. The practical consequence is that “I will back it up when it starts playing up” does not work on an SSD, because there is no playing up.
They present almost identically — the drive vanishes — and the diagnostic separates them.
The commonest serious fault by a distance. Gone from the BIOS, blank model string, or an impossible capacity like 1MB or 8MB — while the NAND behind it still holds everything.
The controller maintains mapping tables constantly. An abrupt cut mid-write leaves them inconsistent, and the drive refuses to present itself rather than serve data it cannot vouch for.
NVMe drives run hot, especially in thin laptops, M.2 slots under a graphics card and sealed enclosures. Often intermittent first — working cold, vanishing warm — before it stops entirely.
Real NAND degradation. Considerably less common than people assume, and the case where prospects are weakest.
Either can close a job before it starts, which is why they are established at the free diagnostic.
TRIM. When you delete a file on an SSD, the operating system tells the drive those blocks are no longer needed, and the controller erases them physically in the background. That erasure is genuine. Nothing retrieves it — not software, not a laboratory, not equipment costing six figures. Deleted files on a healthy, powered SSD are usually gone within minutes.
Which produces a counterintuitive result: a dead SSD is often a better prospect than a working one. A drive that has stopped responding cannot run TRIM, so failure preserves data that continued health would have destroyed.
Encryption. Many SSDs encrypt by default — Class 0, TCG Opal, Samsung’s portable T-series — frequently with BitLocker layered on top. Without the password or recovery key, healthy NAND yields nothing usable. Where the key is genuinely gone we can attempt password recovery, which succeeds on weak or partly-remembered passwords and fails against a long random passphrase. We will say which you are likely dealing with.
And why chip-off is the last resort rather than the first.
Manufacturers build a diagnostic mode into their controllers that bypasses the normal interface. Reached that way, the service area can be read directly — including the translation tables mapping logical addresses to physical flash locations. Those tables are the whole job: without them the NAND is undifferentiated data, because wear levelling means the physical layout bears no relation to the logical one.
Where the controller cannot be revived at all, the flash can sometimes be read directly — de-interleaved across planes, ECC-corrected and unscrambled to that controller’s arrangement. That is slower, riskier, and on many modern drives it returns data the controller had encrypted, so a chip-off can produce a perfect copy of something nobody can read.
Which is why reviving the controller is always attempted first. If a firm proposes chip-off early on a drive whose controller might be recoverable, it is fair to ask why. SSD and NVMe recovery in Manchester is from £300 +VAT after a free 48-hour diagnostic, with a 50% deposit for controller-level work.
Frequently, yes. The commonest serious fault is the controller rather than the flash, so the NAND still holds your data behind a layer that stopped answering. It can often be reached in the manufacturer’s diagnostic mode and imaged read-only.
Because SMART reports flash wear well and controller health barely at all — and the controller is what fails catastrophically. A drive can show 96% life remaining and be undetectable the next day, with nothing in between.
Usually not from a working drive. TRIM tells the controller to erase those blocks and it does so physically within minutes. Nothing retrieves that — which is why a dead SSD is often a better prospect than a healthy one, since a failed drive cannot run TRIM.
It can end it. Many SSDs encrypt by default, often with BitLocker on top, so without the password or recovery key healthy flash yields nothing usable. Where the key is lost we can attempt password recovery — effective on weak passwords, not on long random ones.
That the controller is in a fallback state, not that the flash has failed. No drive is manufactured at that size — it is a placeholder presented when the controller cannot load its firmware or mapping tables. The data behind it is usually intact.
It is the last resort. Reviving the controller is preferred because it performs its own decryption and address translation. Chip-off is slower, riskier, and on many drives returns encrypted data — a perfect copy of something unreadable.