Data Recovery Case File · Second Fixes & Trade Handoffs · The Easier Procedure Applies
A Board Fault Is Answered by the Board, Not by Moving the Disks
His enquiry proposes the hardest available procedure and describes a fault that does not need it. A drive damaged by a liquid spill several years ago where he is "fairly certain the electronics are the issue", with a matching donor already in hand, asking what it would cost "to move the platters from the broken drive to the donor" and accepting there is no guarantee. If his diagnosis is right, the platters should not move at all — the board should.
| Media | Hard drive subject to liquid ingress several years previously — electronic fault suspected by the owner; matched donor drive of the same model available |
| Reported situation | Drive damaged by liquid contact several years previously · electronic failure suspected by the owner · matched donor drive of identical model held by the owner · transfer of the platters to the donor requested · no guarantee of success sought or expected · content required |
| Fault class | Suspected board-level damage with a matched donor available — board substitution with adaptive data transfer indicated in preference to platter transfer; corrosion extent determining feasibility |
| Equipment used | Proposed procedure reassessed against the suspected fault before any work was quoted · board examined at component level under magnification with corrosion mapped · adaptive data read from the original board's firmware memory · donor board fitted with that data transferred · platter transfer held in reserve for spindle or chassis failure only |
The decode: why the donor is the right idea and the platters are the wrong part
Why his instinct to use a donor is correct: a matched drive of the same model is exactly what this kind of work requires. Having one already is a genuine advantage and saves both sourcing time and cost.
Why the platters are the wrong thing to move: they are the difficult part. Multiple platters must retain their exact rotational relationship, which requires clamping the stack and moving it as one unit, and any disturbance can render the drive unreadable.
What should move instead, if the fault is electronic: the board. Swapping the circuit board leaves the sealed assembly entirely untouched, which removes the whole risk that makes platter transfer a last resort.
Why a straight board swap will not work on its own: each board carries data unique to its drive. Calibration values and defect maps are measured for that individual mechanism and stored in the board's own memory, and a donor board arrives with the wrong ones.
What makes it work: transferring that data across. The original board's firmware memory is read and its contents written to the donor, after which the donor behaves as the original did.
Why liquid damage complicates that particular step: the memory component holding the data is on the damaged board. If corrosion has reached it, the data may be unreadable — and that is the question that decides the case.
Why several years matter here specifically: corrosion continues after the liquid has gone. Residue remains conductive and draws moisture from the air, so damage progresses long after the event.
Why the board should nonetheless be examined rather than written off: corrosion is frequently localised. Damage concentrated at the power input may leave the firmware memory entirely clean, and that is established by looking.
When his original proposal would become correct: if the spindle has seized or the chassis is damaged such that the platters cannot turn. Those are the only cases where the disks must leave, and neither follows from a liquid spill.
Why his acceptance that it is a long shot deserves a straight response: it may be considerably better than he thinks. A localised board fault with a matched donor already available is among the more tractable situations there is.
On the bench
The proposed procedure was reassessed against the suspected fault before any work was quoted — platter transfer requiring the rotational relationship between disks to be preserved by clamping the stack, whereas board substitution leaves the sealed assembly untouched. Donor boards carry calibration values and defect maps for their own mechanism, so the original board's firmware memory must be read and transferred. Corrosion progresses after liquid contact, residue remaining conductive and hygroscopic. Corrosion was mapped under magnification.
The outcome
The proposed procedure reassessed against the suspected fault, corrosion mapped at component level, and adaptive data transferred to the donor board. Free assessment, one fixed written figure including VAT, 50% of parts and labour upfront with the balance only on successful recovery. The decode: your donor is the right idea and the platters are the wrong part. An electronic fault is answered by the board — which leaves the sealed assembly untouched and removes the risk that makes platter transfer a last resort.
When you have a matched donor and an electronic fault
Ask about the board rather than the platters — swapping the circuit board leaves the sealed assembly untouched, whereas moving disks requires their exact rotational relationship to be preserved and is the reason platter transfer is a last resort. It isn't a straight swap, though: each board holds calibration values and a defect map measured for its own drive, so the original board's firmware memory has to be read and transferred to the donor. With liquid damage, the question is whether corrosion reached that memory, which is answered by inspection.
The platters may not need moving — call Cambridge Data Recovery on 01223 655015; the procedure reassessed against the fault, corrosion mapped at component level, adaptive data transferred to the donor board.
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.