Data Recovery Case File · Solid State & Flash · Substitution Settles It

Testing the Socket With Something Known Good

His enquiry contains the single most conclusive test anybody sends in. A solid-state drive no longer detected: "I tried different ports but it still didn't work. The PC was able to detect a different drive in the same slot, so it seems like a broken drive." He is right, and the reason he can be certain is the second half. Fitting a known-good device into the same slot is the cleanest elimination in the whole subject — and almost nobody does it, because it requires having a spare.

The decode: why substitution is worth more than repetition

What most people do: try the same drive in different ports, on different machines, with different cables. That is repetition, and it eliminates things one at a time while never producing a positive result — the drive fails everywhere, which is consistent with a broken drive and also with an unusual configuration problem or a systematic incompatibility.

What substitution does instead: puts a device known to work into the exact position the failing one occupies. When that device is detected normally, the slot, its power delivery, the controller behind it, the firmware settings and the operating system are all proven working in the specific configuration that matters. That is a positive result rather than an absence of one, and it is why one substitution test is worth more than a dozen repetitions.

Why it matters particularly for this kind of drive: these slots are configurable, and a slot can be disabled, assigned to a different interface, or sharing bandwidth in a way that turns it off under certain conditions. Those produce a drive that is not detected while being perfectly healthy — and they are indistinguishable from a failed drive by any amount of retrying. A working substitute rules all of them out at once.

So what his result establishes: the machine is fine, the slot is fine, the configuration is fine, and the drive is not. That is a complete diagnosis arrived at by the owner, and the assessment starts from it rather than repeating it.

What remains, and where it sits: a solid-state drive that is not detected has failed to complete its own initialisation. These devices run firmware on power-up, reading internal structures before they can announce themselves — capacity, geometry, and the map linking logical addresses to physical memory. Where those are damaged or the controller has partly failed, the drive never reaches the point of introducing itself, and nothing above it can help.

What the route is: manufacturers build technological and safe modes into their controllers for exactly this, allowing the firmware area to be assessed, damaged modules repaired and addressing restored. The aim is to revive the controller rather than to bypass it, because on this class of device the mapping and frequently the encryption live there.

Worth generalising: if you can borrow or spare a working device of the same type, fit it where the failing one goes. One minute, one conclusive answer.

On the bench

The owner's substitution result was accepted as conclusive — a known-good device detected in the same slot proving the machine, the slot, its power delivery, the firmware configuration and the operating system simultaneously, which repetition with the failing drive cannot do. The drive was assessed on a direct adapter with initialisation state read directly, and vendor technological and safe modes attempted through the PC-3000 portfolio's SSD support, with the firmware area and translation layer assessed.

The outcome

The owner's elimination accepted, the drive assessed on a direct adapter and vendor modes attempted. 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, and the test worth copying: fit a device you know works into the exact slot the failing one occupies. That single positive result proves the machine, the slot, its power and the configuration all at once — where retrying a failing drive in different places only ever produces more absences of evidence.

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.