Yesterday it was an ordinary laptop. Today: ‘no bootable device’, a BIOS listing every port except the one that matters, a drive that has simply vanished. An undetected SSD is its own service category because the causes range from a loose connector to a controller that died overnight — and because every DIY hour spent ‘trying things’ is usually wasted on the wrong cause.
$ ldr nvme id-ctrl → Device: Samsung 980 Pro 2 TB → Status: NOT DETECTED — controller fault → Client: confidential · Bradford $ ldr controller-repair → Controller: re-initialised → FTL: rebuilt from NAND → Imaging: 1.86 TB · 99% read $ ldr verify → ✓ Lightroom_catalog — recovered → ✓ RAW_shoots — 12,880 files → ✓ galleries — safe
Before assuming the worst: reseat once (an M.2 blade or SATA cable that’s walked loose is a real thing, especially after transport or a knock), try one other port or machine once, and glance in BIOS rather than Windows — a drive visible to BIOS but not Windows is a software problem with far gentler answers. That’s the whole approved list. What’s off-list: firmware updates on a misbehaving drive, ‘low-level repair’ utilities, and marathon retry sessions — if a drive is undetected for hardware reasons, retries add nothing, and if it’s wavering in and out, the window for a clean image is closing while you toggle.
Roughly in order of how often we see them: firmware panic-locks — the SSD hits internal corruption and hides rather than risk your data, sometimes presenting as zero-capacity or a wrong name (these respond to service-mode access, and the data typically returns complete); controller death, where the drive’s brain is gone and recovery reads the NAND directly; power-side failures on the drive’s own board; and connector damage on drives that travel. The free diagnostic identifies which within a day or two of arrival — considerably cheaper than guessing, in both money and data.
Comparatively good news: the hardware is still answering, so the problem lies in the partitions, file system or drivers — the recoverable end of the spectrum. Don’t initialise or format when prompted; that's Windows offering to pave over the data it can't read. Diagnostic will read what Windows can't.
No. Intermittent detection means something is failing, and each time it appears could be the last. If it’s visible right now, copy the irreplaceable straight away, most-precious first. If it's gone again, stop cycling power and bring it in while a clean image is still likely.
A manufacturer firmware update can, which is precisely why it’s on the do-not-do list for a drive holding data you haven’t backed up. Bench-level firmware recovery is different: service-mode access that repairs the drive's internal state specifically to read your data out, not to refurbish the drive.