Data Recovery Case File · Desktop Externals & Aging Drives · Half the Board Works
Spinning Proves the Motor Path, and Says Nothing About the Rest of the Board
His enquiry offers a diagnosis worth taking seriously. A drive where "the drive spins up ok, the problem seems to be with the control side of the circuit, most likely caused by a supply problem causing damage to the circuit board — or a firmware issue." The observation underpinning it is sound: a drive that reaches speed has a working motor path, which narrows the fault to the parts of the board that do everything else.
| Media | 250GB hard drive — rotation achieved normally, no host communication established; power supply fault suspected as the origin |
| Reported situation | Drive failing following a suspected power supply fault · rotation achieved normally on power · drive not communicating with the host · owner attributing the fault to the control section of the circuit board or to firmware · content required |
| Fault class | Board fault confined to control circuitry with motor drive intact — supply-borne damage indicated; recorded surfaces not implicated |
| Equipment used | Rotation treated as evidence of an intact motor path rather than general board health · board examined at component level under a current-limited controlled bench supply · damaged components identified and addressed · firmware memory transferred to a matched donor board where repair was not viable · imaging in one supervised session once communication was restored |
The decode: why a board can fail in one half and not the other
What a drive's board actually does: several separate jobs. It regulates incoming power, drives the spindle motor, moves the head assembly, processes the signal from the heads, and handles communication with the host — different circuits, sharing a board.
Why that means partial failure is normal: damage rarely takes everything. A supply fault delivers excess voltage or current along a particular path, and what fails is what that path reaches — leaving the rest functional.
Why spinning is the clearest evidence of that: the motor drive circuit is working. It receives power, generates the correct signals, and brings the platters to speed — a substantial part of the board doing exactly what it should.
What his conclusion follows correctly from: if the motor works and nothing communicates, the surviving fault is downstream. Either the processor and its supporting circuitry, or the communication interface, which is what he means by the control side.
Why supply faults produce this pattern specifically: protective components on the board are designed to fail first. They sacrifice themselves to absorb an over-voltage event, and when they do, the paths they protected go dead while everything else continues.
Why that is genuinely good news for the recording: the fault is electrical and stops at the board. Nothing about it reaches the platters, and a drive that never ran in a damaged mechanical state has scored nothing.
Why a board cannot simply be swapped: each drive's board carries a memory holding calibration and mapping data unique to that individual drive. A replacement board arrives with another drive's parameters and cannot read this one, so that memory has to be transferred across.
Why component-level repair is attempted first: where the damage is confined to protective components, replacing them restores the original board complete with its own configuration. That is simpler and more reliable than any transfer.
Why his alternative suggestion is worth testing too: a firmware fault produces similar silence. A drive unable to read its own configuration also fails to communicate, and the two are distinguished by measurement rather than by inspection.
What must not happen: no further powering through the same supply, and no board swapped from another drive. If a supply fault caused this, connecting the drive to it again risks the replacement board too.
On the bench
Rotation was treated as evidence of an intact motor path rather than general board health — a drive board performing power regulation, spindle drive, head positioning, signal processing and host communication as separate circuits, so damage along one path leaves others functional, with protective components designed to fail first and isolate what they protected. The board was examined at component level under a current-limited controlled bench supply, and firmware memory transferred to a matched donor board where repair was not viable.
The outcome
Rotation treated as evidence of an intact motor path, the board examined at component level on a current-limited supply, and configuration memory transferred where repair was not viable. Free assessment, one fixed written figure including VAT, 50% of parts and labour upfront with the balance only on successful recovery. The decode: your reasoning holds. A board does several separate jobs, so a supply fault takes the path it reached and leaves the rest — and spinning proves the motor circuit survived it.
A drive that spins normally and communicates with nothing
Don't power it through the same supply again, and don't fit a board from another drive. Spinning is genuinely informative: the motor drive circuit is receiving power, generating correct signals and bringing the platters to speed, so a substantial part of the board is working and the fault is downstream in the control or communication circuitry. That's the normal shape of supply-borne damage, because protective components are designed to fail first and isolate the paths they protect. It also means the damage stops at the board and your recording is untouched — but each board carries calibration unique to its own drive.
Don't reconnect the same supply — call Manchester Data Recovery on 0161 871 0788; rotation treated as an intact motor path, board examined at component level on a current-limited supply, configuration memory transferred where needed.
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.