Data Recovery Case File · Solid State & Flash · Two at Once Means a Common Cause
Devices That Fail Together Usually Share Something, and It Is Rarely Both Devices
Her enquiry carries a belief worth correcting and an observation worth pursuing. Two solid-state drives that "have failed and stopped even showing up", used to move files off a machine before running updates, with the documents held nowhere else — and the assumption that "solid-state drives can be almost impossible to recover." They are not, and two failing together is the more interesting fact, because independent devices do not usually fail on the same day.
| Media | Two solid-state drives used for file transfer — both ceasing to enumerate; documents held nowhere else; internal support unable to assist |
| Reported situation | Two solid-state drives used to transfer files from a laptop prior to system updates · both drives subsequently ceasing to appear on the host · documents not held elsewhere · internal support unable to assist · owner understanding solid-state recovery to be largely infeasible |
| Fault class | Simultaneous non-enumeration of two independent devices — common cause indicated at the host, connection or handling; controller-level faults typical and memory contents retained |
| Equipment used | Simultaneous failure treated as evidence of a common cause rather than of two independent faults · each device assessed separately on controlled equipment · board and connector examined at component level under magnification · memory read past the controller where devices did not present · translation layer reconstructed in software for each |
The decode: correcting the belief, then following the coincidence
Why solid-state recovery is not close to impossible: the memory is readable directly. Where a controller will not run, the memory package is addressed past it and the content reconstructed in software.
Where the belief comes from: a real phenomenon applied too widely. Deleted files on a solid-state device are frequently unrecoverable because the drive blanks them on its own schedule, and that specific fact has become a general reputation.
Why it does not apply here: nothing was deleted. Her files were written and the devices then stopped presenting, which is a hardware fault rather than an erasure.
Now the coincidence, which is the useful part: two devices failed together. Independent electronic failures on the same day are unlikely, so something shared is the more probable explanation.
What they shared: a host, a port and a session. Both were connected to the same machine, in the same period, doing the same job.
What that suggests first: the host. A port supplying incorrect voltage or a failing power stage can damage successive devices connected to it.
What it suggests second: the removal. Devices disconnected during a transfer, or during a system update, can be left with inconsistent internal state.
Why the update detail is worth noting specifically: updates restart machines. An update cycle can power down and restart a host repeatedly, and devices connected throughout experience each of those.
Why the distinction matters practically: it predicts the fault. An electrical cause suggests board damage; an interrupted-state cause suggests a controller that will not initialise with intact memory behind it.
What must not happen now: neither device connected to that machine again. If the host caused this, it will do it to whatever is plugged in next, including a recovered copy.
On the bench
Simultaneous failure was treated as evidence of a common cause rather than of two independent faults — independent electronic failures on the same day being unlikely, while both devices shared a host, a port and a session. Solid-state recovery remains feasible because memory is addressable past a non-functioning controller; the contrary reputation derives from deleted content being blanked on the drive's own schedule, which does not apply to written files. Each device was assessed separately on controlled equipment.
The outcome
Simultaneous failure treated as a common cause, each device assessed separately, and memory read past the controller where they did not present. 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. The decode: two independent devices do not fail on the same day by chance. They shared a machine, a port and a session — and that is the thing to look at, including before you plug anything else into it.
Two devices that stopped working together
Don't connect either of them, or anything else, to the machine they were used on — if the host caused this, it will do the same to whatever goes in next, including a recovered copy. Treat the coincidence as the main clue: independent electronic failures on the same day are unlikely, and what they shared was a port, a host and a session. Set aside the idea that solid-state recovery is near-impossible, too. That reputation comes from deleted files being blanked, which isn't what happened here.
Leave that machine alone — call Cambridge Data Recovery on 01223 655015; simultaneous failure treated as a common cause, each device assessed separately, memory read past the controller.
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.