Data Recovery Case File · Portable Drives · The Paradox Result

Passed the quick test, passed the extended test, read nothing: a diagnostic paradox explained

This customer's troubleshooting was methodical to a fault — and it produced a result that would confuse anyone. His 2014-era 1TB My Passport, reliable until a month prior, now made a soft "tic tic" with its light flashing and appeared nowhere as a readable drive; three laptops, both operating systems and multiple cables agreed. Disk Management showed it at 0 bytes offering only "initialise" — declined. And then the paradox: the manufacturer's own diagnostic tool ran its quick test, and its extended test, and the drive passed both. His conclusion — "I think the HD is still working, I'm not keen to try anything else" — was half right, and the restraint in the second half saved the case.

How a dead drive aces its exams

The resolution to the paradox is what a desktop diagnostic can actually reach. When a drive fails to present any readable surface, the vendor tool's "tests" are conversations with the parts still answering — the electronics, the firmware's front desk, the drive's own self-reported health registers — and a drive whose heads have failed can hold that conversation flawlessly: electronics pristine, registers unbothered, every question the tool can pose answered politely by components that were never the problem. "Pass" meant the parts I could reach responded; it carried no information about the one ability the drive had lost, because testing that requires the very reading the drive couldn't do. Meanwhile the soft tic-tic was the actual report, filed by the actual patient: heads attempting their opening reads on a gentle rhythm and failing, the 0-byte listing the bridge's placeholder for a disk that never introduced itself. His two conclusions thus split cleanly — "still working" was true of everything except the part that mattered; "not keen to try anything else" was correct about everything full stop.

The recovery

The bench agreed with the ticking over the test results: heads degraded past their duties above platters kept clean by a month of restraint. A donor head-stack went in under laminar airflow; firmware and the family's key material were secured over the PC-3000 through the USB Stabilizer; and Data Extractor imaged the rebuilt drive head by head in the archive's patient rhythm, hardware encryption resolved with the drive's own keys as coverage closed in the high ninety-nines. The volume he'd been locked out of for a month mounted from the image intact; his data was verified and delivered on new media.

Outcome

Effectively complete recovery — and a rule worth carrying out of the paradox: a diagnostic can only examine what it can reach, and a "pass" from software is a statement about the conversation, not the drive. Believe the physical evidence over the certificate: a drive that ticks, shows 0 bytes, and mounts nowhere has told you its condition in its own words, whatever its exam results say. And when the evidence and the tools disagree, do what this customer did — stop testing, start preserving, and let the tiebreak happen on equipment that can reach all the way in.

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.