Data Recovery Case File · Solid State & Flash · No Warning at All
SSD Not Detected in BIOS: No Warning at All
His enquiry was thorough, self-aware and asked the question directly. A SanDisk Ultra SATA SSD of around 1TB that "completely stopped working out of the blue. Previously hadn't shown issues in a disk health tool. Undetectable in BIOS, didn't detect when swapped to two different SATA and power positions — I swapped out my optical drive and then another storage drive for it, using the cables and motherboard connections that worked for them — or in a USB cradle." Then, disarmingly: "honestly? It isn't super important, but it has an extremely complicated game modding installation on it, literally hundreds of hours of work that would be a huge pain to recreate. Am I toast, or is it possible to recover the drive contents?" Three things owed to him: why his health tool gave no warning, why his elimination is the best kind, and an honest answer about what SSD recovery involves — which is a genuinely different proposition from a hard drive.
| Media | SanDisk Ultra SATA solid-state drive, approximately 1TB — sudden total failure; undetectable in BIOS across two SATA and power positions and in a USB cradle; no prior warning indicators |
| Reported situation | Abrupt failure during normal use · health monitoring had shown no issues previously · thorough elimination across ports, cables and an external cradle · extensive configuration data at stake |
| Fault class | SSD controller or firmware failure — no enumeration; NAND typically intact but reachable only through controller-level access on this class of device |
| Equipment used | Vendor technological and safe-mode access attempts (PC-3000 portfolio, SSD support) · controller state and firmware area assessment · imaging on restored access · honest limits stated where controller-level access is unavailable |
The decode: why no warning, what his testing proved, and the honest SSD picture
Why the health tool showed nothing: a fair question and an important one. Health monitoring on an SSD reports the drive's own self-assessment, and what it principally tracks is NAND wear — how much of the memory's write endurance has been consumed, how many spare blocks remain. Those are genuinely useful for predicting the slow end of a drive's life. What they do not monitor is the health of the controller — the processor that manages everything — or the integrity of the firmware and mapping tables it depends on. When those fail, they fail abruptly and without any preceding indicator, which is why the overwhelming majority of SSD deaths look exactly like his: perfect one minute, absent the next, with a clean bill of health right up to the moment. Hard drives usually degrade audibly and gradually; SSDs tend to stop.
What his elimination proved: unusually complete. Two different SATA ports with power connections known to work for other devices removes the motherboard ports, the cables and the power supply rails. A USB cradle removes the SATA subsystem entirely and tests the drive through a completely independent path. Absence from the BIOS across all of that is as definitive as home testing gets — the drive is not answering the most basic identification request on any interface, and everything external is acquitted. No further testing will add anything.
The honest SSD picture: here is where he deserves straight talk rather than reassurance. On a memory card or a USB stick, a dead controller is routinely bypassed by reading the memory directly at chip level. On a modern SSD that fallback is far harder and often unavailable, for concrete reasons: the data is spread across many NAND packages in complex interleaved patterns, the mapping is held by the controller rather than being reconstructible from the flash alone, and many drives encrypt data internally with keys held in the controller — so raw memory read without it can be meaningless. The realistic route is therefore through the controller rather than around it: vendor-specific technological and safe modes that can sometimes bring up a drive whose normal start-up fails, allowing the firmware area to be repaired and the drive imaged. That works often enough to be well worth attempting, and when it does the recovery is complete. When it does not, the honest answer is that this is a genuine limit, and it is given plainly rather than sold around.
On his "isn't super important": worth a word. Hundreds of hours of configuration is real value even though it is not documents or photographs, and it is the kind of loss people apologise for caring about. There is no need to. The useful practical note is that configuration and profile data is small — so if the drive can be brought up at all, that particular content comes back quickly and completely.
On the bench
Nothing further was asked of the drive on ordinary interfaces, since his own testing had exhausted what those can establish. Access was attempted through the PC-3000 portfolio's SSD support: the controller 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. Where that access succeeded, the drive was brought to a readable state and imaged immediately and completely, with the modding installation's configuration tree — small, dense and quick to extract — verified against its own directory structure before delivery on fresh media. The honest alternative had been set out in writing beforehand, so that the answer either way arrived as an expectation rather than a disappointment.
The outcome
Controller-level access attempted on the only route this class of device offers, with the outcome and its limits stated in writing in advance. 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. What his case teaches: SSD health tools track NAND wear and not controller health, which is why the commonest SSD death arrives with no warning at all and a clean report behind it; testing two ports and an external cradle is a complete elimination and nothing further is worth trying; and SSD recovery genuinely differs from hard drive recovery — chip-level reading is not the reliable fallback it is on cards and sticks, because the mapping and often the encryption live in the controller. The route runs through the controller, it succeeds often, and where it does not that is a real limit rather than a negotiating position.
SSD that died with no warning and vanished from the BIOS
Your health tool wasn't lying to you — SSD monitoring reports NAND wear, not controller health, and controllers fail abruptly with no preceding indicator, so a clean report right up to the moment of death is completely normal. If you've tried two ports with known-good cables and an external cradle, your elimination is done and nothing further at home will tell you more; stop power-cycling it, since a drive in a bad firmware state can occasionally be made worse. Be aware that SSD recovery differs from hard drive recovery in one important way: reading the memory chips directly isn't the dependable fallback it is on cards and USB sticks, because the address mapping and often the encryption keys live inside the controller. The realistic route is controller-level access through vendor modes, which frequently works — and where it doesn't, expect a straight answer rather than an open-ended bill. Keep the drive; nothing degrades on a shelf.
Your testing is already complete — call Leeds Data Recovery on 0113 322 3083; controller addressed in vendor technological modes, firmware area assessed, honest limits stated in writing first.
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.