Data Recovery Case File · Solid State · The Half-Fit
"Doesn't really seem to fit" was the whole answer: an M.2 drive in the wrong caddies decoded — and the dead laptop's estate recovered on the interface it actually speaks
Her sequence was methodical and her suspicion list generous — everything got blamed except the actual culprit. The laptop, a ThinkPad, "died on Friday"; she bought a replacement, extracted the SSD, and tried it in two different caddies: the first, nothing; the second, "it recognises there's something plugged into the computer but won't open it, even after I manually updated all the USB drivers." Her suspects: the refurbished replacement laptop, its operating system's famous moods, the caddies. And buried in the middle, the observation that solves the case: "the SSD doesn't really seem to fit properly into either caddy." That sentence is the diagnosis. M.2 — the small stick format her laptop used — is not one standard but a family of them, and a drive that half-fits a caddy is a drive in the wrong caddy: mechanically persuadable, electrically incompatible. Everything on her suspect list gets acquitted below.
| Device | M.2 SSD from a deceased ThinkPad — the laptop's complete working estate aboard |
| Reported attempts | Two USB caddies: one silent, one enumerating-without-opening · USB drivers updated (no effect) · imperfect physical fit noted in both · no forcing beyond gentle seating, no reformats |
| Fault class | Interface mismatch — wrong-protocol caddies; the drive itself healthy throughout |
| Equipment used | Correct native M.2 interfacing (key and protocol matched) · write-blocked imaging · full-estate verification |
The decode: why M.2 isn't one thing — and why the half-fit was the kindest possible fault
The family, explained: M.2 describes the shape — the small rectangular stick — not the language. Inside that shape live two different protocols (an older drive-dialect and a faster modern one), signalled by different keying notches along the connector edge, plus a range of lengths. A caddy is built for one protocol; a drive speaks one protocol; and the market cheerfully sells caddies whose sockets will mechanically accept a mismatched drive — seating awkwardly, at an angle, "not really properly" — while being electrically unable to converse with it. Her two caddies produced the mismatch's two classic presentations: total silence from one, and from the other the tantalising half-result — the caddy's own USB bridge enumerating (the "something plugged in" her computer saw) while the drive behind it, addressed in the wrong language, never came up as storage. The acquittals, in full: the refurbished laptop — innocent; the operating system's reputation — irrelevant here; the driver updates — the era's classic wrong layer, governing the conversation channel when the problem was the language itself; and her — entirely innocent, because nothing about M.2's keying is explained on any caddy's box. The one real danger, named: a half-fitting connector invites one more firm push — and forced seating is how mismatch cases acquire genuine injuries: bent pins, cracked connector housings, edge-contact damage on the drive. Her gentle attempts and full stop meant this case arrived as the kindest thing an SSD case can be: a healthy drive that had simply never been spoken to correctly.
The recovery — the right socket, the whole estate
The bench did what no consumer caddy pairing had: identified the drive's actual key and protocol at a glance, seated it in native, matched interfacing — flush, correct, speaking its own language — and the SSD answered immediately and completely: healthy controller, healthy flash, the dead laptop's entire working world present and untouched. The estate was imaged write-blocked in one clean pass and verified across the set — documents, photos, the working files a daily-driver laptop accumulates — then delivered on new media in duplicate, ready for the refurbished successor. The report's cause line performed the mass acquittal: no drive fault; interface mismatch across both caddies (wrong protocol for the drive's keying); laptop, operating system, drivers and owner all cleared; the imperfect fit was the diagnosis, correctly observed and correctly not forced.
Outcome
The dead laptop's estate recovered whole from a drive that was never broken — and the M.2 filings the caddy market refuses to print. Treat "doesn't quite fit" as a stop sign: M.2 drives that seat awkwardly are in the wrong caddy — check the keying, or better, stop buying candidates; the third caddy is rarely luckier than the second, and forcing is the only way this genre acquires real damage. Read enumerates-but-won't-open on adapters correctly: that's frequently the adapter's bridge talking while the drive goes unaddressed — a mismatch signature, not a drive verdict. And when a laptop dies with its life aboard: the drive inside is usually fine — it needs the right socket, not a lottery of sleeves. She observed the fit, declined to force it, and asked. The drive had been healthy all along — waiting, in two wrong caddies, for someone to speak M.2 with the right accent.
Laptop SSDs that won't work in caddies
Stop at two attempts, and stop immediately if the drive doesn't seat flush and easy — half-fits are mismatches, and force is the only real hazard in this genre. Don't buy a third adapter, don't update drivers hoping to bridge a protocol gap, and never reformat on any partial appearance. Note the drive's model and the caddies tried; the bench matches key, length and protocol in seconds and reads the drive natively. Dead laptop, healthy drive is the commonest ending here — provided nothing bends before it arrives.
It's the wrong caddy, not a dead drive — call Belfast Data Recovery on 028 9002 0144; native interfacing, matched first time.
Request a quote online →
Our case files are drawn from genuine enquiries received by our laboratory over the past ten years, anonymised to protect client confidentiality. Each one describes the diagnostic and recovery procedure our engineers apply to that fault, using the equipment listed.