Data Recovery Case File · Solid State & Flash · A True Rule, Wrong Device

"Even the Deadest Drives Are Recognised" — Except These

Her enquiry contained a helpful friend's observation that is entirely correct about one kind of drive and misleading about the one she has. A laptop that stopped working: "a family friend who worked in IT discovered that the SSD had packed in. When he plugged the SSD into his laptop, it couldn't identify it. He said this was extremely unusual, as even the deadest of hard drives are normally recognised." A specialist shop later reported the same and told her it was "basically knackered". Her friend's rule is a good one and he applied it faithfully. It is also a rule about hard drives — and on solid-state storage the opposite is true. Complete non-recognition is not unusual at all. It is the characteristic way an SSD fails.

The decode: why the rule holds for hard drives and fails for SSDs

Why he is right about hard drives: a mechanical drive has separable parts. Its circuit board can be working perfectly while its heads have failed, its motor can spin while its surfaces are unreadable, and its electronics will usually complete the introduction to a computer even when the mechanism behind them is in serious trouble. That is why a badly failed hard drive still typically appears — often reporting its model and capacity — before failing at everything else. His expectation is well founded and reflects real experience.

Why solid-state drives behave differently: an SSD has no such separation. The controller is not merely the doorway — it is the entire management layer, holding the address mapping, the wear-levelling state and, on most modern drives, the encryption. When the controller fails or enters a fault state, the drive cannot present anything: not a capacity, not a model, nothing. So an SSD that is completely invisible is not exhibiting an exotic fault; it is exhibiting the normal one. The very symptom that alarmed her friend is the expected outcome.

What that means for the shop's verdict: "basically knackered" is an honest description of where their tools ended, and it is what a general repair shop can reasonably conclude — because at that level there is genuinely nothing further to do with a drive nothing can see. It is not, however, a statement about whether the data is recoverable, because the route past this fault is not one a repair shop has. Two people reaching the same wall using the same class of equipment is not two independent verdicts.

What the actual route is: vendor-specific technological and safe modes — manufacturer-defined states that allow a drive whose normal start-up fails to be addressed anyway, its firmware area assessed and repaired, and the drive imaged. That works often enough to be well worth attempting. The honest counterpart: where the failure is in the memory itself rather than the controller's firmware state, reading the packages directly is not the dependable fallback it is on cards and sticks, because the mapping and often the keys live in the controller. So this is genuinely attemptable and genuinely not guaranteed, and both halves should be said before any money changes hands.

On the bench

Access was attempted through the PC-3000 portfolio's SSD support rather than by connecting the drive to another computer, since two people had already established what that produces. The controller was addressed in its vendor technological modes, its state examined, and the firmware area assessed for the corruption that typically prevents a drive completing start-up. The honest alternative had been set out in writing beforehand, so either result arrived as an expectation rather than a disappointment. Where access was restored, the drive was imaged immediately and completely, and the contents verified by opening before delivery.

The outcome

The controller addressed in vendor modes, access restored and the contents imaged and verified. 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, for anyone told their invisible SSD is unusual: that rule is true of hard drives, whose electronics usually complete the introduction even when the mechanism has failed — but an SSD's controller is the management layer, holding the address mapping and often the encryption, so when it fails the drive presents nothing at all; complete invisibility is therefore the characteristic solid-state failure rather than an exotic one; and two assessments reaching the same wall with the same class of tools is one verdict rather than two. The route past it is vendor-mode access, which a repair shop does not have.

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.