Case file · SSD & flash · BDR-2025-0639
The SSD That Works in No Laptop.
The Latitude will not boot
, its diagnostics flat: the disk is not recognised
. The owner did the engineering properly — swapped the disk with different laptops
, both directions — and the verdict was unanimous: the disk does not work in any
. The drive, not the machines.
Same symptoms on your desk?
01273 964902
The decode.
Two-way swap testing is the cleanest fault isolation available to anyone without a lab, and it convicted the SSD's controller — the processor that presents the memory to the host and maintains the map between logical addresses and physical NAND pages. Controllers fail; the NAND they front usually outlives them. But reaching that memory is a fundamentally different discipline from anything involving platters, because there is no surface to read and no mechanical fault to repair.
Equipment on this case.
How a case runs →| Platform | What it did here | Why this tool |
|---|---|---|
| PC-3000 SSD | Brought the controller into a service state and read the memory behind it | Controller-level access to SSDs, where there are no platters to read |
| PC-3000 Flash | Chip identification and raw read support from a current memory database | Reads memory chips directly, with a current chip database for automatic identification |
| UFS Explorer Professional Recovery | Reassembled the filesystem once the translation layer had been reconstructed | Stronger than most on the awkward filesystems — APFS, ReFS, XFS, ZFS, Btrfs |
On the bench.
Confirm the controller, not the memory, is the casualty
The drive was assessed at controller level rather than through any host interface. It was failing to complete its own initialisation — the stage where an SSD loads its translation tables and prepares to answer the host. Nothing suggested the NAND itself had been exhausted or damaged.
Get the controller into a state that will cooperate
Using the vendor-specific access the platform provides, the controller was brought into a technological mode — a service state in which it will surrender the memory contents it refuses to serve normally. This is the step that separates SSD recovery from SSD replacement.
Rebuild the map, then the filesystem
Raw memory contents mean nothing without the translation layer that orders them, so the mapping was reconstructed before any filesystem work began. Only then was the NTFS volume assembled — files and folders reappearing in their proper structure rather than as fragments.
The outcome.
The user's data recovered complete and returned on new media. The Latitude, blameless throughout, booted happily on a replacement drive — and the owner's swap testing had saved a diagnostic step.
Related on the index.
More from SSD & flash.
Recognise your own drive in this story?
Same rule as every case above: power it down, and let the diagnosis be free before any decision has to be.