Mains-powered desk drives · case file · HUL-2025-0611
A Quarter of an Hour Out of a Loft.
An insulation project for a Bricknell loft resulted in a large number of boxes emerging after several years. In one box, among some older wires, was an Iomega external hard drive. It functioned properly for approximately a quarter of an hour. During that time, it loaded, displayed numerous folders, and opened a couple of the slides Grandad had scanned
. It then terminated prematurely during a mouse click. None of her attempts after that would allow any of the computers to read the contents of the external hard drive. Each machine stated that the external hard drive was corrupted and unreadable
: the laptop at home, then the one in the office
, and the powered hub made not a bit of difference
. The files on it included historical documents about her family, scanned images, and the accounts of a former business.
Sounds like yours? Ring us.
0800 6890668
What causes it.
Windows refers to "corrupted" reads as such because they return incorrectly. Windows does identify this symptom but also fails to identify anything else. The drive did provide additional information. Specifically, it stopped in the middle of reading data, and based on that timing, this points to a problem with a mechanical aspect of the drive and not to a loss of magnetic field from the disks. Mechanical elements don’t like sitting around for years. The oil will migrate. The bearings will settle over time. Sliders lose their lustre. If you ask for a prolonged read of data on a drive in this condition, you’ve made the worst first decision possible.
The tools this one needed.
The steps we follow →| The gear | What this one did | Why we have it |
|---|---|---|
| DeepSpar Disk Imager 4 | Ran the read slowly, using a profile meant for drives left in storage | Grades each head first, reads one surface at a time, and keeps resets, timeouts and power under control |
| ACE Lab PC-3000 Express | Pulled the defect tables and reallocation figures, so we knew which areas to avoid | Reaches the vendor service commands an ordinary ATA connection cannot |
| R-Studio Technician | Put the damaged filesystem structures back together, using the image alone | Handles almost any file system, and puts RAID sets back together |
The stages.
No more USB, and no more poking about
That drive never went near a USB port again. It ran on bench power, and the firmware came off first, because what the firmware says fixes the order of everything after it. Plenty of entries on the grown defect list already, and very few spares left. So one measured pass across the whole surface, and no rooting through folders beforehand to see what was on there.
Slow settings for a drive that had sat still
We instructed the imager to take things slow: to lower the read rate, increase timeouts and allow the heads to cool before moving them into another zone. Under these conditions, the disk provided mostly quiet performance and nearly all errors were associated with a single head positioned within a very narrow area.
Fix the ‘corruption’ on the copy, not on the original
From examining the images, that alarming word represented almost nothing. The failing head had returned part of the metadata associated with the filesystem (the book-keeping information). Since NTFS maintains multiple copies of much of this metadata, it was able to fill in the missing pieces and return the folders with accurate naming and date stamps. The only information that was lost permanently was a small number of scans.
How it finished.
Each item of research, each of the old accounts and the slides were examined individually. There were 9 scans which returned partial results. Each of these is included in the report by name. Nothing has been trimmed or rounded off. The Iomega is not returning to storage in the attic. The archives are being kept on two drives and both drives continue to be accessed.
What people read after this.
Tagged Desktop externals too.
Is yours doing the same?
Shut it off. Get a quote first. Send it to us. We diagnose first. The diagnosis tells you which files are recoverable and which are irretrievable.