Flash & SSD · job notes · RDG-2025-1789
The Memory Was Fine. No Machine Could See It.
The Dell Latitude had been freezing for a month: It seizes for a minute at a time, and then it is fine again, as if nothing had happened
. A research analyst here in Reading had been working around that for four weeks. Then on the Tuesday: Boot Device Not Found
, and nothing further. The SSD went into her partner's machine and then into a caddy, with the same result each time: turned up in neither of them
. Her employer's IT offered a rebuild and that was all
— no use whatever to a part-time MA still being written, or to the interview recordings under it.
Same fault on yours? Tell us what it is doing.
0800 6890668
What actually caused it.
Inside every SSD sits a small processor with two jobs: presenting the disk to whatever host is asking, and maintaining the table that says where a given logical block currently lives in flash. It is called the controller. In practice it fails a long way ahead of the memory it looks after. Those minute-long freezes had been that table breaking up beneath her, with nothing on screen to say so. She had narrowed the field herself before posting anything: a disk that no host will list has a fault beyond the connector, and an SSD does not offer many candidates. Past that point the work resembles a disc job in no respect at all. No motor, no head, no mechanism, and the SATA connector stops mattering entirely.
What this one needed on the bench.
How every job runs →| Bench tools | Its part in this job | Why it is here |
|---|---|---|
| PC-3000 SSD | From first probe to last, the chip was left in its factory service state | Made only for SSD controllers; nothing mechanical enters into it |
| PC-3000 Flash | Identified the V-NAND from the chip database, then pulled the raw image | Reads the NAND direct, past the controller, against a maker-ID library kept current |
| UFS Explorer Professional Recovery | Folders, chapters and audio recovered once the image was back in order | Opens volumes other tools refuse: APFS, ReFS, XFS, ZFS and Btrfs |
What the bench did.
Is the memory used up, or is the controller silent?
After that it saw no host port at all. The rest of the job ran on the bench at controller level, where every attempt to bring the disk up stopped at the same step — loading the translation tables, which has to succeed before a disk can identify itself to anything. The wear counters were the good news of the day: plenty of life left in the memory.
Getting into the factory's service mode
Technological mode was what this controller needed. It is a factory condition, not something an ordinary computer would ever request, and the way in is through vendor-specific commands. In that state the chip will hand over its raw contents; outside it, the chip hands over nothing. Fail at this step and there is no job. Get through it and the files are already as good as home.
Reorder the pages before looking for a file
A raw dump comes out scrambled by design. Wear levelling puts each new piece of a file into whichever package has room at that instant, so the mapping has to be rebuilt from scratch before a document reads as one document. With that done, NTFS mounted without a murmur: folders in their proper places, chapters under her own names for them.
What went back.
The thesis went home on new media, the interview audio and reference library with it. The Latitude had not been the problem at any point. A replacement SSD went in, and it has run properly since. From now on, she says, finished work will sit in three places at once. We intend to check. The job was the published single-drive band, £300 + VAT, agreed in writing before it started.
If this sounds like yours, start here.
More from the flash and SSD file.
If that sounds like yours, stop there.
Post it in as it is, switched off. Looking costs nothing, and you get one fixed figure in writing before any chargeable work begins — £250 + VAT for a card or stick, £300 + VAT for a single drive, from £500 + VAT for RAID and NAS. On most jobs, nothing is charged unless your data comes back.