Job record · Desktop externals · MHD-2025-6611
It Came Down, It Ran, It Stopped.
Insulation was going into a loft in Bourne End, the boxes finally came down, and the Iomega surfaced among a tangle of old cables. It gave her fifteen minutes of good behaviour: it mounted, it listed its folders, and it opened a couple of Grandad’s slide scans
before disappearing from the desktop halfway through a click. Every machine since has returned the same verdict, corrupted and unreadable
, on my own computer and the work one
, and the powered hub changed nothing
. The drive holds the family research, the scanned slides and the old business accounts.
Much the same fault? Call us.
0800 6890668
In everyday terms.
Windows reaches for the word ‘corrupted’ whenever reads fail, so it names a symptom and settles nothing. What the drive itself said was more useful: it stopped while it was reading, and giving up at that moment implicates a tired mechanism rather than data fading off the platters. Years without power are hard on anything mechanical. Grease migrates, bearings take a set, the head sliders lose their edge, and the least kind thing you can then ask of a survivor is one long continuous read.
What the bench used here.
How a job is handled →| Tool | Why we used it | What it brings |
|---|---|---|
| DeepSpar Disk Imager 4 | Ran the reads slowly, on a profile meant for a drive out of long storage | Head map first, then head-by-head reads, holding resets, timeouts and the power line steady |
| ACE Lab PC-3000 Express | Queried the defect lists and reallocation counters for the areas to avoid | Reaches the vendor-specific commands that ordinary ATA has no way of issuing |
| R-Studio Technician | Put the torn filesystem records back together, working only from the image | Its file-system coverage is wide and its array rebuilds hold up |
The lab work.
No further browsing, no more mounts
It saw no USB port again. Bench power went on instead, and the first questions were put to the firmware, whose answers set the order of work: a long grown defect list and a spare sector pool largely spent. That left one careful pass to take the whole surface off, with no preliminary look around to satisfy anybody’s curiosity.
Gentle settings for a drive long out of use
The imager was configured to indulge it: the transfer rate kept low, the timeouts extended, rests scheduled between zones so that it never had time to warm. Handled that way the greater part of the surface came off without protest, and nearly every error logged belonged to one head working a single band of the platters.
Repair the ‘corruption’ on the image, where nothing is at risk
Read back from the image, the alarming verdict came to very little: filesystem records that the tired head had returned torn, or had not returned at all. NTFS holds a duplicate of much of that bookkeeping, and the second copy filled in the missing entries, so folders came back with their names and their dates in agreement. The scans that the weak head would not surrender came to a handful.
How the job closed.
The research files, the accounts and very nearly all of the slides were opened and checked one at a time. Nine scans came back incomplete, and the report lists each of them by name instead of rounding the figure. The Iomega is not going back up into the roof; the archive now sits on two drives, and both are in regular use.
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.