Data Recovery Case File · Desktop Externals & Aging Drives · Unchanged and Not Unaffected
The Fault Has Not Moved and the Drive Has Aged
His enquiry describes a stable problem of unusual duration. A large old external drive where, "about seven years ago, it stopped being recognised by the computer but would still switch on and spin. Even now the computer still makes a recognition noise when connected and it comes up as a device I can eject in the system tray, but nothing shows in the file explorer." The symptom is precise and it has not changed in seven years — which is encouraging about the fault and says nothing reassuring about the mechanism that has been sitting still all that time.
| Media | Large-format external hard drive — enumerating as a device and presenting no volume since approximately 2016; spinning on power; stored unused since |
| Reported situation | Drive ceasing to present a volume approximately seven years previously · continuing to power and spin · host acknowledging connection and listing the device for ejection · no volume appearing in the file manager · drive stored unused since · behaviour unchanged throughout |
| Fault class | Enclosure bridge enumerating with volume unmountable — filesystem or drive-level failure, compounded by prolonged dormancy |
| Equipment used | Dormancy effects assessed alongside the original fault · drive removed from the enclosure and assessed on a native connection · readiness sequence read under strict timeouts · imaged write-blocked · structures rebuilt on the image |
The decode: what the symptom says, and what the years added
What the recognition noise and the ejection entry establish: the enclosure's bridge board is powering up, announcing itself on the bus, and being registered by the host. That is the interface working. It says nothing about the drive behind it, because the bridge answers for itself and the host lists what has introduced itself rather than what can be read.
What nothing appearing in the file manager means: no volume could be mounted. The system read whatever the drive presented, found no filing structure it could interpret, and declined to show anything. So the split is clean — interface alive, volume unreadable — and that has been the position for seven years.
Why a stable symptom is mildly encouraging: it means whatever failed did so once and then stopped changing. A drive that degrades progressively presents differently over time; one that has behaved identically for years suffered a discrete event. That is more consistent with structural damage than with an ongoing physical decline.
Now the part that has changed, and it is the reason not to wait longer. A drive that spins is not the same as a drive that has been spinning. This one has been sitting, largely unpowered, for seven years — and mechanisms develop faults in storage that have nothing to do with why they were put away. Lubricant migrates and thickens, so a spindle that turned freely can become stiff. Heads resting on a platter surface can adhere simply from remaining in contact long enough. The drive that arrives now is the drive that failed in 2016 plus everything seven years has added.
Why that matters practically: nothing about the fault has got worse, but the odds of the mechanism starting cleanly have. Each further year is a further reduction, and the case for acting is that the original problem is probably straightforward while the mechanical one gets harder.
What the assessment does differently because of the age: the drive is not simply powered and tested. Dormancy effects are assessed alongside the original fault, because a mechanism that has been still for seven years may not survive a casual spin-up — and a single unsuccessful attempt can convert a recoverable case into a mechanical one.
The general point for anyone with a drive in this state: a device that stopped working and was kept is a device on a slow clock. Storing it does not preserve the position; it preserves the fault while the mechanism ages around it.
On the bench
Dormancy effects were assessed alongside the original fault — seven years of storage thickening lubricant and allowing resting heads to adhere, conditions that were not present when the drive first stopped mounting and that a casual spin-up can convert into a mechanical case. The drive was removed from the enclosure and assessed on a native connection, taking the bridge out of the question, with the readiness sequence read under strict timeouts. It was imaged write-blocked and structures rebuilt on the image.
The outcome
The dormancy assessed alongside the original fault, the bridge eliminated on a native connection and the structures rebuilt from the image. Free assessment, one fixed written figure including VAT; where a drive has to be opened, 50% of parts and labour is payable upfront with the balance only on success — otherwise no recovery, no fee. The decode: the recognition noise and the ejection entry are the enclosure's bridge announcing itself, which says nothing about the drive behind it — and nothing appearing means no volume could be mounted. A stable symptom over seven years suggests a discrete failure rather than decline. But the mechanism has aged in storage regardless.
Drive that has been in the same broken state for years
Act on it rather than leaving it longer — storing a failed drive preserves the fault while the mechanism ages around it. Your symptom is actually a clean one: the recognition noise and the drive appearing as something you can eject are the enclosure's bridge board announcing itself on the bus, which tells you the interface works and nothing about the drive behind it. Nothing appearing in the file manager means no volume could be mounted, so the filing structures couldn't be interpreted. That's the recoverable combination, and a symptom unchanged for years suggests one discrete failure rather than ongoing decline. What has changed is the mechanism: lubricant thickens over years and resting heads can adhere, so the odds of a clean spin-up fall.
Don't leave it longer — call Guildford Data Recovery on 01483 901310; dormancy assessed alongside the original fault, bridge eliminated on a native connection, readiness read under strict timeouts.
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.