It "powers up ok, it just doesn't get recognised by the computer". Somebody had looked at it already, said "all the data can be recovered", and mentioned "something about the partitions failing". The drive is fourteen years old. Spinning and being ready are two different states, and a drive gets stuck between them more often than people expect. Before a drive announces itself it must read its own internal tables — the service area where a manufacturer keeps its defect lists and translation maps — and if those or the partition structures above them are damaged, the drive turns quietly and tells the computer nothing. The earlier opinion was optimistic in tone but not unreasonable in substance.
| Media | A fourteen-year-old hard drive that powers up and spins normally but is never recognised by the computer, with an earlier assessment attributing it to failing partitions. |
| Reported situation | Hard drive, roughly fourteen years old · powers up and spins without difficulty · not recognised by the computer · earlier assessment blamed failing partitions and said the data was recoverable. |
| Fault class | Partition or firmware fault — the mechanism is sound, but damaged partition structures or service-area data stop the drive presenting itself. The recorded data is unaffected by the drive's age and is reached by addressing the structures on professional equipment and rebuilding from an image. |
| Equipment used | Read onto PC-3000 UDMA, a hardware write-blocker in front of it, firmware, service area and partition structures each assessed · service-area faults addressed at firmware level and the partition table reconstructed so the drive's contents became reachable · imaged out to DeepSpar, the filesystem taken apart in R-Studio, the data validated and written to fresh media. |
A hard drive has a section of platter reserved for itself, which no operating system ever sees. In it live the defect lists, the adaptive parameters and the translation tables that convert the addresses a computer asks for into the physical locations where data actually sits. The drive reads that region before it will report itself ready. Damage it and you get precisely this: a drive that spins sweetly, draws normal current, and is invisible to every machine you connect it to.
One layer up sit the partition structures, which are the map of how the usable space is divided. Those can fail on their own too, and the result looks similar enough from the outside that only proper equipment separates the two. Both are addressed the same way in principle — read the drive underneath its normal interface, repair or rebuild the structures, then image what is now reachable and work on the copy.
The age is a red herring, and worth saying so plainly. Fourteen years does not fade a magnetic recording; a drive of that vintage holds what it always held. What age does affect is the mechanism — bearings, lubricant, the general willingness of a drive to keep spinning once it has been asked to — which is a good argument for reading it once, properly, rather than repeatedly attempting to make it appear in Windows. The earlier assessment's confidence that everything was recoverable was reasonable, but it was a prediction, not a promise, and we would rather make it after imaging than before.
It went onto PC-3000 UDMA with a write-blocker sitting in front of it, which allows a drive that will not present itself to be interrogated at firmware level anyway. The service area, the translation tables and the partition structures were each assessed rather than assumed. The structural faults were addressed so the contents became reachable, the drive was copied to an image on DeepSpar in a controlled pass given its age, and the filesystem was parsed in R-Studio from that image with the recovered files checked before anything was written out.
Structures repaired at firmware level, partitions rebuilt, the drive imaged and the data put onto fresh media. The diagnostic cost nothing; the figure that followed was fixed, written and inclusive of VAT. The mechanism never needed opening and the work was structural rather than physical, so it ran on no fix, no fee: no data, no invoice. The drive was returned with the honest recommendation that fourteen years is a good innings and it should not be asked for a fifteenth.
Resist the urge to keep plugging it into different machines. A drive that spins and is not recognised has usually failed before the point at which any computer could help it — the fault is in the structures it reads about itself, not in the connection — so a fourth machine will tell you exactly what the first three did. What you should certainly not do is accept an offer to initialise the disk, create a partition or write a new partition table, because those overwrite the very structures a recovery rebuilds from. And if you have been told everything is recoverable, treat that as an informed guess rather than a guarantee: the honest version of that sentence comes after the drive has been imaged, not before.
Every case file here is written up from a real enquiry handled for households and businesses across Norwich and Norfolk, anonymised so that nobody is identifiable. Each sets out the reasoning behind the diagnosis and the method used on that particular fault, with the equipment named.
Intermittent is not lucky, it is a countdown — and the silence at the end of it is the motor or the heads
Two noises, two facts: the whir says the motor is fine, the click says the heads are not
No spin means no conversation — the fault is in the power path or the mechanism, and the BIOS is only reporting the silence
Diagnosis costs nothing and takes up to 2 working days from arrival, the quote is fixed in writing, and logical work runs no fix, no fee — start online or ring the freephone.