Case file · Portable drives · BDR-2025-0308
A Dropped Drive Full of RAW Files.
In the middle of a trip, the professional photographer's travel drive hit the floor and quit on him; it makes a clicking and whirring noise
, the lights also flash rapidly
, but there is no connection to be made. On this device, in his words, a vast bulk of my RAW image portfolio
, the main body of work from his career as a photographer.
Same symptoms on your desk?
01273 964902
The decode.
After dropping the drive, the clicking you hear is "head stack hunting" because the drive cannot resolve the servo data it needs and so keeps hunting for it; at this point it will re-calibrate and then begin hunting for servo info again. The fast flashing LEDs indicate that the bridge board is waiting for a disk that does not report itself ready. Both symptoms are quite obvious and both damage the platters every time the drive is powered up, which is why the best thing the owner did was stop constantly trying to plug it back into their system.
Equipment on this case.
How a job runs here →| The system | What it did on the day | Why this tool |
|---|---|---|
| DeepSpar Disk Imager 4 | Head map built first, so the damaged head could be excluded from the initial passes | Head-map-aware imaging with per-head timeout, reset and power-cycle control |
| PC-3000 Data Extractor | Ran the imaging once donor heads were fitted, with per-zone read strategy | The imaging half of the PC-3000 platform, driven by the firmware half |
| UFS Explorer Professional Recovery | Rebuilt the exFAT volume from the image and validated the RAW files by structure | Stronger than most on the awkward filesystems — APFS, ReFS, XFS, ZFS, Btrfs |
At the bench.
Strip the wireless layer, find a standard patient
First the Passport Pro's wireless electronics and battery were pulled off, and underneath there sat a normal 2.5 inch drive with a normal problem. Removing that layer also eliminated the bridge board's habit of turning off power the instant the drive failed to respond, which had caused repeated spin-up attempts each time it was connected.
Matched donor heads, then a head map before anything else
When we installed a donor head stack from the same family and firmware generation and brought the drive up on the imager, rather than reading from front to back, the first task was creating a head map. Which heads worked well? Which were weak or difficult? Where exactly was the damage? One of the heads was much less capable than the others, so we completely excluded it from our first round of recovery efforts.
Strongest heads first, weakest zone last, one pass each
Imaging was done head-good-first, using tight timeouts and careful power-cycling, so the healthy majority of the disk could be banked first, without asking anything of the damaged surface. The weak head's sections were scanned last, at lower speeds. The total amount of time taken to read through all data ran into days, which is the right answer on a dropped drive. It is the speed of reading that turns a recoverable portfolio into scored platters.
Where it ended up.
The recovered portfolio was verified image-for-image at full resolution before being signed off, not just counted; the RAW files themselves were also checked for structural integrity. The drive itself was retired on the spot, and a career's worth of photographs are now stored on media that has never been dropped.
Related on the index.
More from Portable drives.
Recognise your own drive in this story?
As always: turn the device off, and let the diagnosis be free before you make any decision about what to do next.