Call us — 01223 655015
Mon–Fri · 9am–5:30pm · No fix, no fee
Start a free diagnostic →
/ home / services / ssd not detected
Specialist recovery · undetected SSDs

SSD not detected — recovery in Cambridge.

Before assuming the drive is dead, take five minutes to rule out your computer. Loose M.2 cards, silent SATA cable failures, and firmware that hides drives can make a good SSD appear as if it has died. Once you have exhausted these possibilities, here's how to interpret the symptoms you've identified.

£300 + VAT
Only pay if we recover your data, on most jobs
Chip-off done in-house
// work outward from the drive

Four layers, and the drive is only one.

LayerWhat to testRules out
The connectionReseat the M.2 module, try another cable Loose M.2 cards will cause problems with connectivity; so too will silent SATA cable failures. A total of thirty seconds to reseat either device may solve a large number of issues. Physical contact
The slot or portTry a second M.2 slot or SATA port Faults at the board level will present identically to failed storage devices. If you have a working SSD that you know is good in this particular slot (or port), and your own SSD does not function properly in that slot, then yours is the faulty SSD. Host hardware
The BIOSCheck whether the drive appears at all A drive that appears within BIOS but is not visible in Windows indicates an issue with either the partitioning of the drive or the file system. A drive that is missing from BIOS completely would be indicative of an issue at the hardware or firmware level. Software vs hardware
Another machineUSB adapter or a different PC This will quickly eliminate driver-related issues, controller settings and OS faults in one step. This is worth doing before assuming the worst-case scenario. The host entirely
// what the symptom means

Three presentations, three different faults.

01 / ABSENT ENTIRELY

Nothing in BIOS

The controller has lost communication. The most common type of failure by far, and the data on the NAND itself is typically still intact. To reach the data, we will need to go into vendor mode or read the memory directly.

02 / WRONG CAPACITY

Reports a fraction of its size

The solid state drive (SSD) has lost or corrupted the table(s) explaining how it physically organises itself. Such an issue is the result of a firmware problem rather than actual physical damage, and is often one of the more recoverable cases.

03 / DETECTED, UNREADABLE

Appears but will not open

Hardware works, file system doesn't. Least expensive class and most likely to be damaged when you accept Windows' “format” / “initialise” offer.

// how it is reached

Two routes in, when the controller is gone.

In cases where the controller itself does not respond, there are two methods available to access the stored data. The first is vendor mode, a manufacturer-specific “engineering” interface through which we can review/repair the controller's own firmware and the translation tables used by the controller to interpret your data. Since in this case the drive is able to reconstruct its own data from what is stored on it, this is the preferred method.

When a controller fails completely, we have to bypass the controller and read the NAND (the non-volatile memory chips) directly. The memory chips are accessed and the raw flash is extracted; after that, the data is reconstructed by performing operations that reverse those done to it by the failed controller: wear levelling, interleaving, XOR scrambling and error correction. All of these operations can differ depending upon the manufacturer of the controller and/or the version of its firmware.

The hard part is putting it back together (that's why SSD work is not simply plugging chips in) because if the controller's arrangement is not reversed properly, raw NAND will look like static noise.

// pricing

From £300, fixed in writing.

The price for SSD and NVMe recovery is from £300 +VAT. We charge the same for direct NAND reads as for vendor-mode work; this pricing is established at diagnostic by fault type, regardless of how involved the work turns out to be.

There's very little chance of a committed parts cost on our solid-state work, unlike mechanical work, so on nearly all of it you only pay if we recover your data.

// questions

Undetected SSDs, answered.

You don't get any warning from solid state, but SMART does provide reasonable data on flash wear, and virtually nothing about the controller's health. It is the controller that usually fails. There was no sign for you to miss.

Yes, for the great majority of failures. This is due to the fact that it is the controller/firmware that fails, rather than the NAND flash where the data is stored. Thus, your data still exists in a physical sense but cannot be accessed normally due to the failure of the controller/firmware.

No. Initialising the disk creates a new partition table and removes the existing table used to locate your files. When Windows indicates it cannot read a disk, that is exactly what a recoverable error looks like.

A lot. Several NVMe SSDs are encrypted with the default setting. If you have the password/key, it does not matter; without either one, there is no way into the drive, regardless of how good the health of the NAND may be.

No. The only drives we attempt to recover are those which can be physically removed from a computer. Therefore, an SSD which is soldered onto a laptop or Mac board is not something we recover. In addition, for Apple T2 and Apple Silicon computers, the key is also permanently stored in a security chip located on that same board.

Typically 3-10 working days. Recovery through vendor mode typically occurs faster than through a direct read of NAND due to the fact that we must reverse engineer the organisation of the data arranged by the controller prior to being able to make use of it.

// ssd not showing up?

Leave it unformatted — we’ll recover it.

We do our own controller, firmware and chip-level recovery and provide a complimentary written diagnosis to start with. Also, in most cases you only pay if we recover your data. Begin your recovery today.