Portable drives · case notes · EDR-2025-3131
Spinning, Lit, and Never Mounting.
Three Torbay wedding seasons taught the ArmorATD to travel rough, unplugged in a hurry between venues. The Monday after a christening it refused: greyed out in Disk Utility, and it won’t mount
— studio iMac and her partner’s MacBook agreeing — though it spins and the light comes on like always
. Behind the bumper: the Capture One catalogue, a year of clients’ RAWs.
Sound familiar? Talk to us.
0800 6890668
In plain English.
Spin-up and a lit LED answer only the cheap questions. Above them sit the bridge, the firmware and the volume structures macOS has to parse before a disk is offered — and one wrecked structure there keeps an otherwise healthy drive invisible. The catalogue raised the stakes further: Capture One holds every edit in a database kept away from the RAWs themselves, so a recovery that returns the pictures but loses that database hands back a year of weddings stripped of their adjustments.
The tools this job took.
See how your case runs →| System | The part it played | Why we rate it |
|---|---|---|
| ACE Lab PC-3000 Express | Checked motor, heads and firmware thoroughly enough to rule all three out | Talks to a drive through the maker's own commands, not just standard ATA |
| PC-3000 Data Extractor | Captured the full image with the small structural regions taken first | The PC-3000's imager, taking its orders from the firmware side |
| UFS Explorer Professional Recovery | Decoded the damaged Mac volume and set the catalogue’s folders back in order | Handles the harder filesystems well — APFS, ReFS, XFS, ZFS and Btrfs |
On the bench.
Let the hardware clear its own name
The bench set out to find a physical fault and could not raise one: firmware replies prompt, defect list ordinary, reads sampled under every head clean. So blame moved up a layer, to the structures a Mac parses before it will mount anything.
Small regions first: the metadata outranks the terabytes
Imaging ran to a deliberate order: catalogue database and volume structures to safe storage first, the terabytes of RAWs after. A few gigabytes settle whether a working library comes home or a heap of orphaned frames — so they jumped the queue.
Rebuild it, then run it as she would
With the volume reassembled from the image, testing meant using it: Capture One opened against the recovered catalogue, sessions loaded, a sample of edits compared against their RAWs. A library that has quietly shed its adjustments passes every file count going — which is why a file count was never the test.
How it ended.
Catalogue and RAWs went home with every adjustment still in place, proven in her own software before dispatch. One loss was named plainly: the christening import was mid-write when the volume died, and no recovery returns data that never reached the platters.
More like this in the casebook.
More cases from Portable drives.
Sound like your drive?
Every case here points the same way: power the device down, take the free diagnosis, then make your decision.