Desktop externals · bench file · CDF-2025-0334
Sort Them by Noise and You Start Wrong.
When a letting agency in Cwmbran shut one of its branches, both drives were packed into the same box. The Iomega came off a shelf in the stationery cupboard to take a last archive copy, and it never finished the job — ten minutes on a folder, then it vanishes
— which the office put down to the age of the thing
. The Seagate was newer. It had been on a filing cabinet until a removals trolley caught it, and since then it just ticks to itself
and nothing will pick it up
.
Does that match yours? Call us.
0800 6890668
Why that happens.
Noise is the wrong thing to sort by, and here it pointed exactly backwards. Heads wrecked in a fall cannot reach the platters, and nothing about that moves: leave the drive in a drawer for a month and it comes out the way it went in. So the loud Seagate was also the one that could afford to wait. The Iomega was urgent for the opposite reason — it still half worked. Its reads had dropped below anything the USB bridge would put up with, Windows walked away from each copy halfway, and more surface went for good with every restart. A noise tells you the drive is broken. It does not tell you which of the two to start with.
What we used on this one.
Every step, in order →| The tools | What it did here | Why it helps |
|---|---|---|
| DeepSpar Disk Imager 4 | Handled the Seagate after the swap: build a head map, take the best surfaces first | Maps the heads first, works surface by surface, and keeps resets, timeouts and power in hand |
| PC-3000 Data Extractor | One pass over the Iomega, every stall given a fixed limit and written down | Imaging driven from inside the drive's own firmware, by the PC-3000 |
| R-Studio Technician | Built each drive’s folder tree back from its completed image | Reads nearly every file system, and rebuilds arrays you can rely on |
How it went.
The fault decides the order, not the noise
Arriving in one box bought neither drive a place in the queue; each was judged on what was actually wrong. Switched off, the Seagate in four weeks would be the drive that landed here, so waiting cost it nothing. The Iomega had no margin like that. Under power it shed sectors hour by hour, with none of them coming back, so it took the bench first while the Seagate waited on a shelf.
Begin with the Iomega, and keep moving
The surface was going during the stalls, so the stalls were given a budget. Every read got a short fixed window; whatever ran over was noted, skipped past, and revisited later on softer settings. Nothing dropped off the bus, and no pass ever had to start over. What had beaten the office became a column of numbered lines, and the drive copied through at a steady rate.
Then the Seagate: fresh heads, and no hurry
The Seagate would give up nothing until it had a new head stack. A donor set was matched and fitted in laminar-flow air, and every head was checked on the bench before any reading began. The fall had cut a mark across one surface. The rest read clean and handed over the lot; the scarred one gave back only part.
Signing it off.
The outcome was the reverse of what the branch expected. The Iomega — written off by everyone in the office — came back very nearly complete. What went missing was on the Seagate: the damaged band across that single surface, and a set of client files sitting on it, each one named in the report rather than buried in a percentage.
Pages people often read next.
Filed beside Desktop externals.
Is that what yours is doing?
Power it down, get it to us, and hold off on any decision until the diagnosis says what can still be read.