Data Recovery Case File · Apple Mac · The Backup on Night Shift

"Kirsk-kirsk-kirsk": a customer's onomatopoeia, a crash that may have caught the hourly backup mid-write — and the drive that was doing its job when everything stopped

The sound came transcribed, and customer transcriptions are better evidence than most people believe. His WD My Book 4TB had gone non-responsive after his Mac crashed overnight — invisible to the computer and to Disk Utility, though the maker's own utility "does pick it up, but none of its buttons do anything." On power it makes "an unhealthy 'kirsk-kirsk-kirsk' noise." And his timeline carried the detail that gives the case its register: the crash happened when the machine "probably wasn't actually using the drive... though it might have been doing its automatic Time Machine backup." He'd worked the maker's support checklist to its end — nothing changed. Ideas welcome, he wrote. Here are all of them.

Three decodes: the sound, the see-but-can't-touch utility, and the chicken-and-egg crash

The transcription first, with the commendation it deserves: "kirsk-kirsk-kirsk" — rhythmic, repeated, mechanical — is a customer's ear catching what the bench calls a recalibration loop: heads seeking, failing to read what they need, returning and trying again on a cycle; distinct from the sharp click of the classic death rattle, and diagnostic precisely because he wrote it down instead of calling it "a weird noise." (This archive's standing note: record or transcribe drive sounds — owners' onomatopoeia routinely narrows the fault class before the parcel arrives.) The utility paradox next: the maker's software "picks it up, but none of its buttons do anything" is the identity-versus-function split this archive meets weekly wearing a new coat — the drive still serves its cheap identity records, so the utility can list it, while every button presses a real operation into a mechanism that can't complete real reads; the checklist he then worked was honest effort against a fault no checklist reaches, and its silence was itself a finding. And the chicken-and-egg, handled fairly: his theory ran that the backup "pushed the processor over the edge" — but the likelier causality runs the other way. Time Machine works hourly, quietly, at scale; a drive entering failure stalls, and a Mac waiting on storage that stops answering hangs and dies exactly as his did overnight. The backup didn't kill the machine; the drive's decline, met mid-backup, hung the machine — the crash was the messenger, and the drive was already the story. Which sharpens the stake this page most wants named: the casualty was the backup itself — the drive holding the household's entire versioned history — and a dead backup drive deserves recovery urgency, not a shrug, because it is usually the only complete copy of everything in the house.

The recovery

At the bench the kirsk rhythm resolved into its authorship — a mechanism whose heads could no longer complete the reads its own start-up and every utility button required — and was retired with the donor and firmware attention the presentation predicted, under laminar airflow. The PC-3000 then did what no button could: imaged the full 4TB at patient tempo, coverage closing in the high ninety-nines, and the drive's real cargo rose from the image — the Time Machine backup structure intact, its long history of the Mac browsable back through its versions, verified by opening files across several restore points. Delivery on new media came with the register's specific guidance: the recovered backup restores exactly as Time Machine expects, the interrupted final increment (the overnight session the crash cut short) noted honestly as partial, and every earlier snapshot whole — the machine's past, saved by the thing that was saving it when the lights went out.

Outcome

Four terabytes of versioned history recovered — and the page's three lines for the archive. Transcribe the noise: his three syllables were worth a page of symptoms; owners' sound-reports are evidence, and the bench reads them. Vendor utilities that see but can't act are telling you the fault's depth, and the end of the support checklist is the beginning of the bench, not of despair. And backup drives die on duty: they work the hardest hours in the house, hourly and unwatched, and when one fails the correct reflex is the one he had — recover it — because "it was only the backup" is the sentence people say right before discovering it was the only complete copy of ten years. The Mac got a new destination that week; the delivery note's last line put a second one beside it, because the real moral of a dead backup is that backups need backups too.

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.