Case file · Mac & Apple · BDR-2025-0607
Dropped, and Now Only a Slight Click.
After the drop, the drive cannot open
— no icon on the Mac's desktop, and when plugged in, a click so slight the owner allowed herself hope: surely a quiet noise meant mild damage? It wasn't a loud, horrible sound. Perhaps it was nothing much.
Same symptoms on your desk?
01273 964902
The decode.
The kindest thing a diagnosis can do is decline to flatter. A click is the head stack failing to find its reference and recalibrating — the acoustics depend on the drive's form factor, its mounting and how much of the noise the enclosure absorbs, not on how much damage has been done. A whispering clicker and a hammering one are the same patient, and both are consuming platter surface with every attempt.
Equipment on this case.
How a case runs →| Platform | What it did here | Why this tool |
|---|---|---|
| DeepSpar Disk Imager 4 | Head map after donor heads, then imaging ordered by head health | Head-map-aware imaging with per-head timeout, reset and power-cycle control |
| PC-3000 Data Extractor | Managed the read passes with per-zone strategy and controlled resets | The imaging half of the PC-3000 platform, driven by the firmware half |
| UFS Explorer Professional Recovery | Rebuilt the Mac volume — APFS and HFS+ structures both handled natively | Stronger than most on the awkward filesystems — APFS, ReFS, XFS, ZFS, Btrfs |
On the bench.
Take the quiet click as seriously as a loud one
The drive was opened and the head stack inspected before any further power was applied. The damage was real, if modest: contact marks on the head sliders and no meaningful damage to the platters — the pattern you get when someone stops trying early, and the reason her instinct after the second attempt was worth more than she realised.
Matched donor heads, then map before reading
A donor stack from the correct family and generation was fitted and a head map built. All heads returned to service, with one reading slightly weaker than the others — imaging was ordered accordingly, strongest first.
Rebuild the Mac filesystem, not a generic one
Mac volumes reward being read by something that genuinely understands them. The container and its structures were parsed properly from the image rather than carved blindly, which is what preserves the folder hierarchy, file names and dates instead of returning a heap of anonymous documents.
The outcome.
Everything returned, verified by opening the recovered volume through the owner's own machine. Her decision to stop trying after the second attempt is what kept 'everything' available as a word.
Related on the index.
More from Mac & Apple.
Recognise your own drive in this story?
Same rule as every case above: power it down, and let the diagnosis be free before any decision has to be.