Data Recovery Case File · Portable Drives · Unlocked but Unmounted

Past security, short of the volume: where a drive that unlocks-but-never-appears is actually failing — and the not-yet-backed-up remainder brought home

His enquiry was one of the most self-aware this archive has received. The WD My Passport for Mac stopped mounting "not long after I plugged it into my new MacBook Air" — it managed the first couple of times, then never again — and his observations were layered and honest: no clicking or anything suggesting mechanical failure; a theory offered tentatively ("it is possible it is heat related"); and the crucial detail: "the security software still runs when it's plugged in, but once unlocked the drive does not appear" — on the new Mac, on a 2011 MacBook Air, or on a Windows desktop. Then the confession that earns this page its subtitle: "I downloaded WD's drive utility app — before looking at the warning on your site not to use third-party apps, alas" — though the utility did report the drive's free and used space. And the stakes, stated with the same honesty: most of the really important material is backed up to the cloud or other drives, "but there's so[me]..." — a remainder that mattered. Every layer of that account gets its answer.

The decode: what the successful unlock proves, the heat theory audited — and the utility graded gently

The layers, walked in order, because his symptoms map them perfectly: a security-model Passport presents in stages — the enclosure's bridge enumerates (his did, on every machine), the vendor's unlock layer challenges and accepts the password (his did, every time), and only then does the computer get to ask the drive proper for its volume. His failure sits precisely at that third stage: past security, short of the volume — and the successful unlock is genuinely good news twice over. It proves the bridge and its security hardware healthy, and it proves encryption is not the barrier: the layer that scrambles and unscrambles his data is doing its job on demand, which means the recovery's target is the ordinary one — a drive whose substantive reads are failing in the media/firmware territory beneath — rather than a locked-vault problem. (The maker's utility, for all that he half-regretted running it, quietly seconded the diagnosis: capacity and used-space figures come from the drive's cheap identity records, so its report confirmed the pattern — identity serves, volume doesn't.) The heat theory, audited fairly: offered tentatively and dismissed gently — drives do fail thermally, but "stopped working soon after meeting my new laptop" is far more often the new-machine variant of the timing fallacy this archive keeps acquitting: the new Mac changed nothing except when he was watching; a drive already in quiet decline met a week of fresh attention, mounted twice on its remaining margin, and finished. No clicking simply means the failure lives in firmware and media rather than in the mechanism's louder parts. And the utility, graded with the warmth his self-catch deserves: the maker's own tool is among the gentler things a worried owner can run — read-mostly, no repair ambitions — and his instinct to check the site's guidance mid-download, then stop and write in, is the behaviour that guidance exists to produce. The warning stands (utilities aimed at failing drives ask failing hardware more questions), his single run cost approximately nothing, and a customer who reads the archive before finishing the install is the archive working.

The recovery — beneath the layers, with his keys

The recovery ran the layers in the order his symptoms had mapped: the security stage handled with his credentials so the unlock he'd proven a dozen times happened once more, on the bench's terms — and then the work went where the volume had been failing to come from. Through the USB Stabilizer on the PC-3000, the drive's firmware records were repaired and its failing reads brought under management, the imaging running cooperative territory first and the degraded regions last in bounded passes; coverage closed in the high ninety-nines, and the volume that three machines had waited for finally mounted — from the image. Verification then honoured his honest inventory: the not-elsewhere remainder — the material his backups didn't cover — was identified against his description, opened and confirmed first, with the already-safe majority extracted alongside as reconciliation. Delivery went out on new media in duplicate, the security question resolved per his preference on the recovered copy (protection is a choice again once the data is safe), and the report closing with the line his layered enquiry had earned: bridge healthy, security healthy, encryption never the obstacle — the drive beneath them simply finished, and the timing framed the new laptop for it.

Outcome

The remainder recovered, the layers reconciled, the new MacBook acquitted — and the filings his unusually self-aware enquiry earns. An unlock that works is evidence, not irony: security-layer success on a drive that never mounts localises the fault beneath encryption and marks the case as ordinary recovery territory — say it plainly in your enquiry, as he did, and bring your credentials; they're part of the method. Distrust new-device timing: drives that fail "soon after" a new machine, cable or dock have usually just finished on schedule in front of a fresh audience. And keep his mid-download habit: checking guidance before running tools — even catching it halfway, alas and all — is the difference between this page's gentle grading and the archive's harder ones. Most of the important stuff was backed up, he wrote. Now all of it is, twice — which is the only version of that sentence worth keeping.

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.