Data Recovery Case File · Portable Drives · Two Faults, One Solved
He Fixed Something, and the Next Fault Became Visible
His enquiry reads as a failure and describes a success. An external drive working in the morning and not by the afternoon: "I bought new connectors and this meant that the drive was found on the computer, but not able to do anything." The drive still does not work, so it feels as though the purchase achieved nothing. It changed the symptom, which means it solved a fault — and what he is looking at now is a second one that was hidden behind the first.
| Media | External hard drive — failing to initialise on the original cabling; enumerating but not presenting a usable volume following cable replacement |
| Reported situation | Drive functioning normally in the morning · failing to initialise later the same day · replacement connectors obtained by the owner · drive detected by the computer following replacement · no usable access to content · contents required |
| Fault class | Two sequential faults — cabling resolved by owner intervention; residual fault at volume or drive level now isolated |
| Equipment used | Owner's cable replacement accepted as elimination of the interface layer · drive assessed on a native connection with the enclosure also eliminated · readiness sequence read under strict timeouts · imaged write-blocked · structures rebuilt from surviving copies on the image |
The decode: what a changed symptom means
Why the purchase was not wasted: before, the drive did not initialise at all. Now it is found by the computer. Those are different states, and something moved between them — which means the cabling was genuinely part of the problem and replacing it genuinely fixed that part.
Why it feels like a failure: because the goal was access to files, and he does not have it. But diagnosis works by changing one thing and observing what happens, and a symptom that changes in response to an intervention is the most informative result available. A symptom that does not change tells you only what to rule out.
Why two faults at once is more common than it sounds: a cable failing on the same day as a drive is unlikely as coincidence, but they are frequently related. Marginal cabling delivers unstable power, and a drive running on unstable supply can be interrupted mid-write — which damages its filing structures. So the first fault plausibly caused the second, which explains both the timing and the sequence.
What "found but not able to do anything" describes: the device enumerated and announced itself, and no volume could be mounted. So the interface layer is working — cable, port, and the enclosure's bridge — and the failure is at the filesystem or the drive itself. That is a much narrower position than where he started.
Why the enclosure is still worth eliminating: a cable is one part of the path. The bridge board inside the enclosure is another, and it may have suffered from the same unstable supply. Connecting the drive natively removes the last piece of the interface from consideration, and if the volume appears at that point, the case is essentially over.
What the morning-to-afternoon timeline suggests: a discrete event rather than gradual decline. Something happened during that day — a knock, a power interruption, an unclean disconnection — and identifying it, if anybody can, would narrow this further.
What must not happen now: no format and no repair. A drive that enumerates without presenting a volume is precisely what a system offers to initialise, and that offer will appear on every connection.
On the bench
The owner's cable replacement was accepted as elimination of the interface layer — a symptom changing in response to an intervention being the most informative diagnostic result available, and confirming the cabling was genuinely part of the fault. The drive was assessed on a native connection with the enclosure's bridge also eliminated, marginal cabling and a marginal bridge frequently sharing a cause. The readiness sequence was read under strict timeouts, the drive imaged write-blocked, and structures rebuilt from their surviving copies on the image.
The outcome
The interface eliminated by the owner's own intervention, the enclosure ruled out natively 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: your purchase was not wasted. The drive went from not initialising to being found, and a symptom that changes in response to an intervention is the most informative result there is. You solved one fault and revealed the next.
Replacement cable that changed the symptom without fixing it
That wasn't wasted money — it was a real diagnostic result. Your drive went from not initialising at all to being found by the computer, and a symptom that changes in response to an intervention tells you far more than one that doesn't. It means the cabling genuinely was part of the problem and you genuinely fixed that part; what you're looking at now is a second fault that was hidden behind the first. Those two are often related rather than coincidental, because marginal cabling delivers unstable power and a drive interrupted mid-write ends up with damaged filing structures. Worth trying the drive on a direct connection too, to rule out the enclosure's own board. Don't format it.
That's progress — call Guildford Data Recovery on 01483 901310; interface eliminated by your own test, enclosure ruled out on a native connection, structures rebuilt from their surviving copies.
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.