SSD & flash · written up · BHD-2025-8639
No Machine Will Admit It Exists.
A researcher in Edgbaston had spent a month with a Dell Latitude that kept locking up for a minute, then going on as though nothing happened
. On a Tuesday morning it gave her Boot Device Not Found
and stopped there. She tried the drive in her partner's laptop, then in a caddy on USB; the 850 EVO didn't show up in either one
. The help desk at work told me the only fix was a rebuild
, which does nothing for a half-written MA and the interviews sitting under it.
Sounds like yours? Give us a ring.
0800 6890668
What that means.
Those borrowed machines had done most of the diagnosis before the drive ever reached us. If not one host will list a disk, the trouble is on the far side of the connector, and inside an SSD the list of suspects is short. Top of it is the controller: the small processor that introduces the drive to a computer and holds the table linking every logical block to the flash page it actually lives on. A controller will often fail long before the flash it manages shows any real wear. In hindsight, those minute-long freezes were the map falling apart while she worked. Getting at flash with no controller in play bears no resemblance to disc work. Nothing spins, nothing is mechanical, and the SATA connector has nothing left to say.
What did the work here.
The order of the work →| Equipment | The job it did | What it adds |
|---|---|---|
| PC-3000 SSD | Kept the chip in the maker's factory service state for the whole read | Made for SSD controllers only; nothing mechanical stands in the way |
| PC-3000 Flash | Identified the V-NAND from its chip library, then took the raw dump | Goes straight to the NAND chips, checked against a maker-ID library that is kept current |
| UFS Explorer Professional Recovery | Rebuilt folders, thesis chapters and interview audio from the sorted image | Handles the file systems other tools give up on: APFS, ReFS, XFS, ZFS, Btrfs |
What we did.
First question: worn-out flash, or a dead controller
The drive never saw a host port again. Everything happened on the bench at controller level, and start-up failed in the same place every time: right where the translation tables get loaded, which is before a drive says anything about itself. The wear counters brought the good news. There was a great deal of life left in the memory.
Open the service mode the factory keeps to itself
Vendor-specific commands put the controller into technological mode, a factory condition no ordinary computer ever asks it to enter. Once there, the chip will give up the raw contents it will not serve any other way. That single step is the whole difference between a drive like this coming back and being written off.
Put the pages back in order before hunting for files
A raw dump comes out scrambled on purpose: wear-levelling spreads every file across the packages as it writes, so the translation has to be rebuilt before any of it looks like data. Once it was, the NTFS volume opened whole, every folder back in its place and the chapters still under the names she gave them.
How it closed.
The thesis, every interview recording and the full reference library went back complete on fresh media. The Latitude itself had never been faulty; it has a new SSD in it and runs fine. She has given her word that the finished thesis will end up in three different places, and we mean to check.
Other pages worth a look here.
Alongside SSD & flash.
Is yours behaving the same way?
Switch the device off, post it in, and decide nothing until the diagnosis comes back to tell you where you stand.