Case file · Portable drives · SDR-2025-0308
RAW Files on a Freshly Dropped Drive.
A working photographer's field drive went off a van tailgate onto concrete and came up hurt: it clicks then whirrs, over and over
, the light blinks fast
, and no machine sees it. On it, in his own words, two years of shoots I haven't delivered
— the working end of a career.
Seeing the same thing yourself?
0800 6890668
The translation.
Clicking after a fall is the head stack hunting for servo marks it can no longer make sense of, resetting, then hunting again. The blinking light is the bridge board sitting there waiting on a drive that never reports itself ready. Neither sign is subtle, and each power-up buys both of them at the price of platter surface — which is why the most useful thing he did was stop plugging it in.
Kit used on this job.
What happens in a case →| Platform | Its role in this case | Why we use it |
|---|---|---|
| DeepSpar Disk Imager 4 | Built the head map first, so the injured head sat out the early passes | Head-map-driven imaging, with per-head timeouts, resets and power-cycle control |
| PC-3000 Data Extractor | Drove the imaging once the donor stack went in, zone by zone | The PC-3000 platform's imaging unit, commanded by its firmware unit |
| UFS Explorer Professional Recovery | Rebuilt the HFS+ volume off the image and checked each RAW file's structure | Handles the difficult filesystems better than most — APFS, ReFS, XFS, ZFS, Btrfs |
In the lab.
Take off the shell and the bridge, meet an ordinary patient
The rubber sleeve and the drive's own USB bridge came off first — underneath all that sits a plain 2.5in mechanism with a plain injury. Losing the bridge also lost its habit of cutting power the instant the drive failed to answer, which had been provoking a fresh spin-up attempt every single time he connected it.
Fit matched donor heads, then map them before reading a thing
Donor heads matched on family and firmware revision went in, and the drive came up on the imager. Rather than read front to back, the first task was to map the heads: which read cleanly, which laboured, and where the damage lay. One head was plainly weaker than its neighbours, so the opening pass left it out altogether.
Best heads first, worst ground last, a single pass apiece
Imaging went strongest-first with short timeouts and managed power cycling, banking the healthy bulk before asking anything of the injured surface. The weak head's territory was swept at the end, slowly. The whole read took the better part of a week, which is the right answer on a dropped drive — hurry is what turns a recoverable archive into scored platters.
The result.
The archive came back and was checked frame by frame at full size before sign-off, RAW files opened and inspected rather than merely counted. The drive was retired the same afternoon. Two years of undelivered work now sits on media that has never met a tailgate.
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.