Data Recovery Case File · Apple Mac · The Universal Stall
Sounds healthy, halts everything: a drive that froze Finder, emptied Disk Utility, and hung Terminal — decoded and imaged past its own silences
His symptom ladder descended through macOS one rung at a time, and the bottom rung is the diagnosis. The 1.5TB Seagate, HFS+-formatted, got stuck mid-way through being backed up to his NAS; after an unplug-replug it mounted fine — then browsing the directories "seemed to lock Finder up." Now: no partitions shown in Disk Utility at all; and the last resort, diskutil list in Terminal, does find the drive — "but halts Terminal too." His closing observation completes the picture from the other side: "it still sounds healthy when I turn it on, no loud clicks or anything like that." A drive with a clean soundtrack that freezes every tool from Finder down to the command line is telling one consistent story, and it's not the one the silence suggests.
| Device | Seagate 1.5TB external, HFS+ — failed mid-backup to a NAS; archive drive being copied off |
| Reported ladder | Backup stalls → replug → mounts, then Finder locks on browsing → Disk Utility shows no partitions → diskutil list finds the drive but hangs Terminal → mechanically quiet throughout |
| Fault class | Degraded media/firmware serving reads late-or-never — every layer of macOS waiting politely on answers that don't come |
| Equipment used | DeepSpar USB Stabilizer 10Gb · ACE Lab PC-3000 Express + Data Extractor (HFS+ reconciliation) |
Why one slow drive freezes every tool — the stall decoded
The unifying mechanism behind his whole ladder: storage requests in an operating system wait. When software asks a drive for data, the request doesn't fail fast — it queues, patiently, while the drive retries internally — and a drive whose degrading surfaces or firmware serve some reads eventually and some never becomes a tar pit that captures every tool which touches it, each at the layer it asks from. Finder locked because browsing reads directory structures, and a directory read stalled; Disk Utility showed nothing because enumerating partitions requires reading the partition tables, and those reads never returned to populate the window; and diskutil list — the revealing rung — found the drive (the device level, cheap identity queries, still answering) and then hung, because listing means reading the same stuck tables. One fault, four presentations: device present, data territory stalling — localised, by his own methodical descent, more precisely than most bench reports manage. Two footnotes his account earns. The quiet soundtrack is genuinely meaningful — no clicks means the mechanism isn't failing catastrophically; this is the slow fault family, media and firmware degradation, which stalls rather than crashes and images beautifully under managed reading. And the timing is this archive's oldest pattern wearing Mac clothes: the failure surfaced mid-backup because the backup was the marathon — a full sequential read of an ageing archive drive is precisely the workout that finds the wear light use skated over. The rescue attempt didn't break the drive. It examined it.
The recovery
The bench replaced polite waiting with managed insistence: on the PC-3000 through the USB Stabilizer, the drive's internal retry theatrics — the machinery behind every frozen window — were retired, its degraded firmware records repaired, and imaging ran the patient order across the 1.5TB: cooperative territory banked at pace, the stall-prone regions (the partition tables and directory structures his tools had queued on, prominently among them) negotiated last in bounded, error-managed passes that take an answer or take a boundary, never an infinite wait. Coverage closed in the high ninety-nines. The HFS+ volume reconciled whole on the image — directories browsable in an instant, the very act that froze Finder now trivial against healthy media — and the interrupted backup was completed by other means: his archive verified, delivered on new storage, and copied onward to the NAS that had been waiting since the stall, the original errand finally run.
Outcome
Full recovery of a drive that never made a wrong sound — and the pattern filed for every Mac owner descending the same ladder. Quiet-but-stalling is its own fault family: when Finder freezes on browsing, Disk Utility draws blanks, and even Terminal hangs on the listing, the drive is present and its data territory is failing to serve — stop descending at that point, because every further tool queues on the same stuck reads, and each session works the failing regions harder. Force-eject cleanly, power down, and note the ladder you climbed (his four-rung account was half the assessment). And the timing lesson, one more time for the archive's running tally: drives disproportionately fail during the backup that would have saved them — which is an argument for backing up earlier, never for backing up less.
Drives that hang every tool including Terminal
Stop at the first universal stall — Finder, Disk Utility and diskutil are all queueing on the same failing reads, and repeat attempts just re-run the tar pit. Don't force repairs with First Aid or third-party tools; they read (and write) the exact territory that's stalling. Note which layers hung and in what order — the ladder localises the fault — and let the drive be imaged with reads that take boundaries instead of waiting forever. Quiet drives from this family recover extremely well. The silence was never the problem.
That's a stall, not a loss — call Belfast Data Recovery on 028 9002 0144 before another tool joins the queue.
Request a quote online →
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.