Portable drives · case file · SDR-2025-1131
It Powers Up and Spins, but Never Mounts.
A sailing photographer's G-Technology ArmorATD won't appear on my MacBook any more
, even though the LED still lights and I can feel it turning
. Inside the rubber shell: a Capture One catalogue and a season of Solent regatta RAWs, a year of billable work shut behind hardware that looks and sounds perfectly well.
Seeing the same thing yourself?
0800 6890668
The translation.
Light and rotation rule out the coarsest mechanical failures and push the problem further up the chain — towards the bridge, the firmware, or the structures macOS must parse before it will present anything at all. The catalogue adds its own condition. Capture One keeps its database apart from the RAW files it points at, so a job that returns every image but breaks that database hands a photographer a season of pictures with every adjustment gone.
Kit used on this job.
What happens in a case →| Platform | Its role in this case | Why we use it |
|---|---|---|
| ACE Lab PC-3000 Express | Proved the motor, heads and firmware sound before blaming the filesystem | Talks to drives using maker-specific commands beyond the ordinary ATA instruction set |
| PC-3000 Data Extractor | Took a full image, capturing the volume metadata ahead of the picture data | The PC-3000 platform's imaging unit, commanded by its firmware unit |
| UFS Explorer Professional Recovery | Interpreted the Mac volume and put the catalogue's folder tree back together | Handles the difficult filesystems better than most — APFS, ReFS, XFS, ZFS, Btrfs |
In the lab.
Rule the mechanism out before accusing the volume
Nothing was taken on trust just because the drive sounded healthy. Firmware answered as expected, the defect log held nothing unusual, and sample reads across each surface came back clean. That left the volume structures, not the hardware under them.
Capture the metadata before the pictures
Imaging order was deliberate: catalogue and metadata areas were secured ahead of the bulk RAW data, because those small regions decide whether an owner gets a working library back or just a heap of pictures with no history.
Put the volume back, then check the catalogue actually loads
The filesystem was rebuilt from the image, then the catalogue was launched and walked through to confirm it still resolved to the right RAWs with adjustments attached. A library that opens having forgotten every edit is half a job, and nobody discovers that unless somebody looks.
The result.
The catalogue and the RAWs came back with every adjustment attached, checked in the owner's own software before shipping. The one gap: the import running when the fault hit never finished writing, and nothing recovers data never stored.
Similar cases on the index.
Further cases in Portable drives.
Does this sound like your own drive?
The rule holds as in every case above: switch it off, and let a free diagnosis come before any decision.