Flash & SSD · case file · CDF-2025-0639
No Computer Would Admit It Was There.
For a month the Dell Latitude had been freezing on her — it stops dead for a minute or so, then carries on like nothing went wrong
. A researcher in Lisvane, and a month is a long time to work around that. Tuesday morning it got no further than Boot Device Not Found
. She put the drive into her partner's laptop, then into a USB caddy, and the 850 EVO wasn't there in either of them
. Work's help desk reckoned a rebuild was all they could offer
, no use at all to a half-written MA and the interview recordings underneath it.
Does that match yours? Call us.
0800 6890668
Why that happens.
Every SSD carries a small processor that does two jobs: it introduces the drive to the computer, and it keeps the table saying which flash page each logical block actually lives on. That is the controller, and it gives out long before the flash it looks after comes anywhere near worn. Which is what those minute-long freezes were, in hindsight — the table coming apart while she typed. Her own troubleshooting had settled most of the rest before the parcel arrived: when no host anywhere will list a disk, the trouble sits past the connector, and inside an SSD there are not many suspects. Working on flash with the controller out of play is nothing like working on a disc. Nothing turns, nothing is mechanical, and the SATA plug has nothing further to say.
What we used on this one.
Every step, in order →| The tools | What it did here | Why it helps |
|---|---|---|
| PC-3000 SSD | Held the chip in the maker's own factory state for the entire read | Built for SSD controllers alone; no mechanics involved anywhere |
| PC-3000 Flash | Matched the V-NAND against its chip library, then pulled the raw dump | Bypasses the controller to read the NAND itself, against a manufacturer-ID library kept up to date |
| UFS Explorer Professional Recovery | Rebuilt folders, chapters and interview audio out of the sorted image | Reads the volume formats that defeat most software: APFS, ReFS, XFS, ZFS, Btrfs |
How it went.
The first question: worn flash or a dead controller
It never went near a host port again. All of it was done on the bench at controller level, and every start-up died in the same spot: the moment the translation tables are meant to load, which comes before a drive tells a computer anything at all about itself. Then the wear counters, which were the good news of the day — the memory had years in it yet.
Open the service mode the factory keeps for itself
Technological mode was where the controller had to go — a factory state that no everyday computer has any reason to ask for, reached through a set of vendor-specific commands. Once it is there, the chip hands over the raw contents it will not give up by any other route. That one step is the difference between this drive going home and this drive going in the bin.
Put the pages in order first, then look for files
What comes off is scrambled by design. Wear-levelling puts consecutive parts of a file in whatever package has room at the time, so the mapping has to be worked out again before any of it resembles a document. Once that was done the NTFS volume opened intact, folders where they belonged and the chapters still carrying the names she had given them.
Signing it off.
The thesis went back whole on fresh media, along with every interview recording and the entire reference library. There was never anything wrong with the Latitude; a new SSD went in and it runs perfectly well. She has promised the finished thesis three homes rather than one, and we will be asking.
Pages people often read next.
Next to SSD & flash.
Is that what yours is doing?
Power it down, get it to us, and hold off on any decision until the diagnosis says what can still be read.