Portable hard drives · job record · PLY-2025-1131
Powered, Turning, and Absent From Every Desktop.
The wedding was on Saturday. Come Tuesday the drive would do no more: the icon turns grey and no volume ever appears
. What her assistant’s MacBook reported, the studio iMac reported too. All the while, it has power, it turns, the light behaves exactly as normal
. Beneath the orange bumper lay twelve months of RAW files shot for paying clients, together with the Lightroom catalogue that records what was decided about each of them. Take the database away and only frames remain. The Rugged Mini had spent two working seasons inside a Kingsbridge photographer’s bag, and a good few jobs had finished with someone pulling a cable free in a car park with no lights on.
Sounds like yours? Talk it through.
0800 6890668
Why it happens.
Rotation and a lit LED get you past the first of four hurdles. A USB bridge sits above the motor. Above that sits firmware. Above both sit the volume structures, and macOS insists on reading those before an icon reaches the desktop. Damage any one layer and a perfectly good mechanism might as well be absent. The catalogue is what raised this above a routine disk job. Lightroom does not write crops, corrections or star ratings into the pictures at all — they live in a separate database. Give back the RAW files alone and she has twelve months of shooting with every edit removed.
The kit this job called for.
How the job runs →| The kit | What it did here | Why we keep it |
|---|---|---|
| ACE Lab PC-3000 Express | Ran motor, heads and firmware hard; not one of them gave any trouble | Drops the disk into its maker's service mode, out of reach over plain ATA |
| PC-3000 Data Extractor | Copied everything, putting the small structural regions in front of the bulk | The PC-3000 runs the copy through the drive's own firmware |
| UFS Explorer Professional Recovery | Repaired the broken Mac volume, then straightened out the catalogue’s folder tree | Mounts what other software will not: APFS, ReFS, XFS, ZFS and Btrfs volumes |
How it ran.
Clear the hardware first
A search for physical damage turned up nothing worth writing down. Firmware replied when asked. The defect list contained no surprises. Test reads from every head came back clean. That places the fault further up — in the record-keeping a computer has to work through before it will offer you a volume.
Copy the most valuable part ahead of the rest
Reading order was decided before a single sector moved. Volume descriptors and the catalogue database went into safe storage at the head of the queue, and the terabytes of RAW files followed them. Those few gigabytes are what separates an archive she can open and work inside from a heap of loose frames.
Then use it the way she would
A rebuilt volume gets worked in here, not merely inspected. Lightroom was aimed at the recovered catalogue and the collections appeared. Several edited frames were put alongside the originals beneath them and compared. A library that has quietly shed its edits will still give you the right file count.
How it ended up.
Catalogue and RAW files went back together, adjustments still attached, tested inside her own editing software before anything was packed. One loss has to be recorded, and the report states it in the opening line instead of somewhere lower down: when the structures failed the Saturday import had been written only half way, and no platter can produce data that never landed on it.
Pages people open after this.
Other cases from the pocket-drive file.
Seeing the same thing?
Leave it switched off and post it in. Nothing happens until the diagnosis, which lists what can still be read and what cannot.