Desktop externals · case notes · MHD-2025-6334
One Ticks, the Other Fades Under Load.
Two drives left a Marlow letting agency in one parcel when a branch shut. The older Iomega had come out of a stationery cupboard for a final archive copy and would not see it through — a folder takes ten minutes and then vanishes
— which the office had put down to age, what else
. The newer Seagate had gone off a filing cabinet under a removals trolley; since then it only ticks away to itself
and nothing recognises it at all
.
Much the same fault? Call us.
0800 6890668
In everyday terms.
Judged by sound, the ranking came out exactly inverted. A drive whose heads were damaged in a fall cannot position itself over the platters, and that condition is stable: a fortnight on a shelf leaves it neither better nor worse, which made the Seagate the louder fault and the patient one. The Iomega was the emergency precisely because it still worked. Its reads had slowed beyond anything the USB bridge would tolerate, Windows abandoned each copy part of the way through, and every further power-up took a little more surface with it. Volume indicates that something is wrong. It says nothing at all about which drive belongs on the bench first.
What the bench used here.
How a job is handled →| Tool | Why we used it | What it brings |
|---|---|---|
| DeepSpar Disk Imager 4 | Handled the Seagate post-surgery: head map built, the soundest surfaces read first | Head map first, then head-by-head reads, holding resets, timeouts and the power line steady |
| PC-3000 Data Extractor | One full pass over the Iomega, with every stall given a fixed limit and logged | The PC-3000's imaging module, working under firmware-level control |
| R-Studio Technician | Raised each drive’s directory tree again out of its completed image | Its file-system coverage is wide and its array rebuilds hold up |
The lab work.
Running order set by the fault, not the noise
Sharing a parcel bought neither drive any priority; each was assessed separately. Unpowered, the Seagate would be in precisely the same state a month later as it was on arrival, so waiting cost it nothing at all. The Iomega had no such margin. Every hour under power cost it sectors permanently, so it went onto the bench while the Seagate waited on a shelf.
The Iomega came first, at speed
Since the stalling was doing the damage, the stalling was put on an allowance. Every read was given a fixed, short window; anything that exceeded it was recorded, passed over and returned to afterwards under gentler settings. No transfer expired on the bus, no pass restarted from the beginning. What had defeated the office became entries in a log, and the contents of the old drive transferred at a steady rate.
Donor heads for the Seagate, with time to spare
Only a replacement head stack was going to move the Seagate forward, so a matched donor was fitted under laminar flow and each head graded before a single sector was requested. One surface had been scored by the fall. The rest were intact and released everything on them; the scored one gave up what it still could.
How the job closed.
The outcome reversed what the office had assumed. The Iomega, written off by everyone who had handled it, returned all but complete. The Seagate lost one scored band on one surface, and with it a group of client files — each of them named individually in the report rather than glossed over.
More of the jobs we've closed.
Filed beside Desktop externals.
Does any of that match your case?
Nothing needs deciding until the diagnosis is back: switch the device off, send it in, and let the findings settle it.