Case file · Desktop externals · BDR-2025-0334
One Drive Clicks, the Other Fades.
Two drives arrived sharing a box and nothing else. The first: a dropped hard disk (2Tb) which clicks and is not recognised
— the owner's verdict, mechanical failure
, entirely correct. The second was subtler: working very slow and eventually disappears from windows explorer
mid-transfer, suspected of a software or chip problem
.
Same symptoms on your desk?
01273 964902
The decode.
The owner had, without the vocabulary, diagnosed both correctly. A drop followed by clicking is a head stack that can no longer resolve servo data — hardware, requiring parts. Slowing and then vanishing under load is a different animal: the drive is completing reads too slowly, the controller times out, and the operating system drops the device rather than waiting. One needs surgery; the other needs speed. Treating them alike would have wasted the second drive's remaining life while the first sat waiting.
Equipment on this case.
How a case runs →| Platform | What it did here | Why this tool |
|---|---|---|
| DeepSpar Disk Imager 4 | Head map and staged imaging on the dropped drive after donor heads went in | Head-map-aware imaging with per-head timeout, reset and power-cycle control |
| PC-3000 Data Extractor | Ran the second drive's read pass with timeout control the OS can't offer | The imaging half of the PC-3000 platform, driven by the firmware half |
| R-Studio Technician | Rebuilt both filesystems from their images and reunited the data | Broad filesystem coverage and dependable RAID reconstruction |
On the bench.
Triage them apart, and set priorities
The two drives were assessed separately and given different priorities. The clicking drive was stable in the sense that it was doing nothing — it could wait safely, powered off. The fading drive was actively deteriorating each time it was used, so it went first, because its window was the one closing.
Image the fader before it finishes fading
The degrading drive was imaged with aggressive timeout control — the very thing Windows lacks. Where the operating system had waited, given up and dropped the device, the imager simply logged the slow sector, moved on, and returned later. Most of the drive read at reasonable speed once the stalls stopped derailing the whole transfer.
Then the mechanical job, properly and slowly
The dropped drive received a matched donor head stack, a head map, and a staged image working the healthiest heads first. Its damage was genuine but localised, and patience recovered the great majority of the surface.
The outcome.
Both recoveries landed — the dropped drive's data via donor surgery, the fading drive's via speed and timeout discipline. Two fresh drives went home holding what two failing ones nearly kept.
Related on the index.
More from Desktop externals.
Recognise your own drive in this story?
Same rule as every case above: power it down, and let the diagnosis be free before any decision has to be.