Desktop externals · job record · BHD-2025-8611
Fifteen Good Minutes, Then Nothing.
A loft in Yardley was being insulated, so the boxes came down at last, and the Iomega turned up in among a knot of old leads. It behaved for fifteen minutes — mounted, showed its folders, opened two or three of Grandad’s slide scans
— and then went off the desktop in the middle of a click. Since then every machine gives her the same answer, corrupted and unreadable
: the laptop at home and the desktop at work
, and even on a powered hub it was the same
. On the drive: the family history research, the scanned slides, and the accounts from the old business.
Sounds like yours? Give us a ring.
0800 6890668
What that means.
‘Corrupted’ is the word Windows reaches for whenever a read fails, so it labels the symptom and settles nothing. The drive itself was more informative: it quit in the middle of a read, and quitting at that particular moment points at a mechanism worn past its best, not at bits fading from the platters. A long spell with no power is unkind to moving parts. Lubricant creeps away from where it is wanted, bearings settle into one position, sliders go dull — and asking a survivor for one long unbroken read is the least forgiving way to begin.
What did the work here.
The order of the work →| Equipment | The job it did | What it adds |
|---|---|---|
| DeepSpar Disk Imager 4 | Read at reduced speed, on a profile built for drives out of long storage | Head mapping first, then one surface at a time, with resets, timeouts and power all governed |
| ACE Lab PC-3000 Express | Read out the defect lists and reallocation figures to map the ground to avoid | Gets at the factory service commands that standard ATA cannot carry |
| R-Studio Technician | Reassembled the torn filesystem records, working from the image alone | Broad file-system support, with RAID rebuilds that can be trusted |
What we did.
Stop looking at it, stop plugging it in
No USB port went near it after that. It came up on bench power, and the firmware was asked first, since its answers decide the running order: a grown defect list already long, and a reserve of spare sectors nearly spent. So one measured pass to lift the whole surface, and no exploratory poke about beforehand to satisfy anyone’s curiosity.
Soft settings for something long left standing
The imager was set up to humour it: throughput held down, timeouts stretched out, a rest booked between zones so the drive never got a chance to warm. Treated like that, most of the surface came away without complaint, and almost every error in the log traced back to one head over a single band.
Fix the ‘corruption’ on the copy, where nothing can be lost
Off the image, that frightening verdict amounted to very little: filesystem records the weak head had handed back in pieces, or had not handed back at all. NTFS keeps a spare of much of that bookkeeping, and the backup supplied what was missing, so folders returned with names and dates that agreed with one another. What the poor head never gave up came to a small handful of scans.
How it closed.
The research, the accounts and all but a few of the slides were opened and inspected one by one. Nine scans came back part-formed, and every one of the nine is named in the report; no figure was rounded. That Iomega will not see the loft again. Two drives hold the archive between them now, and neither of them sits idle.
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.