Data Recovery Case File · Portable Drives · A Message Is Not a Verdict
A Message That Sounds Final Is Usually a Report That Communication Failed
Her enquiry quotes a message written to sound like a conclusion. A drive that suddenly stopped working, where connecting it produces a warning that "your device has suffered a fatal error", tried on several computers without success — with photographs and video of her children as babies on it. That wording is doing more work than the software behind it: it reports that the host could not communicate, which is a symptom rather than a diagnosis.
| Media | External hard drive — host software reporting an unrecoverable device error; no volume presenting; behaviour consistent across multiple hosts |
| Reported situation | External drive ceasing to function suddenly · host displaying a message describing an unrecoverable device error · drive tried on several separate computers · behaviour identical on each · photographic and video content of the owner's children sought |
| Fault class | Communication failure between host and drive — message generic and not diagnostic; underlying cause to be established by measurement rather than from the wording |
| Equipment used | Host message treated as a report of failed communication rather than as a diagnosis · drive removed from the enclosure and addressed directly with imposed timeouts · current draw measured across the start-up cycle on a controlled bench supply · service area read under strict timeouts in vendor technological modes · imaged under capped timeouts with occupied regions taken first |
The decode: what the message can and cannot know
What the software producing that message actually has: very little. It knows a command was issued to the drive and did not complete, and that is the entire basis of the wording.
Why the language is so much stronger than the evidence: it is written for reassurance rather than accuracy. Manufacturer software uses definite phrasing so that people stop trying, which is good advice expressed as a false certainty.
What the message therefore genuinely establishes: the host could not talk to the drive. Nothing about the recording surface, the heads or the content follows from it at all.
Why the same message covers wildly different faults: they present identically to the host. A failed interface board, a drive not completing initialisation and a mechanical fault all produce a command that does not complete.
Why trying several computers was worth doing: it eliminated them. Identical behaviour on multiple hosts removes the port, the machine and the operating system from consideration.
Why that is genuinely useful rather than merely disappointing: it narrows the fault to the device. Everything outside the enclosure has now been excluded by her own testing.
How the actual cause is established: by measurement rather than by messages. Current draw across the start-up cycle shows whether the motor reached speed and whether the heads attempted to position, which no host can determine.
Why the enclosure comes off first: external units interpose a bridge board between the drive and the host. A bridge that has failed produces exactly this behaviour with a perfectly healthy drive behind it.
Why the sudden onset is worth noting: it fits a hardware cause. Filesystem damage usually produces a drive that appears and misbehaves, rather than one that stops being reachable at all.
What must not happen while she decides: no further connection attempts. If the drive is failing during initialisation, each attempt repeats whatever is failing.
On the bench
The host message was treated as a report of failed communication rather than as a diagnosis — the software knowing only that a command was issued and did not complete, with definite phrasing chosen to discourage further attempts rather than to describe a condition. A failed bridge board, incomplete initialisation and mechanical faults all present identically to a host. Consistent behaviour across multiple machines excludes port, host and operating system. Draw was measured across the start-up cycle.
The outcome
The message treated as a communication report, the drive addressed outside its enclosure, and draw measured across the start-up cycle. 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: that message knows one thing — a command did not complete. It is written to sound like a verdict so that people stop trying, which is good advice dressed up as a certainty about your photographs.
When software tells you a device has failed unrecoverably
Take the advice and ignore the certainty: stop connecting it, but don't read the wording as a statement about your files. The software knows only that a command didn't complete, and the definite phrasing is chosen to make people stop trying rather than to describe a condition — the same message covers a failed interface board, an incomplete start-up and a mechanical fault alike. Trying several computers was worth doing, since identical behaviour on each rules out the machines.
That is not a diagnosis — call Cambridge Data Recovery on 01223 655015; the message read as a communication report, drive addressed outside its enclosure, draw measured across the start-up cycle.
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.