A software tester in Ormskirk did what testers do. The drive stopped being recognised, so he checked Disk Management, saw nothing, tried the same cable with a different drive, tried the same drive on a different machine, and arrived at a conclusion before writing in. I have ruled out the cable and the computer, he wrote, and he had.
| Media | An external portable drive that suddenly stopped being recognised, with the cable and host machine both eliminated by the owner's own testing. |
| What was reported | External portable drive, suddenly not recognised, nothing shown in Disk Management, the cable confirmed working with another drive and the drive confirmed missing on another machine, owner assumes a physical failure, recovery sought. |
| Fault class | Firmware. The service area held corruption that stopped the drive coming ready, so it never presented itself to any host. The board was healthy and the mechanism was sound. |
| On the bench | Read directly behind a hardware write blocker on PC-3000 UDMA with firmware, service area, board and mechanism each profiled in turn, the corrupt service area structures rebuilt from the drive's own copies, imaged on DeepSpar, filesystem parsed in R-Studio, files validated and written to fresh media. |
His testing was worth more than he thought. Cable with a known good drive, drive with a known good machine. That is proper elimination and it means nobody had to repeat it. It also meant the drive could be assessed directly instead of starting with the obvious.
Drive side does not mean physical, though. He assumed a physical breakdown, which is the natural conclusion, but firmware failures produce exactly the same silence. A drive with corrupt service area structures never comes ready, and a drive that never comes ready is invisible to every operating system in the same way a dead one is.
The difference is worth real money. Firmware repair is logical work and runs on no fix, no fee. A mechanical or board fault does not, and takes half the quoted price upfront. Same symptom, different terms, and the only thing that separates them is a diagnostic.
Nothing shown in Disk Management is not a bad sign in itself. It means the drive never introduced itself. What it says about the platters is nothing at all.
The drive went behind a hardware write blocker onto PC-3000 UDMA and firmware, service area, board and mechanism were each profiled in turn rather than assumed. The board tested healthy and the mechanism spun and settled correctly, which pointed straight at the firmware.
The corrupt service area structures were rebuilt from the drive's own redundant copies, which keeps the translation between logical and physical addresses correct. The drive then came ready and was imaged on DeepSpar. The filesystem was parsed in R-Studio from the image and the files validated before being written to fresh media.
Service area rebuilt, drive imaged, everything back. He had expected the expensive answer and got the straightforward one, which is the right way round for a surprise to go.
One drive, £300 + VAT. Firmware and service area repair is logical work, so this ran on no fix, no fee terms. Had it been the board, the same drive would have carried 50% upfront, because board repair is electronic work and the published terms exclude it.
Write down what you tested and send it with the drive, because it genuinely saves time and it stops anybody repeating work you have already done. Then stop testing. Once the cable and the host are eliminated, further attempts add nothing and each power-up is a risk if the fault turns out to be mechanical. Do not run recovery software against a drive that does not appear, because there is nothing for it to talk to. Do not assume drive side means expensive either. Firmware faults look identical from the outside and are among the more straightforward jobs on the bench.
Every case file here is written up from a real enquiry handled for households and businesses across Liverpool, Merseyside and the wider North West, anonymised so that nobody is identifiable. Each one gives the reasoning behind the diagnosis, the method the fault actually called for, and the equipment it was worked on.
A large drive that will not register has a firmware, board or mechanical cause, and only a direct read separates them
Clicking is a head fault and a rattle after a knock is usually loose hardware, and both are settled in one clean-air visit
Write errors are an early warning, and the right response is one careful image, not weeks of retries
The diagnostic is free and takes 2 working days from arrival, the figure is fixed in writing, and logical faults run on no fix, no fee. Start online or ring the freephone.