Case record · Mac & Apple · SDR-2025-0621
It Mounted Slowly, So I Pulled It Out Too Soon.
Eleven years of lesson recordings were stored on one Mac drive, with a house move in between. It did appear, after four or five minutes
, with everything else frozen while it decided what to do, so she unplugged the drive. Now it won't show up at all
, and First Aid says it can't be repaired
. There is no backup.
Seeing the same thing yourself?
0800 6890668
The translation.
The slowness was itself the diagnosis. When you mount a volume on macOS, it has to read the catalogue of information about each file on the volume before it can do anything else. If there are problems reading this catalogue due to a slow or malfunctioning disk, the Finder will be waiting for these reads to complete before it continues. This is when you see the spinning beachball. So, the delay belongs to the disk, and not to an uncooperative Mac. Then, First Aid makes matters worse in one particular way: it repairs file systems, and if First Aid finds any errors, its response is to write. It writes data to a disk that may already be quietly failing. This reaction from First Aid is the exact opposite of what should happen.
Kit used on this job.
What happens in a case →| Which platform | Its role in this case | Why we use it |
|---|---|---|
| DeepSpar Disk Imager 4 | Imaged on cautious settings, with no further mounting allowed first | Head-map-driven imaging, with per-head timeouts, resets and power-cycle control |
| UFS Explorer Professional Recovery | Read the HFS+ volume out of the image with its catalogue intact | Handles the difficult filesystems better than most — APFS, ReFS, XFS, ZFS, Btrfs |
| ACE Lab PC-3000 Express | Firmware-level checks established that the surface fault was spreading. | Talks to drives using maker-specific commands beyond the ordinary ATA instruction set |
In the lab.
No further mounting, and First Aid retired
The drive left the kitchen table and stopped meeting operating systems altogether. Firmware-level checks indicated a spreading surface fault, and most of the damage was located right at the point HFS+ uses to store the catalogue, which accounts for both the four-minute mount and First Aid giving up.
Take the catalogue areas first, and gently
The imaging process occurred in a very specific order. The metadata area was completed first, and slowly, because metadata is used to convert raw sectors into names for recordings stored in dated folders. After the metadata, the bulk audio was imaged. Unplugging the USB cable early had interrupted one read, but it resulted in no loss beyond that.
Rebuild the Mac volume off the copy
The filesystem was rebuilt from the finished image rather than being patched where it lay, and that is the difference between eleven organised years and eleven thousand nameless files. The folders, filenames and dates survived alongside the audio.
The result.
The recordings came back in their original folders, checked on her own Mac before sign-off. Nine audio files from the weakest band returned truncated, and were listed as such.
Similar cases on the index.
Further Mac & Apple cases.
Does this sound like your own drive?
As in every case above, the rule holds: switch it off, and let a free diagnosis come before any decision.