Data Recovery Case File · Trust, Practice & Honest Limits · Erase It Before It Goes Back

The opposite of recovery: certified erasure of an unmountable warranty drive — why a Time Machine disk is your whole life in versions, how erase commands work below a broken filesystem, and the seals never touched

Most enquiries in this archive want data back; his wanted it gone — for the best of reasons, and with a constraint worth decoding. A 6TB G-Drive Pro, two years old, serving as the Time Machine backup for his iMac: "it suddenly stopped working — I could see the drive in Disk Utility but it was shown as unmounted; I could not re-mount it or re-format it." He's claiming under warranty and must return the drive to the manufacturer. His data is safe — "I have another backup" — so his concern is precisely the right one: "my main concern is to safely erase the data from the drive. Are you able to erase the data without physically disassembling the disc, which may invalidate the guarantee?" Yes — and this page explains the three things his excellent question contains: why a backup drive is the most privacy-dense object most people own; how a drive whose filesystem won't mount can nevertheless be commanded to erase itself, below the broken layer entirely; and what a verifiable, warranty-safe erasure actually looks like on paper.

The decode: the stakes, the mechanism, and the honest edge

Why a backup drive is the privacy problem, concentrated: the instinct behind his request deserves spelling out, because most people ship failed drives back without a thought. A Time Machine disk is not "some files" — it is a versioned copy of an entire computer's life: every document in every draft, every photo, mail archives, browser-era detritus, things deleted from the Mac years ago but faithfully retained in the backup's history. Returned readable, it hands that totality to whoever handles the RMA stream — refurbishers, recyclers, unknown downstream custody. And the cruel twist his case captures: the drive won't mount, so he cannot erase it himself — the failure that triggers the warranty claim is the same failure that locks the owner out of his own housekeeping. That trap is exactly what professional sanitisation exists for.

How an unmountable drive erases itself: the mechanism is the page's central decode. Mounting is a filesystem-layer act — the operating system parsing the volume's structures — and his drive fails there. But erasure doesn't live at that layer: drives implement secure-erase as firmware-level commands, executed by the drive's own controller against the raw media, entirely indifferent to whether any filesystem parses. A drive that enumerates in Disk Utility (his does) is a drive answering commands at the drive level — and a drive answering commands can, in the typical case, be instructed to sanitise itself end to end: the controller overwriting or purging every sector, broken volume and all. No opening, no platters touched, no seals disturbed — the enclosure never even needs its screws counted. The erasure then gets what a warranty return deserves: verification — the drive re-read in sampled passes across its span, the emptiness confirmed and hashed, and a written certificate of erasure issued: the document that turns "I wiped it, honest" into paperwork an RMA can travel with.

The honest edge, stated in advance: one boundary belongs on the page: this route requires the drive to accept commands, which his — visible, enumerating — evidently does. A drive too far gone to respond at the command level can't be told to erase itself, and the honest options there are narrower: manufacturer-side destruction assurances, accepting residual risk, or physical destruction that forfeits the claim — a trade-off laid out plainly if ever reached, decided by the owner with the facts. His drive never reached it; most in his position don't.

On the bench

The drive was assessed on the Atola TaskForce 2 — command responsiveness confirmed exactly as its Disk Utility visibility had promised — and the sanitisation ran at firmware level: the secure-erase executed by the drive's own controller across all six terabytes, below and indifferent to the volume that wouldn't mount, the enclosure sealed and untouched throughout. Verification followed as discipline, not ceremony: sampled read-back across the span, the erased state confirmed and recorded, and the certificate of erasure issued in writing — drive identifiers, method, date, verification summary. The G-Drive left for its warranty return exactly as the manufacturer expects to receive it physically, and exactly as its owner needed it to be digitally: intact outside, empty inside, and documented as both.

The outcome

The unmountable drive securely erased at firmware level, verified by read-back, certificated in writing, and released to its RMA with warranty seals untouched. One fixed written figure including VAT for the sanitisation service. The doctrine his foresight writes for every warranty claim: a backup drive is your whole digital life in versions and should never travel readable; a drive that won't mount can still usually be commanded to erase itself, because sanitisation lives below the filesystem; and the deliverable to insist on is the certificate — erasure you can hold, attached to hardware you never had to open.

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.