Data Recovery Case File · Second Fixes & Trade Handoffs · The Attempt Is Information
A Failed Copy Tells You the Drive Was Reached and Then Would Not Give It Up
This enquiry arrives after a high-street attempt. An external drive that stopped being recognised and disappeared from the system, where a retailer "has been unable to access or recover the data and transfer it to a new external drive" and advised a specialist. What they tried is as informative as what they concluded — a transfer attempt means the drive was connected and worked on, and that has both told us something and cost something.
| Media | 1.5TB external hard drive — no longer recognised and absent from the host; transfer to replacement media attempted by a retailer without success |
| Reported situation | External drive no longer recognised · drive absent from the system · retailer unable to access the content · attempted transfer to a replacement external drive unsuccessful · specialist recovery advised · contents required |
| Fault class | Device not presenting to the host with a failed transfer attempt in its history — extent of prior powering and write activity determinative of current state |
| Equipment used | Prior attempt assessed for powering and write activity before any new work · absence from the host distinguished from a filesystem-level fault · current draw measured on a controlled bench supply · imaged write-blocked under strict per-sector timeouts · healthy regions captured first |
The decode: what a failed transfer establishes, and what it may have used up
What attempting a copy implies about their process: they connected the drive and tried to read from it. A transfer is not a diagnostic — it is an attempt to move data, which presupposes the data can be reached, so the attempt tells us they got at least far enough to try.
Why their failure is a narrower finding than it sounds: a general retailer works with ordinary tools on machines that mostly work. "Unable to recover" from that starting point means it could not be done with standard equipment, which is a statement about the equipment as much as about the drive.
What the important unanswered question is: how many times the drive was powered during the attempt. A transfer that fails partway is often retried, and each retry is a full power-up and another pass at whatever is failing — so the number matters and is worth asking them directly.
Why write activity is the other thing worth establishing: a copy in the intended direction reads from the failing drive and writes to the new one, which is harmless to the source. Any repair, check or clone attempted alongside it is not, and a good-faith account of what was run costs nothing to obtain.
What the symptom itself narrows to: the drive is not appearing at all. That places the fault before any filesystem question — not a volume that cannot be read, but a device that is not announcing itself, which is a device-level condition.
Why that is consistent with their result: a drive that does not present itself cannot be copied by any ordinary means. Their tools were never going to reach it, and the attempt failing at that stage is expected rather than surprising.
What is done differently: the drive is assessed on a controlled supply rather than a host connection, so power draw and behaviour are observed directly. Where it can be brought to present itself, it is imaged under capped timeouts with healthy regions taken first — the order dictated by condition rather than by folder structure.
Why capturing to an image rather than copying to a new drive matters: a file-level transfer stalls at the first difficult region and may never reach the healthy material beyond it. An image proceeds by condition and does not stop, and every subsequent question is answered from the copy.
What must not happen now: no further attempts of the same kind. The drive has already been through one round of powering and retrying, and a second adds cost without adding information.
On the bench
The prior attempt was assessed for powering and write activity before any new work — a transfer presupposing readable data and therefore failing at the point of access, with each retry constituting a full power-up and further pass at the underlying fault, while a copy in the intended direction reads from the source harmlessly and any repair or clone alongside it does not. Absence from the host was distinguished from a filesystem-level fault, indicating a device not completing enumeration. Imaging ran write-blocked under strict per-sector timeouts with healthy regions captured first.
The outcome
The prior attempt assessed for powering and write activity, the fault placed below any filesystem question, and imaging performed under capped timeouts. 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: a failed transfer is a statement about ordinary equipment as much as about your drive. It never presented itself to the host, so a copy was never going to reach it — and what matters now is how many times it was powered trying.
After a shop has tried to copy your drive and failed
Ask two specific questions rather than accepting the conclusion: how many times the drive was powered during the attempt, and whether anything besides a copy was run against it. Each retry is a full power-up and another pass at whatever is failing, and while a copy in the intended direction reads harmlessly, a repair, check or clone doesn't. Their result is also narrower than it sounds — a general retailer using standard tools concluding it can't be done says as much about the equipment as the drive. If your drive never appeared on the system at all, a copy was never going to reach it.
Ask what was run — call Easy Data Recovery on 028 9002 0144; prior attempt assessed for powering and write activity, draw measured on a controlled bench supply, imaged under capped timeouts with healthy regions 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.