Apple machines · bench record · HUL-2025-0607
A Tick, Then Silence, Then Another Tick.
The rucksack had not been closed, and the drive dropped out onto the kerb on Lowgate. A rubber shell tempts you to think nothing of it. Twelve years of site photographs and drawings were on it. Then neither of my Macs will mount it
, and held up to his ear, a tick, a few seconds of nothing, then one more — quiet enough to talk yourself out of.
Sounds like yours? Ring us.
0800 6890668
What causes it.
The noise tells you about the box, not the damage. A 2.5in platter pushes less air about than a 3.5in, a light shell carries the sound less well, and a Rugged wears rubber precisely to deaden knocks and noise. None of that changes what is on the platters. Strip the shell off and the faint tick and the thump of a big desktop unit turn out to be the same thing happening: heads hunting for a servo mark, missing it, backing off, going again. Every one of those attempts drags them over the surface your files are written on.
The tools this one needed.
The steps we follow →| The gear | What this one did | Why we have it |
|---|---|---|
| DeepSpar Disk Imager 4 | Scored each new head after fitting and set the reading order from that | Grades each head first, reads one surface at a time, and keeps resets, timeouts and power under control |
| PC-3000 Data Extractor | Worked through the surface band by band, logging every reset | Copying is run at firmware level, with the PC-3000 in charge |
| UFS Explorer Professional Recovery | Put the whole HFS+ catalogue back — safer than carving on an Apple volume | Opens the volume formats most tools cannot: APFS, ReFS, XFS, ZFS, Btrfs |
The stages.
Quiet or loud, it is treated the same
It was not powered again until it was open under a lamp on the bench. The damage was the ordinary kind, on a smaller scale: contact marks on the sliders where they park, platters all but clean. He had tried twice and then stopped, and the reason there was so little to photograph is that he stopped.
Get the heads right before reading anything
The donor was matched on family and on the production window it came from. With its stack fitted, each head was tested on its own. Every one of them read, but one read measurably weaker than the rest, so it was left until last and the pass started with the best of them.
Give HFS+ back the structure it expects
HFS+ holds its whole index in a single catalogue file. Lift that off the image in one piece and an archive comes back as an archive. Miss it and the customer gets a heap. His jobs came back named, filed by year, with the dates they were recorded under — not a folder of numbered files to be opened one at a time.
How it finished.
Nothing was short. The rebuilt volume was mounted and two jobs opened from it, one from the earliest year on the drive and one from the most recent — photographs in the first, drawings in the second. It survived because two attempts were made, not twenty.
What people read after this.
Other cases on Apple machines.
Is yours doing the same?
Turn it off. Send it to us. The diagnosis comes first. It says which files are still readable and which are not.