Case notes · SSD & flash · MKD-2025-4639
A Month of Locking Up, Then Nothing.
A Wolverton researcher's Dell Latitude had spent a month locking up for a minute, then carrying on
. One Tuesday it got as far as Boot Device Not Found
and stopped. Her partner's laptop was tried, then a USB caddy, and the 850 EVO didn't appear on any of them
. The IT desk at work could only suggest a rebuild
— no answer at all for a half-written MA and the interviews behind it.
Same fault? Start here.
0800 6890668
Without the jargon.
Her round of borrowed hardware had already done most of the diagnosis. A drive that no host will list is carrying its fault internally, and on an SSD there is really only one candidate: the controller, the small processor that fronts the drive and maintains the table tying every logical address to a flash page. Controllers routinely fail years before the memory they look after. Read backwards, those minute-long freezes were that table already coming apart. Reaching flash without a working controller resembles platter work in no respect at all. Nothing spins, nothing is mechanical, and the ordinary interface says nothing.
The kit this job needed.
See how a job runs here →| Kit | Why it was used | What it gives us |
|---|---|---|
| PC-3000 SSD | Kept the chip in the factory's own service state while the dump ran | Made to address SSD controllers directly, with no mechanism involved |
| PC-3000 Flash | Identified the V-NAND against its chip library and handled the raw read | Pulls data straight off the flash chips, matching each part to a constantly updated ID library |
| UFS Explorer Professional Recovery | Made the reordered image readable again: folders, chapters, interview audio | Ahead of the pack on difficult filesystems: APFS, ReFS, XFS, ZFS, Btrfs |
What happened on the bench.
Decide first: worn-out flash, or a dead front end
No host port came near it again. Everything happened at controller level on the bench, and start-up kept collapsing at one telling point: the moment where an SSD pulls in its translation tables before it will present itself at all. The wear figures gave the better half of the news, because this flash had plenty of life left.
Take the controller into the mode its maker reserved
Vendor commands put the controller into technological mode. That is a factory service condition, one no ordinary machine ever asks for, and in it the chip will surrender the raw contents it otherwise refuses to serve. That single manoeuvre is the entire difference between recovering this drive and skipping it.
Put the order back before asking for a single file
Raw NAND arrives out of order on purpose. Wear-levelling spreads each file across the chips, so the mapping had to be rebuilt before any of it resembled data. From the reordered image the NTFS volume came back intact, folders exactly where she had left them, chapters still carrying their own names.
The outcome.
The thesis, the interview recordings and the reference library all came back complete on new media. The Latitude itself had done nothing wrong and runs today on a replacement SSD. She has undertaken to keep the finished thesis in three places, which we intend to hold her to.
Other jobs from the casebook.
More from SSD & flash.
Does that sound like your device?
One lesson runs through the lot: cut the power, let us look for free, then decide with the facts in hand.