Data Recovery Case File · Desktop Externals & Aging Drives · That Session Was the Window
Working Somewhere Else Proves Capability, and Failing There Afterwards Proves It Was Declining
Her enquiry describes a sequence rather than a state, and the sequence is the whole finding. A drive that "started not working on my laptop but works on my friend's one, then it stopped" — with no sound, no drop and cables already changed. Three observations in order: it failed, it worked, it failed again. That middle one proves the drive was capable of working, and its ending proves it was on the way down while she was watching.
| Media | External hard drive — failing on one host, functioning on a second host, then ceasing to function there also; no audible activity; no impact reported |
| Reported situation | External drive ceasing to function on the owner's computer · drive subsequently functioning on a second computer · drive ceasing to function on that computer also · no unusual sounds reported · no impact or handling incident reported · cable substituted without effect · guidance on options sought |
| Fault class | Progressive failure demonstrated across successive hosts — capability established by the working session; decline established by its ending; interface or firmware fault indicated over mechanical |
| Equipment used | The working session treated as evidence of capability and its ending as evidence of decline · further connection stopped · drive removed from the enclosure and addressed directly with imposed timeouts · current draw measured across the start-up cycle on a controlled bench supply · imaging under capped timeouts with occupied regions taken first |
The decode: what each stage in the sequence establishes
What the first failure alone would have suggested: the host. A drive that fails on one computer is often failing because of that computer, its port or its software.
Why the second stage appeared to confirm that: it worked elsewhere. A drive functioning on a different machine is the classic evidence that the first machine was at fault.
Why the third stage overturns it entirely: the second machine failed too. A drive that stops working on a computer where it had just been working eliminates the host as the explanation.
What the sequence therefore establishes: the drive was declining throughout. It was marginal on the first machine, still capable on the second, and no longer capable by the end of that session.
Why that is genuinely valuable information: it dates the decline. Most enquiries cannot say when a drive was last working, and hers can say almost exactly.
Why the working session was the window: content was reachable then. A drive presenting normally is a drive that can be copied, and that opportunity existed and closed.
Why saying so is not a criticism: nothing marked it. A drive that starts working again looks fixed rather than temporarily willing, and copying everything immediately is not the obvious response to something appearing to recover.
What the absence of sound contributes: it argues against the mechanism. A drive with no unusual noise and no impact history is more likely to have an interface or firmware fault than a mechanical one.
Why that is the more favourable reading: those faults leave the recording untouched. A drive that cannot present itself is not a drive that has lost anything.
What must happen now: no more attempts on any machine. Each one is a start-up on a device that has already demonstrated it is getting worse between them.
On the bench
The working session was treated as evidence of capability and its ending as evidence of decline — failure on one host suggesting that host, function on a second appearing to confirm it, and subsequent failure on that same second host eliminating the explanation entirely. The sequence therefore dates the decline, which most enquiries cannot do. Absence of sound and impact argues for interface or firmware rather than mechanical involvement. Draw was measured across the start-up cycle.
The outcome
The sequence read as capability followed by decline, further connection stopped, and the drive addressed directly outside its enclosure. Free assessment, one fixed written figure including VAT, 50% of parts and labour upfront with the balance only on successful recovery where the drive is opened. The decode: the middle observation is the important one. It worked on that machine, which proves it could — and then stopped there, which proves it was declining while you watched.
A drive that works somewhere else and then stops there too
Report the whole sequence rather than the current state — failed, worked, failed again is far more informative than not working, because the middle stage proves the drive was capable and its ending eliminates the host as the explanation. It also dates the decline, which most enquiries can't do. If a drive ever starts working again, copy everything immediately: it looks like a fix and is usually a window. Stop connecting it now, on any machine.
Tell us the sequence — call Cambridge Data Recovery on 01223 655015; the working session read as capability and its ending as decline, drive addressed directly, occupied regions captured first.
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.