Mac & Apple · bench notes · MHD-2025-6607
It Fell, and Now It Ticks Quietly.
Twelve years of drawings and site photographs sat on a drive that had slid from an open rucksack onto a kerb in Cookham, and because the case is wrapped in rubber its owner thought little of it. Then neither Mac would show it
. Held to the ear it gave one tick every few seconds, quiet enough to sound like nothing.
Much the same fault? Call us.
0800 6890668
In everyday terms.
Loudness is a poor witness. What decides how much noise a failing drive makes is the diameter of its platters, the mass of its chassis and, in a Rugged, a rubber sleeve fitted expressly to absorb sound, none of which has any bearing on your files. Underneath, a tick you can hardly hear and the bang from a full-size desktop unit are one behaviour: the head stack sweeping for a positioning reference it cannot locate, pulling back, then setting out again. Each sweep is another crossing of the surfaces your work is written on.
What the bench used here.
How a job is handled →| Tool | Why we used it | What it brings |
|---|---|---|
| DeepSpar Disk Imager 4 | Ranked every head once the donor stack was in, and fixed the read order | Head map first, then head-by-head reads, holding resets, timeouts and the power line steady |
| PC-3000 Data Extractor | Covered the platters band by band, each reset counted and logged | The PC-3000's imaging module, working under firmware-level control |
| UFS Explorer Professional Recovery | Rebuilt the HFS+ catalogue whole; Apple volumes are its strongest ground | Reads the awkward filesystems others stumble over: APFS, ReFS, XFS, ZFS, Btrfs |
The lab work.
Quiet or loud, the answer is the same
Nothing was powered up again until the drive was open on the bench. What came to light was the familiar damage in miniature: contact marks on the sliders where they had come down, and platters showing next to nothing for it. He had made two attempts and then left it alone, and that restraint is legible in how little there was to find.
Fit the correct heads before reading a byte
A stack lifted off a donor of the same family, built in the same period, went in, and every head was then surveyed. All of them read, although one lagged behind the others on the weak-read test, so that one was left until last and the imaging opened with the strongest.
Let HFS+ set the terms of its own rebuild
Everything HFS+ knows about a volume lives in its catalogue file, and lifting that cleanly out of the image is what decides whether you get an archive or a pile. The projects came back under their own names, ordered by year and with their dates intact, rather than thousands of nameless files to be sorted by hand.
How the job closed.
Nothing was missing. The check was to mount the rebuilt volume and open one job from the first year on it and one from the last, drawings and site photographs alike. A complete result was only available because the count of attempts stopped at two rather than twenty.
More of the jobs we've closed.
Other cases involving Macs.
Does any of that match your case?
Nothing needs deciding until the diagnosis is back: switch the device off, send it in, and let the findings settle it.