Data Recovery Case File · Desktop Externals & Aging Drives · Most of the Work Already Done

Arriving With the Cheap Causes Eliminated

His enquiry is short and has more diagnostic work behind it than most. An external drive no longer working: "it appears to be spinning, and there are no alarming noises. I have removed it from its enclosure and tried a different connector, to no avail." Three findings in two sentences, and the third is the one almost nobody produces. Taking the drive out and connecting it natively eliminates the enclosure, its bridge board and the entire external interface at once — though it is worth saying that it also carries a risk he happened to avoid.

The decode: what he has ruled out, and the risk in doing it

What rotation establishes: the motor works, the bearing turns freely, and the drive has power. That removes the family of faults where a drive cannot start at all.

What the absence of noise establishes, and it is worth reporting deliberately: people describe what they hear and almost nobody describes what they do not. Silence during rotation is a real finding — it rules out clicking (heads failing to position), straining and beeping (a motor unable to turn a stack), grinding (physical contact with the surfaces), and a periodic tick (a timed retry cycle). Four whole fault families eliminated by a negative observation.

What the native connection establishes, and this is the valuable one: connecting the bare drive directly removes the enclosure's bridge board, its power arrangement and the external interface in a single step. Those are among the commonest causes of an external drive appearing dead — and they are also the cheapest to fix, so ruling them out changes both the diagnosis and the likely cost. Most enquiries in this archive arrive without this test having been done.

What is left after all three: a drive that spins normally, sounds correct, and does not identify itself on a direct connection. That is the configuration and readiness family — most often an inability to read its own service area, the reserved region holding firmware, defect maps and geometry which must be read on every start-up before the drive can announce what it is. The user data is untouched by that, and it is addressed in the drive's technological modes.

Now the caveat, because the test he ran is not universally safe. Some external enclosures perform encryption in the bridge board rather than on the drive. On those, the drive removed from its case reads as meaningless data no matter what it is connected to — and worse, somebody unaware of that can conclude the drive is unrecoverable when it is perfectly fine inside its own enclosure. The enclosure should always be kept, never discarded, and where a drive shucks to nothing readable the possibility of interface-level encryption should be checked before any conclusion. He appears to have avoided this, but it is the reason the test is not advice for everyone.

On the bench

The owner's eliminations were taken into account — rotation, absence of unusual acoustics, and a direct native connection between them ruling out the motor, four acoustic fault families, and the enclosure's bridge and interface. The enclosure was retained and checked for interface-level encryption, since some perform encryption in the bridge and a drive shucked from one reads as meaningless data regardless of its condition. The readiness sequence was read directly under strict timeouts, with PC-3000 Express technological-mode service area assessment and imaging on restored addressing.

The outcome

The owner's eliminations taken into account, the enclosure checked for interface encryption and the service area repaired before imaging. Free assessment, one fixed written figure including VAT; where a drive has to be opened, 50% of parts and labour is payable upfront with the balance only on success — otherwise no recovery, no fee. The decode: connecting the bare drive directly is the elimination most people never do, and it removes the enclosure, its bridge and the interface at once. Reporting that there were no unusual noises rules out four more families. One caution though — keep the enclosure, because some perform the encryption themselves.

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.