Lab accepting new cases ·  Mon–Fri, 9am–5:30pm Urgent? Call 01273 964902
BDR Brighton Data Recovery 01273 964902 Start a case
BDR / Casebook / The SSD That Works in No Laptop

Case file · SSD & flash · BDR-2025-0639

The SSD That Works in No Laptop.

The Latitude will not boot, and the diagnostics are flat: the disk is not recognised. The customer performed the engineering correctly (they swapped the disk with different laptops, both ways), and the conclusion of all testing parties was that the disk does not work in any. The hardware failure lies within the drive, not the laptops.

Outcome verified with the client Details anonymised

Same symptoms on your desk?
01273 964902

The decode.

Two-way swap testing is the most effective fault isolation method available to anyone who doesn't have a lab for performing troubleshooting. That's how the controller of the SSD (a processor responsible for presenting the memory to the host computer and maintaining a mapping table that associates each logical address used by the host operating system to a specific location in the NAND) was identified as the part that failed. Failure can occur in controllers, while typically the NAND devices are far longer lived. However, accessing that memory is a completely different form of technology compared to any platter-based device technology due to lack of a surface to read and no mechanical fault to repair.

Equipment on this case.

How a job runs here →
The systemWhat it did on the dayWhy this tool
PC-3000 SSDBrought the controller into a service state and read the memory behind itController-level access to SSDs, where there are no platters to read
PC-3000 FlashChip identification and raw read support from a current memory databaseReads memory chips directly, with a current chip database for automatic identification
UFS Explorer Professional RecoveryReassembled the filesystem once the translation layer had been reconstructedStronger than most on the awkward filesystems — APFS, ReFS, XFS, ZFS, Btrfs

At the bench.

01

Confirm the controller, not the memory, is the casualty

The evaluation of the SSD occurred at a controller level instead of being evaluated using any type of host interface. The controller was unable to complete its self-initialisation, the phase during which an SSD loads its translation maps and prepares to respond to the host. There were no indications that the NAND portion of the SSD had become exhausted or damaged.

02

Get the controller into a state that will cooperate

Using the vendor-specific mechanisms the platform provides for access, the controller was transitioned into a technological mode, a service state wherein it would relinquish the memory contents it refused to provide otherwise. This is what distinguishes SSD recovery efforts from simply replacing an SSD.

03

Rebuild the map, then the filesystem

Raw memory contents represent nothing without the ordering provided by the translation layer; therefore, the mapping was recreated prior to beginning any filesystem operations. Only after the mapping was created could the NTFS file system be constructed, and files and directories reappeared organised according to their respective structures rather than as pieces.

Where it ended up.

All of the user's data were restored successfully and returned on new media. The Latitude was again able to boot successfully when presented with a replacement disk; thus the customer's swap testing prevented having to do one additional diagnostic step.

What this case teaches: If your SSD fails in every machine, then you know exactly where the problem resides. Continue performing your swap tests; this is diagnostic testing.

Recognise your own drive in this story?

Do the same thing as all of the cases above: turn off the power source, and allow the diagnosis process to run free of charge prior to making your determination.

01273 964902