Desktop externals · job notes · BHD-2025-8334
Ranked by Noise, the Order Comes Out Wrong.
A letting agency in Sutton Coldfield was closing a branch, and both drives went into the same box. The Iomega had been dug out of a stationery cupboard to take one last archive copy and never finished it — ten minutes on one folder, then it disappears
— which everyone in the office read as old, obviously
. The Seagate was newer and had come off a filing cabinet when a removals trolley caught it; after that all it does is tick to itself
and no machine will see it
.
Sounds like yours? Give us a ring.
0800 6890668
What that means.
Sound is a bad guide to urgency, and here it pointed the wrong way entirely. Heads wrecked in a fall cannot find the platters, and that is a settled state — leave the drive on a shelf for a month and it is in the same condition when you come back to it. So the Seagate, the noisy one, was also the one that could wait. The Iomega was urgent because it still half worked. Reads had slowed past anything the USB bridge would sit through, Windows gave up on each copy partway, and every restart cost it more surface for good. Noise tells you a drive is broken. It tells you nothing about which one to put on the bench first.
What did the work here.
The order of the work →| Equipment | The job it did | What it adds |
|---|---|---|
| DeepSpar Disk Imager 4 | Took the Seagate after surgery: map the heads, read the best surfaces first | Head mapping first, then one surface at a time, with resets, timeouts and power all governed |
| PC-3000 Data Extractor | A single pass across the Iomega, each stall capped at a set time and logged | Reads the disk from inside its firmware, using the PC-3000's imager |
| R-Studio Technician | Rebuilt the folder tree of each drive from its finished image | Broad file-system support, with RAID rebuilds that can be trusted |
What we did.
The fault sets the queue, not the volume
Arriving together earned neither drive a place in the queue; both were judged on their own. Left switched off, the Seagate would be identical in four weeks to the way it landed, so a wait was free. The Iomega had no room like that. Powered up, it shed sectors by the hour and never got them back, so it went on first and the Seagate sat on a shelf.
Start with the Iomega, and do not linger
The stalls were what cost it surface, so the stalls got a budget. Each read had a short fixed window; anything that ran over was noted, skipped, and picked up later on softer settings. Nothing timed out on the bus and no pass had to start again from zero. The thing that had beaten the office became a list of line numbers, and the old drive copied across at a steady rate.
The Seagate next: new heads, no clock running
The Seagate needed a head stack before it would do anything at all. A matched donor set went in under laminar flow, and each head was graded on the bench before anything was read at all. The drop had left a score mark on one surface. The others read clean and gave everything up; the marked one gave what was left of it.
How it closed.
What came back was the opposite of what the office expected. The Iomega, the drive everyone had already given up on, was returned near enough whole. The Seagate lost the scored band on that one surface, and a set of client files with it, listed by name in the report instead of buried in a total.
Other pages worth a look here.
Others under Desktop externals.
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.