Data Recovery Case File · Desktop Externals & Aging Drives · Keeping It Was the Right Call
The Swap Did Not Work and He Preserved the Answer
His enquiry describes an attempt that failed and a precaution that matters more. A drive from 2009 unused for years: "it doesn't work any more and is not recognised by the computer. I've tried multiple computers; the disk console does not pick it up either. I removed its original controller board and used a new one, but it still doesn't work — I have put the original board" aside. The swap was never likely to work on its own, and keeping the board he removed is what makes the rest of this possible.
| Media | Hard drive of approximately 2009 vintage, unused for several years — not enumerated on any host; controller board substituted by the owner without effect; original board retained |
| Reported situation | Drive of approximately 2009 stored unused for several years · not recognised on any computer · absent from the disk management console · original controller board removed by the owner and a replacement fitted · behaviour unchanged · original board retained |
| Fault class | Failure to enumerate on a long-dormant drive — board substitution ineffective without adaptive data transfer; original board essential |
| Equipment used | Original board recovered into the assessment as the source of adaptive data · dormancy effects assessed alongside the original fault · firmware memory read from the original board and transferred where a replacement was indicated · readiness sequence read under strict timeouts · imaged write-blocked |
The decode: why a board swap alone fails, and what he preserved
What a controller board carries beyond its circuitry: a small memory chip holding adaptive data — parameters unique to that individual drive, describing its specific heads, its preamplifier settings, its calibration, and the map of defective areas found during manufacture. That information is not generic and it is not on the platters. It is written to the board's memory at the factory for that drive alone.
So what happens when a board is simply exchanged: a replacement arrives carrying another drive's adaptive data. The electronics may be identical, the part number may match exactly, and the drive still will not work — because the controller is applying one drive's calibration to another drive's mechanism. It usually produces no recognition at all, which is precisely what he found.
What has to happen instead: the memory chip is transferred from the original board to the replacement, or its contents are read and written across. Then the replacement carries the correct parameters and the drive behaves as itself. That is the step his attempt was missing, and it is why board swaps have a reputation for not working — most people try it without it.
Why keeping the original board is the decisive thing he did: without it, the adaptive data is gone, and with it the drive's own defect map and calibration. Recovering a drive whose original board has been discarded is materially harder and sometimes not possible at all. He may not have known why it mattered, and it mattered enormously.
Whether the board was the fault at all: worth establishing rather than assuming. He substituted it because the drive was not recognised, which is a reasonable hypothesis — but a drive of that age, unused for years, has other reasons not to start. The original board may be perfectly healthy.
What the years in storage have added: lubricant thickening and possible head adhesion, both of which develop during dormancy rather than at the moment of failure. A drive that was working when it was put away can be unable to start when it comes out.
What to send: both boards, the drive, and a note of which board came off it. Labelling matters, because two visually identical boards are not interchangeable and only one of them holds the right data.
On the bench
The original board was recovered into the assessment as the source of adaptive data — a controller carrying parameters unique to its own drive, including calibration and the factory defect map, so a replacement fitted alone applies another drive's settings and typically produces no recognition at all. Dormancy effects were assessed alongside the original fault, the drive having been stored for years. Firmware memory was read from the original board and transferred where a replacement was indicated, the readiness sequence read under strict timeouts, and the drive imaged write-blocked.
The outcome
The original board recovered into the work as the source of adaptive data, dormancy assessed alongside the fault and the drive imaged on restored readiness. Free assessment, one fixed written figure including VAT; where a drive has to be opened, 50% of parts and labour is payable upfront with the balance only on success — otherwise no recovery, no fee. The decode: a controller board carries a memory chip holding parameters unique to that individual drive — calibration, head characteristics, the factory defect map. So an identical replacement fitted on its own applies the wrong drive's settings and generally produces nothing. Keeping the board you removed was the important decision.
Swapped a drive's controller board and it still doesn't work
Keep the board you took off, and send both — that's the decision that matters most, whether or not you knew why. A controller board isn't just circuitry: it carries a small memory chip holding parameters unique to that individual drive, including its calibration, its head characteristics and the map of defects found at the factory. None of that is on the platters. So fitting a replacement, even one with an identical part number, means applying another drive's settings to your mechanism, which usually produces no recognition at all — exactly what you found. The missing step is transferring the memory chip's contents from your original board. Label which board came off the drive, since two identical-looking boards aren't interchangeable.
Send both boards — call Guildford Data Recovery on 01483 901310; original board used as the source of adaptive data, dormancy assessed alongside the fault, readiness read under strict timeouts.
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.