SSD Not Detected in BIOS? Stop and Read This First.

What this means and what to do next

An SSD that has stopped showing up in BIOS, Disk Management or Disk Utility presents very differently from a hard drive with the same symptom. There's no clicking, no whining, no audible cue at all — SSDs are silent in operation and silent in failure. The first sign is usually that a system that booted yesterday won't boot today, or a backup drive that worked last week now appears nowhere when plugged in. The drive is probably not mechanically dead. What has almost certainly happened is a firmware-level fault inside the SSD's controller, and the data is still on the NAND chips inside.

Modern SSDs are essentially small computers. The controller chip runs firmware that translates host commands (read this LBA, write this LBA, TRIM these blocks) into the dance of reads, writes, and garbage collection across the NAND flash chips. The mapping between LBAs and physical NAND locations lives in a complex tree of metadata called the Flash Translation Layer, or FTL, and a corruption of the FTL is the single most common cause of an SSD going undetected — the controller boots, looks for its FTL, finds inconsistent data, and refuses to expose any drive at all to the host as a safety measure. The user data is intact in the NAND chips, but it's only meaningful with the FTL that maps it.

What this means for recovery: SSDs are recoverable, but the techniques are completely different from hard drive recovery. We use specialist SSD-aware tools (PC-3000 SSD, custom firmware loaders, NAND chip-off readers) to either repair the SSD's firmware in place, force the controller into a maintenance mode that exposes the data despite the FTL fault, or — for the hardest cases — desolder the NAND chips themselves, read them directly, and reconstruct the FTL in software. Each manufacturer's controller has its own quirks, so brand and model matter.

The four most common causes of an SSD not being detected

1. Firmware corruption in the Flash Translation Layer (FTL). By far the most common cause. The controller boots, attempts to read its FTL from a reserved area of the NAND, finds the FTL inconsistent (often because of an unexpected power loss during a write), and refuses to come online. The drive shows up in BIOS as either nothing at all or as a 0 GB device with a generic name. Recovery typically uses a manufacturer-specific technology mode on the PC-3000 SSD to repair or rebuild the FTL in place; if that's not possible, we move to NAND chip-off.

2. NAND wear or failed NAND blocks crossing a critical threshold. SSDs have a finite write endurance. Consumer drives are rated at hundreds to a few thousand program-erase cycles per cell; enterprise drives are rated higher. As cells wear, they get retired by the controller until eventually too many cells are retired and the controller can no longer guarantee data integrity. Some SSDs respond to this by silently going read-only, others by simply refusing to come online. Recovery requires reading the surviving NAND blocks, repairing the FTL to point to those blocks, and extracting the data.

3. Power-event damage — surge, brownout, or controller chip burnout. A surge from a failing power supply, a lightning strike on the mains, or even a poorly-grounded USB port can damage the SSD's controller chip directly. Symptoms vary from "no detection at all" to "detected as 0 bytes" to "detected with the wrong size". Recovery usually requires NAND chip-off — desoldering the NAND chips from the failed SSD, reading them directly with a NAND reader, and reconstructing the FTL in software. Encryption (very common on modern SSDs) makes this harder but is solvable for most controllers.

4. M.2 / U.2 connector or motherboard slot fault (false alarm). Worth ruling out before assuming the SSD is dead. An M.2 NVMe drive that's not seated correctly, a worn M.2 slot, or a motherboard with a flaky NVMe controller can all show "SSD not detected" while the SSD itself is fine. We always test inbound SSDs in two different known-good slots before declaring a controller fault. If your local IT person has tried multiple slots already, this isn't your problem.

How Data Clinic recovers an SSD that won't show up in BIOS

On arrival, we identify the exact SSD make, model and controller. The controller chip's identity (Samsung Phoenix, Marvell, Silicon Motion, Phison, Realtek, etc.) determines which recovery tooling and which firmware extraction techniques we'll use. We then test the SSD in two known-good interfaces (SATA, M.2 NVMe, U.2 as appropriate) to rule out connector or motherboard issues.

If the SSD is responding but with FTL corruption, we connect it to a PC-3000 SSD and put it into manufacturer-specific technology mode — a low-level diagnostic mode that bypasses the normal boot path. From technology mode we can read the controller's internal logs, inspect the FTL state, and either repair the FTL in place or extract a complete user-data image despite the FTL damage. This is the fastest and lowest-cost recovery path; many cases complete in 1 to 3 working days at our lower price tier.

If the controller is non-responsive, we move to NAND chip-off. The SSD is opened, the NAND flash chips are desoldered using a hot-air rework station, and each chip is read directly using a Riff Box, PC-3000 Mobile, or specialist BGA NAND reader. We then reconstruct the FTL in software, decrypt the user data using the SSD's per-drive encryption key (which we extract from a non-volatile portion of the controller chip), and assemble the original file system. This is more invasive and more expensive but it's effective on SSDs that no other technique can reach. More about our SSD recovery service →.

Recovered files are returned on a new drive of your choice. We can also restore directly to a replacement SSD if you've bought one — we'll image the data straight onto it and hand you a working drop-in replacement.

Get a free initial diagnosis in 60 seconds

In the tool below, choose SSD → Not detected by computer for the right recovery path.

What our customers say

Frequently asked questions