Data Recovery Case File · Desktop Externals & Aging Drives · The Chip That Has to Move
Every Board Carries Calibration Data Belonging to One Drive
His enquiry contains a precise mechanical observation and a reasonable experiment that failed for a reason worth knowing. A drive that "spins, the arms go over the disc twice and then it stops spinning. Not recognised. Changed the lead, tried another board with the same code" — and nothing changed. Boards of the same model are not interchangeable, because each carries a small memory holding values measured from the individual drive it was built with.
| Media | External hard drive — two head sweeps followed by spin-down on power; not enumerating; donor board of matching revision fitted without effect |
| Reported situation | Drive functioning normally, then failing on reconnection minutes later · rotation commencing · head assembly sweeping twice · rotation ceasing · drive not recognised · reported as uninitialised and unallocated · cable substituted · donor board of matching code fitted without improvement |
| Fault class | Service area read failure — two-sweep signature indicating failure to load firmware; donor board without transferred adaptive data unable to address the drive |
| Equipment used | Sweep-and-stop behaviour interpreted as service area read failure · original board retained as the source of adaptive data · adaptive memory transferred from original to donor before any further attempt · firmware modules assessed and repaired in technological modes · imaging on restored addressing |
The decode: what the two sweeps mean, and why the board swap failed
What the drive is doing: on power, it spins up and the heads move out to read a reserved region holding its own firmware and calibration — the service area. Two sweeps and a stop is that read being attempted, retried once, and abandoned, after which the drive shuts down because it cannot proceed without what it was looking for.
Why that is a recognisable signature: the count matters. A drive that sweeps repeatedly and continues is doing something different from one that tries twice and gives up, and the deliberate stop indicates a firmware-level decision rather than a mechanical failure to move.
Why his board swap was a reasonable thing to try: a drive that spins but does not present frequently has a board fault, and matching the printed code is the obvious way to select a donor. It is what almost everybody does, and the advice circulates widely.
Why it cannot work on its own, and this is the part nobody is told: modern drive boards carry a small memory chip holding adaptive data — calibration values measured at manufacture for that specific drive's heads, surfaces and motor. Every unit is slightly different, and the board is programmed with the corrections its own drive needs.
What happens when a donor board is fitted: the electronics work perfectly and they are using the wrong corrections. The drive attempts to read its service area using another drive's calibration and fails — which produces the same symptoms as before, because it is the same failure arrived at differently.
What the correct procedure is: the adaptive memory chip is transferred from the original board to the donor. Then the donor is running that drive's own calibration, and the board substitution does what he expected.
Why the attempt carries a risk worth naming: some drives write to their adaptive area during start-up. A drive started on a mismatched board can have wrong values written back, which is why board swapping is not the harmless experiment it appears to be.
What his symptom suggests regardless: the two-sweep signature points at the service area rather than the board — so the fault may not have been a board fault at all, and the swap was addressing the wrong component.
On the bench
Sweep-and-stop behaviour was interpreted as service area read failure — the head assembly moving to read a reserved region holding firmware and calibration, retrying once and shutting down deliberately when it cannot be loaded. The original board was retained as the source of adaptive data, modern boards carrying a memory holding calibration values measured at manufacture for that individual drive's heads and surfaces. Adaptive memory was transferred from original to donor before any further attempt.
The outcome
The signature read as a service area failure, the original board retained for its adaptive data, and firmware modules repaired in technological modes. Free assessment, one fixed written figure including VAT, 50% of parts and labour upfront with the balance only on successful recovery. The decode: a matching code is not a matching board. Each carries a small memory holding calibration values measured for that individual drive, so a donor runs the wrong corrections — the chip has to be transferred with it.
Before swapping a drive board
Keep the original, and know that matching the printed code isn't sufficient. Modern boards carry a small memory chip holding adaptive data — calibration values measured at manufacture for that specific drive's heads, surfaces and motor — so a donor board works perfectly while using another drive's corrections, and the drive fails to read its own service area exactly as before. The chip has to be transferred across. There's a risk in trying, too: some drives write to their adaptive area on start-up, so running one on a mismatched board can have wrong values written back. If your drive sweeps twice and stops, that points at the service area rather than the board anyway.
Keep the original — call Oxford Data Recovery on 01865 593000; signature read as a service area failure, adaptive memory transferred from the original board, firmware modules repaired in technological modes.
Request a quote online →
Our case files are drawn from genuine enquiries received by our laboratory over the past ten years, anonymised to protect client confidentiality. Each one describes the diagnostic and recovery procedure our engineers apply to that fault, using the equipment listed.