Board-level faults · job log · RDG-2025-1753
The Fault Arrived With the Lights.
Next door, a digger found the supply cable feeding a builders' merchant at Theale, just off M4 Junction 12, and the yard spent a morning without electricity. When it came back on, the office desktop got as far as Default boot device missing
and no further, the BIOS adding only no drive found on either channel
. Nine years of supplier accounts were on that machine, together with the stock and price file and every photograph the website runs on.
Same fault on yours? Tell us what it is doing.
0800 6890668
What actually caused it.
Read the board and you have the story. Across the mains input sits a small part designed to fail before anything expensive does, and it had done precisely that. Restoring a supply is a rougher event than losing one, which is why kit that sat out a whole morning of no power without complaint can be finished in the first second after the lights return. The recording is untouched by any of it, though. Files are held as tiny magnetic grains, each pointing one way or the other. An orientation holds no charge, so a spike finds nothing there to work on. So a disk that disappears after an outage is, far more often than not, an intact archive sitting behind ruined electronics.
What this one needed on the bench.
How every job runs →| Bench tools | Its part in this job | Why it is here |
|---|---|---|
| ACE Lab PC-3000 Express | Proved the donor board first — identity, SMART log and defect tables all responding | Gets into the manufacturer's own service mode, which plain ATA never reaches |
| PC-3000 Data Extractor | Gave the imager this drive's defect maps first, and went at the surfaces afterwards | Copies at firmware level, through the drive's own controller rather than around it |
| R-Studio Technician | Opened the image's NTFS volume and walked the whole folder tree | Handles almost any file system, and puts an array back together off the images |
What the bench did.
Trace where the surge actually went
Under magnification a spent sacrificial component shows up immediately, and finding it answers almost nothing. The question that matters is how far the surge travelled afterwards. Plenty of it routinely gets past that component; further down the line sit the motor driver and the interface chip, and neither was assumed to be healthy. Test only the obvious part and the disk quits halfway through imaging.
Move the original ROM onto the donor
Tracking down the right board revision gave us working electronics. A donor cannot supply one thing, though: the memory chip belonging to this individual drive. That came off the damaged board and went across. Calibration figures burned into that ROM at the factory apply to one head stack over one set of surfaces and to nothing at all beyond them. Fit a board without them and it spins the motor, sounds entirely correct, and returns rubbish.
Set the defect map in place before imaging starts
With the donor in place the Barracuda gave its name and its full 2TB. The defect tables went into the imager's configuration before any imaging began. Not one request had to be repeated. Surfaces behave like that when nothing but the board has failed.
What went back.
Inside the week it was all checked and returned on a new disk. Both machines, the till and the office one, now sit behind a UPS, and a second drive takes a copy of the supplier accounts nightly.
If this sounds like yours, start here.
More jobs that began with the power.
If that sounds like yours, stop there.
Post it in as it is, switched off. Looking costs nothing, and you get one fixed figure in writing before any chargeable work begins — £250 + VAT for a card or stick, £300 + VAT for a single drive, from £500 + VAT for RAID and NAS. On most jobs, nothing is charged unless your data comes back.