The testing had already been done properly here. The drive "has failed", the owner reported, and it was "just not being recognised when I plug it into my laptop or another desktop computer" — two machines, same silence, which quietly settles an important question: the fault is in the drive, not the computers. Only the data was wanted; the hardware itself could go in the bin afterwards for all they cared, which is the right way round to care about it. A drive that presents itself to nobody has usually failed in its firmware, its board or its mechanics — three faults with three fixes, all of them starting the same way: the drive read directly, on equipment that doesn't need it to introduce itself.
| Media | An external hard drive, failed and invisible to a laptop and a desktop alike — the work on it wanted, the hardware itself expendable. |
| Reported situation | External drive · failed · not recognised on a laptop · not recognised on a second desktop · data needed, device not · recovery sought. |
| Fault class | Firmware, board or mechanical failure — the drive can no longer present itself, so no computer lists it. Data ordinarily still on the platters; reached by addressing whichever fault the bench finds, on equipment that speaks to the drive at service level. |
| Equipment used | PC-3000 UDMA behind a hardware write-blocker for the direct read — power behaviour, firmware and service area, board and mechanism each assessed in turn; the fault corrected at its own level (firmware repair, board work with this drive's ROM carried over, or clean-air mechanical work under laminar flow); DeepSpar imaging; R-Studio to locate the work, verified out onto fresh media. |
When a drive stops being recognised, most people blame the visible parts — the cable, the port, the computer. This owner did the diagnostic properly without knowing it: two different machines, and the drive invisible to both. That's the host ruled out. What remains is the drive itself, and 'not recognised' narrows to three usual suspects: firmware that's stumbled (the drive's own internal software, which it must boot before it can say hello), a board fault (no electronics, no introduction), or a mechanical problem keeping it from readying itself.
None of the three announces itself from outside, and none of them needs to. Recovery equipment doesn't wait for a drive to volunteer its name the way Windows does — it speaks to the drive at service level, reads its condition directly, and gets answers a desktop USB port never could. Which of the three faults this is gets established there, in minutes rather than guesses.
Worth saying plainly: the data doesn't care which fault it is. Platters hold their recording whether the firmware above them is confused, the board beside them is dead or the mechanism around them has stuck. The fault decides the route and the price band; it very rarely decides the contents. And the owner's instinct — data wanted, device expendable — is exactly the right frame, because the drive is never coming back into service either way. It's a container to be emptied carefully, once.
Direct read on PC-3000 UDMA, write-blocked throughout. Power draw profiled first, then the firmware and service area interrogated, the board inspected, the mechanics listened to — the failure localised to one of the three. Firmware faults are repaired in place; a failed board is repaired or replaced with this drive's own ROM contents carried across; anything mechanical goes under laminar flow for clean-air work. Then the image is taken on DeepSpar, the filesystem walked in R-Studio, and the wanted work located, verified and copied out to fresh media.
The drive gives up its contents at the bench without ever being recognised by a computer again — it doesn't need to be. Nothing is owed for finding out what failed: assessment is free, reported inside two working days of the drive arriving, and followed by a single fixed quote in writing. A purely firmware-level recovery runs as logical work, no fix, no fee; if the lid has to come off, half the figure is taken up front and the balance only on proven success.
Two computers is enough evidence — stop there. The third and fourth attempts don't add information, but they do add power cycles to a drive that may be failing mechanically, and a mechanical failure is the one you least want to exercise. Unplug it, note down anything you remember about how it failed, and send it in as it is. And if your own verdict on the hardware is 'bin it once the files are off' — good. That's the correct amount of sentiment for a failed drive.
Every case file on this site is written up from a genuine enquiry handled for customers across York and North Yorkshire, anonymised to keep client confidence. Each one sets out the diagnostic reasoning and the recovery method our engineers apply to that fault, on the equipment named.
Years on a shelf stiffen the mechanism, not the recording — freed in clean air, not spun until it gives in
Five machines can't all be wrong — power without presentation points at firmware or board, read past directly
A business drive that quit overnight gets urgency of the useful kind — method, priority, and no shortcuts
Free diagnostic inside 2 working days of arrival, one fixed quote, no fix no fee on logical faults — start online or ring the freephone.