Case file · Desktop externals · BDR-2025-0903
A Fatal Hardware Error, Then Two Clicks.
The decline had acts. First the drive became very slow to load
. Then Windows produced a fatal hardware error
, and the drive's identity shrank to a bare local disk
. Finally the ritual settled: it starts spinning and emits two clicks, it stops after that
. Curtain.
Same symptoms on your desk?
01273 964902
The decode.
Spin, two clicks, stop is a drive running its startup sequence and failing the same step twice before giving up cleanly. On power-up a drive must read calibration and adaptive data from a reserved area of the platters; if the heads can't resolve it, the drive recalibrates, tries once more, and shuts down rather than continuing blind. The preceding slowdown was those heads weakening; the fatal hardware error was the operating system noticing.
Equipment on this case.
How a case runs →| Platform | What it did here | Why this tool |
|---|---|---|
| DeepSpar Disk Imager 4 | Head map after donor heads, then imaging ordered strictly by head health | Head-map-aware imaging with per-head timeout, reset and power-cycle control |
| PC-3000 Data Extractor | Handled the read passes with reset and power-cycle control between stalls | The imaging half of the PC-3000 platform, driven by the firmware half |
| R-Studio Technician | Rebuilt the filesystem from the completed image | Broad filesystem coverage and dependable RAID reconstruction |
On the bench.
Read the failure sequence as a diagnosis
The two-click ritual is precise enough to work from: it places the fault at startup calibration rather than at general reading, which means the reserved service area on the platters is where the heads are struggling first. Inspection confirmed head degradation consistent with wear rather than impact — this drive had been dying slowly for months.
Donor heads, then find out what survived
A matched donor head stack restored the drive's ability to complete its startup sequence, and it identified correctly for the first time in weeks. A head map immediately followed, because a drive that has been reading badly for months usually has damage distributed unevenly across its surfaces.
Image at once, healthiest surfaces first
A drive that failed this way does not get asked twice. Imaging started in the same session, working the strongest heads first and leaving the weakest zones for final passes at reduced speed. The great majority of the surface read cleanly once the calibration problem was solved.
The outcome.
Full image, full recovery, files verified open rather than merely counted. The two-click ritual was recorded in the case notes and never performed again.
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.