Portable drives · case notes · EDR-2025-3131
Spinning, Lit, and Never Mounting.
Roughing it through three Torbay wedding seasons had got the ArmorATD used to travelling, unplugged in a hurry from venue to venue. It was the Monday after a christening when the ArmorATD refused to work: greyed out in Disk Utility, and it won’t mount
(both the studio iMac and her partner’s MacBook agreed), although it spins and the light comes on like always
. Behind the ArmorATD’s bumper were the Capture One catalogue and a year’s worth of clients’ RAWs.
Sound familiar? Talk to us.
0800 6890668
In plain English.
Spin-up and a lit LED will only answer the inexpensive questions. On top of these are the bridge, the firmware and the volume structures which macOS must process prior to offering a disk for use, and one destroyed structure here prevents an otherwise good drive from being shown. The catalogue raised the stakes even higher: Capture One stores each photo edit in a database located separately from where the RAWs themselves are kept. Therefore a recovery that can find the pictures but loses that database will be handing back one year's worth of weddings without 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 identify a physical issue with the drive, but it could not find any indication of one: the firmware replied promptly, the defect list was ordinary, and all the sampled reads were clean (under every head). Therefore, as no evidence of a physical fault was found, the next layer of possible errors was evaluated: the structures a Mac interprets before it will mount anything.
Small regions first: the metadata outranks the terabytes
The imaging was ordered by design: the catalogue database and the volume structures were sent to safe storage first, before the terabytes of RAWs. A few gigabytes determine whether a working library comes home or a mess of orphaned frames, so they moved to the front of the queue.
Rebuild it, then run it as she would
Once the volume had been pieced together from the image, testing it simply involved using it: Capture One was opened and the sessions loaded against the recovered catalogue, then samples of the edited images were compared to their original RAWs. A library that has quietly shed its adjustments still passes every file count going, and this is why a file count was never used as an evaluation metric.
How it ended.
The catalogue and the RAWs went home with all adjustments still intact, as this had been proven in her own software prior to dispatch. The one loss was stated clearly: the christening import was mid-write when the volume failed, and no recovery will restore data that was never written to disk.
More like this in the casebook.
More cases from Portable drives.
Sound like your drive?
Each case here points to the same decision-making process: shut down the device, take the free diagnosis, then make your decision.