Case file · Portable drives · SDR-2025-0308
RAW Files on a Freshly Dropped Drive.
A professional photographer's field drive fell from the van tailgate onto concrete and came up hurt: it clicks then whirrs, over and over
, the light blinks fast
, and none of his machines are able to see or recognise it. As he states in his own words, on it are two years of shoots I haven't delivered
, the working part of a career.
Seeing the same thing yourself?
0800 6890668
The translation.
When a drive falls it will start clicking: the head stack hunts for the servo marks it cannot make sense of anymore, resets, then hunts again. The blinking light is the bridge board sitting there waiting for a drive that never reports itself ready. Both signs are obvious, and every power-up gets both of them at the cost of platter surface, so one of the smartest things he did was simply stop plugging it in.
Kit used on this job.
What happens in a case →| Which 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 were removed first; underneath them sits a standard 2.5in mechanism with a plain injury. Removing the bridge also removed its habit of cutting power as soon as the drive did not respond, which had been triggering a new spin-up attempt every single time he connected it.
Fit matched donor heads, then map them before reading a thing
The donor heads, matched on family and firmware revision, were then installed and the drive came up on the imager. Instead of reading data front to back, the initial step was to map the heads: which could read cleanly, which struggled, and where the damage lay. As one head clearly read weaker than the others, it was left out of the first pass altogether.
Best heads first, worst ground last, a single pass apiece
Imaging went to the strongest heads first, with short timeouts and managed power cycling, so we could bank as much healthy data as possible before asking anything of the injured surface. We used a slow sweep for the weak head's area at the end. The entire read took the better part of a week, which is the correct amount of time on a dropped drive: hasty recovery is what turns a recoverable archive into scored platters.
The result.
We checked every frame of the recovered archive at full resolution before final sign-off, opening and inspecting the RAW files rather than simply counting them. The same afternoon, the damaged drive was retired. 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.