Pocket drives · case on file · BHD-2025-8308
One Drop, One Tick, Two Seasons Home.
Nothing else held the originals. Edited JPEGs had gone out to clients and been cleared off the laptop long before, so two seasons of wedding work lived on one pocket drive — the one that slid out of a half-zipped bag onto a Bromsgrove driveway. It ticks six or seven times and then stops
, and the blue light comes on, and that is the lot
. On it: every raw file from two seasons of weddings
.
Sounds like yours? Give us a ring.
0800 6890668
What that means.
Servo patterns are written onto the platters at the factory, and they are the only way a head knows which track it is over. Put the stack out of alignment and none of that reads back, so the arm sweeps across, recognises nothing, parks, and starts again — over and over, which is the tick. Read nothing into the LED. All it proves is that the USB board has power; it says not one thing about the mechanics behind it. He tried it twice, got the same performance both times, then stopped. Stopping was the best thing anybody did to that drive.
What did the work here.
The order of the work →| Equipment | The job it did | What it adds |
|---|---|---|
| DeepSpar Disk Imager 4 | Scored each head before a single read, which put the poor surface last | Head mapping first, then one surface at a time, with resets, timeouts and power all governed |
| PC-3000 Data Extractor | Drove the imaging after the transplant, zone by zone, from inside the firmware | Reads the disk from inside its firmware, using the PC-3000's imager |
| UFS Explorer Professional Recovery | Put the exFAT volume back together from the image, then opened each CR3 | Handles the file systems other tools give up on: APFS, ReFS, XFS, ZFS, Btrfs |
What we did.
Sleeve off, bridge board out, an ordinary disk underneath
Peel back the rubber, unplug the small USB bridge, and what is left is a 2.5in SATA disk like any other — except this one has been dropped. On bench power the decision moves to us: it turns when we have a reason to turn it, and not because a laptop somewhere has gone hunting for a volume.
New heads in, then a survey before one sector is read
A donor from the same product family, on the same firmware revision, gave up its stack. With those heads fitted the patient came back with its correct identity — and still nothing was read off it. The survey came first: each head timed and scored for how cleanly it read, so the order was set by this drive and not by a procedure. One head was solid. The other read slowly and kept hesitating, so its surface went to the back of the queue.
Strong surface at the front, the doubtful one last
The good side came off first — timeouts kept short, a power cycle whenever it stalled — so most of the archive was banked before the weak head was asked for a thing. Its platter side followed at the end, at whatever pace it wanted. Six days from bench to sign-off. On a drive that has hit concrete, slow is not a compromise — slow is how it gets done.
How it closed.
Before the job was signed off every CR3 was opened and drawn on screen, because a filename in a listing that will not render is no use whatever to a photographer. The set went back on new media, with a duplicate written that same afternoon. Two seasons of weddings now sit where they should have been sitting all along: on two separate drives.
Other pages worth a look here.
Also filed under Pocket-size drives.
Is yours behaving the same way?
Switch the device off, post it in, and decide nothing until the diagnosis comes back to tell you where you stand.