Data Recovery Case File · Solid State & Flash · Nothing Preceded It
It Did Not Deteriorate, It Stopped
His enquiry describes a failure with no lead-up at all. A 2TB solid-state drive holding family photographs: "the drive has randomly stopped working. Now when the laptop is switched on it states no bootable device." The absence of any warning is not incidental — it is how solid-state drives usually fail, and it is why the advice that works for mechanical drives does not transfer.
| Media | 2TB solid-state drive — abrupt cessation of function without preceding symptoms; host firmware reporting no bootable device; approximately 1.6TB of personal content held |
| Reported situation | Solid-state drive in normal service · no slowness, errors or warnings reported beforehand · drive ceasing to function without notice · firmware reporting no bootable device · approximately 1.6TB of family photographic content required |
| Fault class | Controller-level failure without precursor — abrupt loss characteristic of solid-state media; memory unaffected by the controller ceasing to respond |
| Equipment used | Drive powered as little as possible to limit controller housekeeping · enumeration state read under strict timeouts · vendor technological modes attempted with the drive's own mapping preserved · chip-level read past the controller where the controller could not be brought up |
The decode: why mechanical drives warn and solid-state ones do not
How a mechanical drive fails: gradually and audibly. Regions become slow before they become unreadable, the drive retries, transfers take longer, the machine hesitates, and there is frequently a noise. Anybody paying attention gets weeks of notice, which is why so much of this archive is about reading early signs.
How a solid-state drive fails: at the controller, and abruptly. There is no mechanism to become noisy, nothing to slow down mechanically, and no gradual degradation of access — the component that presents the storage either responds or does not, and the transition between those two states is instantaneous.
Why that matters for expectations: people who have owned mechanical drives assume a failing device gives notice. On solid-state media, working perfectly the day before is entirely normal and tells you nothing about the day after. The absence of warning is not something he missed.
Why the memory is very likely intact: a controller that has stopped responding has not erased anything. The memory is a separate component, holding charge exactly as it did — and the failure is in the part that speaks for it rather than the part that stores.
What "no bootable device" tells us specifically: the firmware enumerated storage and either found nothing or found something that could not be read as bootable. Which of those it was matters, and it is established by whether the drive appears in the firmware's own device list at all.
Why time works against him in a way it would not on a mechanical drive: a solid-state drive that can be brought up at all runs background housekeeping whenever powered, and blocks marked for erasure are processed. Powering it repeatedly to test is not free here, which inverts the usual advice about mechanical drives where the cost is mechanical rather than logical.
What the routes are: the controller is addressed in its vendor technological modes where it can be brought up at all, with the drive's own mapping preserved. Where it cannot, the memory is read at chip level past the controller and the translation layer reconstructed in software.
What this means for anybody relying on solid-state storage: the early-warning strategy does not exist. A second copy is the only warning system available.
On the bench
The drive was powered as little as possible to limit controller housekeeping, background block processing continuing whenever a solid-state device runs. Enumeration state was read under strict timeouts — mechanical failure being gradual and audible while solid-state failure occurs at the controller and is instantaneous, with no mechanism to degrade progressively. Vendor technological modes were attempted with the drive's own mapping preserved, and chip-level reading applied past the controller where it could not be brought up.
The outcome
Powered time minimised, enumeration read under strict timeouts, and the memory recovered past the controller where required. Free assessment, one fixed written figure including VAT; where a chip has to be removed, 50% of parts and labour is payable upfront with the balance only on success — otherwise no recovery, no fee. The decode: there was no warning because solid-state drives do not give one. Mechanical drives slow down and make noises; a controller either responds or it does not, and the change between those is instantaneous. You missed nothing.
Solid-state drive that stopped without warning
Stop powering it, and don't reproach yourself for missing signs that don't exist. Mechanical drives fail gradually — regions slow before they fail, transfers drag, and there's usually a noise, which is why so much advice is about reading early symptoms. Solid-state drives fail at the controller, and there's no mechanism to become noisy or to degrade progressively: the component that presents your storage either answers or it doesn't. Working perfectly yesterday tells you nothing. Time also matters more here than on a mechanical drive, because a solid-state device processes background block erasure whenever it's powered. The memory itself is almost certainly untouched.
Leave it unpowered — call Oxford Data Recovery on 01865 593000; powered time minimised, enumeration read under strict timeouts, memory read at chip level past the controller where needed.
Request a quote online →
Our case files are drawn from genuine enquiries received by our laboratory over the past ten years, anonymised to protect client confidentiality. Each one describes the diagnostic and recovery procedure our engineers apply to that fault, using the equipment listed.