Data Recovery Case File · Apple Mac · The Clone That Wouldn't

"It identifies a mechanical error" — her cloning utility told the truth and stood down: the software ceiling decoded above the tool, not against it, and 2.5TB brought across the hardware way

Her enquiry opened with the instruction it repeated at the close — "please email rather than call" — honoured, both times, in full. The situation: a 5TB Western Digital external, Mac-formatted, 2.5TB in use, and a precise symptom set: "I am unable to copy any of the files off… onto my Mac, or onto another external hard drive. It is extremely slow, or crashes after one or two files. I can see the files within Finder, so I know they are there — I just can't move them." Then the detail that lifts this case above the genre: she escalated to exactly the right species of tool — a whole-disk cloning utility — and it did something more honest than fail: "it identifies a mechanical error" and declined the job. Her goal was stated with the same clarity: everything off, onto another drive, to keep. This page's decode is owed to that cloning utility as much as to her: it diagnosed correctly, refused correctly — and its refusal marks the exact altitude where software ends and this bench begins.

The decode: why the visible files wouldn't move, and why the right tool still couldn't

The tease, restated for this volume: these files have met the pattern before — a catalogue that lists everything over contents that won't come — and the mechanics hold here: showing the folder tree needs only short, well-worn reads of the volume's table of contents; moving 2.5TB demands long expeditions across the whole surface, exactly what a mechanically faltering drive can no longer sustain. One or two files, then a crash: the expedition setting out, and failing at the first difficult territory.

Her escalation, graded at full marks: reaching for a cloning utility instead of dragging folders is the capable owner's move — clone-the-disk is the right shape of answer, and this archive recommends the instinct. And her tool's response deserves its credit spelled out: it inspected, identified a mechanical error, and refused to grind a failing mechanism through a doomed pass. That is a well-behaved tool protecting a patient — a better outcome than the utilities elsewhere in these files that thrashed ahead and made things worse.

The ceiling, drawn precisely: here is why even the right software stops where hers did. A software cloner works through the operating system, over a consumer connection, against a drive it cannot manage — it can't tune timeouts per region, can't rest the mechanism, can't reorder the harvest around weak heads, and must largely take the drive as the OS presents it. Hardware imagers invert every one of those limits: native access below the operating system, per-region patience, head-aware sequencing, the harvest banked in the drive's good spells and paused in its bad ones. The cloning utility's "mechanical error" wasn't defeat; it was a correct referral upward — the software man's honest ceiling from elsewhere in this volume, spoken this time by the software itself.

The recovery: the clone she wanted, made the hardware way

Out of its enclosure and onto native connections, the drive confirmed the tool's diagnosis — a mechanism weakening at sustained reads — and was given to hardware imagers: catalogue-guided so the in-use 2.5TB led the harvest, head-aware and unhurried, difficult regions revisited with patience rather than force. The image completed across the drive's spells; the volume mounted from the copy exactly as Finder had been promising all along; and the estate was written to her destination drive and verified — folders opened, files sampled across the span, the "I know they are there" finally converted into "and here they are."

On the bench

This case's whole decode was the ceiling between software cloning and hardware imaging, so here is the floor above it, itemised. Data Extractor on the PC-3000 read the drive with per-sector timeouts measured in milliseconds rather than the operating system's patient minutes; issued vendor-level read commands that bypass the drive's own retry theatrics; skipped forward at the first sign of a struggling region and returned in later passes with different parameters; and built a sector map distinguishing read, weak and dead territory in real time. Her cloning utility could do none of that — not as a flaw, but as a boundary — and its honest refusal is why the drive arrived with enough life left for the layer that could.

The outcome

Two and a half terabytes delivered onto new media to keep, precisely as she'd scoped — the whole exchange, from first assessment to final manifest, conducted by email as twice requested. Free assessment, one fixed written figure including VAT, no recovery, no fee. And a closing line for the tool that knew its limits: software that says "mechanical error — not my job" has told you the truth and the address of the next step. Hers had both right.

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.