A music collection went dark when this laptop's SSD "failed unexpectedly last week". The account that reached our South Yorkshire intake is precise: "The drive failed without warning", the operating system stopped seeing it, and a second machine connected over a SATA-to-USB cable proved "unable to detect the storage drive either". Sensibly, the owner "removed and replaced the faulty storage drive but have retained it". Sudden, total invisibility across two computers points to a controller or firmware failure rather than worn-out memory — and that distinction is exactly what makes the case workable.
| Media | SATA solid-state drive from a laptop — no detection on the host system or on a second machine via USB adapter; drive removed, retained and unpowered since |
| Reported situation | Sudden failure during normal use with no prior symptoms · drive invisible to the operating system, to diagnostics and to boot · cross-checked on a second computer over SATA-to-USB with the same result · replacement fitted, original kept safe · unreplaced personal media collection sought |
| Fault class | Electronic failure at controller or firmware level — the memory almost certainly intact behind a component that has stopped introducing itself to any host |
| Equipment used | Power-rail behaviour profiled on a bench supply with current monitoring before any host connection · PC-3000 SSD with manufacturer-specific loaders and technological modes for the drive's controller family · safe-mode access via service pins where the family provides them · translator and firmware structures rebuilt where damaged · full image taken the moment stable access exists, with hash verification |
Gradual and sudden point at different components. Worn flash memory announces itself: slowdowns, errors, files that stop opening. A drive that is perfect on Monday and invisible on Tuesday has lost the component that speaks for it — the controller, or the firmware it boots from. The memory chips behind it rarely die in the same instant.
Their two-machine test already did real diagnostic work. Trying a second computer and a different interface rules out the laptop, its port, its cable and its operating system in one move. When nothing anywhere sees the drive, software-level explanations are finished — and so is any software-level fix, which is why further tools were never going to help.
An SSD that never enumerates is unreachable by every consumer method. Detection is the drive's own first act: firmware boots, identifies itself, reports a size. When that handshake never begins there is nothing for recovery software to scan. Access has to be re-established underneath the standard interface, in the controller's technological modes.
Firmware failure is a known disease with known treatments. SSD system areas — the maps that translate addresses to physical flash — corrupt in recognised, family-specific ways, and professional platforms carry loaders for exactly this: waking the controller in a service state, rebuilding the translator, and bringing the drive up long enough to be imaged completely. First stable access is spent on a full image, because a revived controller owes you nothing twice.
One honest caveat belongs on the table early. Many SATA SSDs encrypt internally as a matter of course, keyed inside the controller even when the owner never set a password. For those, reading the memory chips directly around a dead controller yields ciphertext — so the viable path runs through reviving the controller itself, and the assessment establishes early which kind this drive is.
Retaining the drive unpowered was quietly excellent. No repeated power cycles on a failing controller, no reinitialising attempts, no tools writing hopefully at an absent device. The case arrives in the best condition its failure allows.
Power rails were profiled first on a bench supply with current monitoring, distinguishing a dead-short board from a controller that powers but never boots its firmware. The drive was then brought up on PC-3000 SSD using the loader for its controller family, safe-mode pins used where provided, and the translator and damaged firmware structures rebuilt. With stable access established, the drive was imaged in full and the music library extracted from the verified image.
Rail profiling, controller revived in technological mode, translator rebuilt, full image on first stable access and the collection extracted. Free assessment, one fixed written figure including VAT; where recovery is not possible, nothing is charged. The decode: no warning is the signature of an electronics failure, and electronics can be worked with. Your memory chips are almost certainly fine — they have simply lost the component that introduces them.
Stop power-cycling it — each attempt exercises the failed component, and on some families worsens the firmware state. Software cannot scan a drive the computer cannot see, so skip further tools. Do exactly what was done here: remove it, keep it safe and unpowered, and note the make and model, because on solid-state drives the controller family determines the recovery route before the drive is even connected.
Our case files are written up from genuine enquiries our lab has handled for customers across Sheffield and South Yorkshire, anonymised to protect client confidentiality. Each one describes the diagnostic and recovery approach our engineers apply to that fault, using the equipment listed.
Free diagnostic, fixed quote, no fix no fee — start now or call the freephone.