Data Recovery Case File · Desktop Externals & Aging Drives · Do Not Mistake Recovery for Repair
Nothing Fixed It, So It Is Working Despite Something Rather Than Because It Improved
This enquiry describes a drive that failed on location and then appeared to come back. A rugged portable that "stopped responding whilst out on a job just after we had transferred files to it. Looked like a power loss. The head got stuck in place, but now the drive does read and respond — however we're unable to" access it fully. A drive that resumes after a stall has not been repaired, and partial function is the state most likely to be mistaken for improvement.
| Media | 1TB ruggedised portable hard drive — apparent power interruption during field use following a transfer; subsequent partial return of function; content not fully accessible |
| Reported situation | Drive in professional field use · files transferred to it · drive ceasing to respond immediately afterwards · apparent power interruption observed · mechanism reported as having stalled · drive subsequently reading and responding · content not fully accessible · contents required |
| Fault class | Unresolved fault with partial function restored — intermittent operation indicating persistence rather than resolution; capture window finite |
| Equipment used | Return of function treated as intermittency rather than resolution · no working use permitted during the available window · Atola Insight Forensic error-rate assessment · imaged write-blocked under strict per-sector timeouts · capture prioritised to the most recent transfer first |
The decode: why coming back is not the same as being fixed
What people conclude when a device recovers: that whatever it was has passed. The drive works, the files are visible, and the natural response is to carry on using it — which is entirely reasonable and is the most expensive available reading of the situation.
Why nothing has been repaired: no component was replaced, no fault was addressed, and nothing was done to it between failing and working. Whatever caused it to stop is still present, unchanged, and the drive is now operating around it.
What such faults typically are: a supply component sagging under load, a head that made brief contact and released, a connection that is marginal, or a controller failing to complete an operation and recovering on the next attempt. All of them come and go, and all of them get worse.
Why partial access is the confirming evidence: he cannot reach everything. A resolved fault produces full function; partial function is the signature of a fault that is still there and is affecting some operations and not others.
Why this state is more dangerous than outright failure: a dead drive gets taken somewhere. A working one gets used — and continued use on an unresolved mechanical fault is exactly how a recoverable situation becomes a scored one, as this archive has seen repeatedly.
So the correct reading of the current window: it is for capture, not for work. Every access should be spent copying rather than checking what survived, and the drive should not go back on a job under any circumstances.
What the timing suggests: it failed just after a transfer, which is sustained writing — the heaviest demand the drive had faced that day. Faults surface under load, and the transfer is more likely to have exposed the problem than to have caused it.
What ruggedisation does and does not cover: a rugged enclosure protects against impact, water and dust from outside. It offers no protection whatever against the drive's own electronics or mechanism failing, and field users reasonably assume more protection than exists.
On the bench
The return of function was treated as intermittency rather than resolution — nothing having been replaced or addressed between failure and recovery, so the originating fault persists and the drive operates around it, with partial access constituting evidence of an unresolved condition rather than a resolved one. No working use was permitted during the available window. Imaging ran write-blocked under strict per-sector timeouts with capture prioritised to the most recent transfer first.
The outcome
The recovery treated as intermittency, the window spent on capture rather than work, and the most recent material prioritised. 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: nothing repaired it. No component was replaced and nothing was done between it failing and working, so whatever stopped it is still there — and your partial access is the evidence that it is.
Drive that failed and then started working again
Treat the current window as time to copy, not time to work — and don't put it back into service. Nothing repaired it: no component was replaced and nothing was done between it failing and responding again, so whatever caused the stall is still present and the drive is operating around it. Your partial access confirms that, because a resolved fault produces full function. This state is more dangerous than outright failure, since a dead drive gets taken somewhere and a working one gets used. Worth knowing too that a rugged enclosure protects against impact, water and dust from outside, and offers nothing against the drive's own electronics.
Copy, don't work — call Oxford Data Recovery on 01865 593000; return of function treated as intermittency, error rates measured, imaged under capped timeouts with your most recent material 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.