Case record · SSD & flash · SDR-2025-0639
The SSD No Laptop Will Accept.
It had been having trouble booting up properly
, and then it simply stopped working. The owner did the sensible thing and tried on other computers with the same result
: first another laptop, then a USB caddy, and not recognised in the system
each time. A repair shop had already said it couldn't help
.
Seeing the same thing yourself?
0800 6890668
The translation.
Running a suspect drive in a different machine, and a known-good drive in the original, is about the best diagnosis anyone can manage without a lab, and here it pointed clearly to the SSD's controller. That chip is the go-between: it presents the flash to the computer and keeps the mapping table that translates logical addresses into physical pages. Controllers typically fail long before the memory they manage does. However, getting to the data stored on flash memory is very much unlike working on a platter: there is no surface to read and nothing mechanical to fix.
Kit used on this job.
What happens in a case →| Which platform | Its role in this case | Why we use it |
|---|---|---|
| PC-3000 SSD | Coaxed the controller into a service mode and read the flash sitting behind it | Reaches SSD controllers directly, on media with no platter to read |
| PC-3000 Flash | Identified the memory against an up-to-date database and supported the raw read | Pulls data straight from memory chips, with a current library that identifies them automatically |
| UFS Explorer Professional Recovery | Put the file structure back together once the mapping had been rebuilt | Handles the difficult filesystems better than most — APFS, ReFS, XFS, ZFS, Btrfs |
In the lab.
Establish that the fault is the controller and not the flash
The disk was examined at controller level, never through a host port. It was stalling partway through its own start-up routine, the point at which an SSD reads in its mapping tables and makes itself ready to respond. There was no evidence of worn-out or damaged flash.
Persuade the controller into a state that will talk
Manufacturer-specific commands for the platform were used to place the controller into technological mode, the service state where it hands over memory contents it would not serve in normal operation. That single step is the difference between recovering an SSD and simply replacing one.
Rebuild the mapping, then the file tree
Raw flash contents are meaningless until the layer that orders them has been restored, so we did the mapping first and filesystem work second. Only after that was the NTFS volume put back together, with folders and files in their proper places rather than as loose pieces.
The result.
Everything the owner wanted came back in full, on fresh media. The Latitude was never at fault and started up just fine from a new disk, and the swapping he had already done spared us a diagnostic step.
Similar cases on the index.
Also from SSD & flash.
Does this sound like your own drive?
As always, the rule applies here: turn the device off, and let a free diagnosis come before any decision.