Data Recovery Case File · Desktop Externals & Aging Drives · Almost Textbook
He Confirmed the Fault, Stopped, and Took It Out of Circulation
His enquiry describes handling that is close to ideal. A 3TB drive that failed within the last day, removed from the machine and tested once in a docking station "to test whether the drive was truly the issue, and it was" — a consistency check could not run, and "it's now disconnected from everything and being stored safely." That is the sequence that preserves the most: one deliberate test, a conclusion, and then nothing.
| Media | 3TB hard drive holding approximately 2 to 2.5TB — failed within the preceding day; confirmed faulty by a single external test; withdrawn from use and stored |
| Reported situation | Drive failing within the preceding twenty-four hours · approximately 2 to 2.5TB of content held · drive removed from the machine · single test performed through a docking adapter confirming the drive as the fault · consistency check unable to run as the drive was inaccessible · drive disconnected and stored · folders held at the top level of the volume |
| Fault class | Undetermined at device level with condition preserved — minimal powering since failure; access not achieved by ordinary means |
| Equipment used | Minimal powering since failure credited as preservation of condition · single confirmatory test accepted as sufficient without repetition · current draw measured on a controlled bench supply · service area and enumeration read under strict timeouts · imaging under capped timeouts with top-level structure used to scope priority |
The decode: what he did right, and what remains to be established
Why the single test was the correct amount of testing: it answered a real question. Moving the drive to a docking adapter separates the drive from the machine it was in, and unchanged behaviour there establishes that the fault travels with the drive — which is worth knowing and worth exactly one attempt.
Why stopping there is the part most people get wrong: the natural next step is another cable, another machine, another attempt. Each of those repeats a question already answered while spending whatever the drive has left, and the information gained after the first confirmation is nil.
Why the consistency check not running was fortunate: it was unable to reach the drive. Had it run, it would have written corrections to a volume nobody has yet assessed — and on a drive with unreadable regions, that discards references to intact content.
Why storing it disconnected matters: a drive that is not powered is not degrading. Whatever state it reached at the moment of failure is the state it is still in, and that is the best position anyone can be in a day after a failure.
Why the twenty-four hours is worth noting: nothing has intervened. No repair attempts, no software, no repeated power cycles — so the assessment begins from the original fault rather than from the original fault plus a week of well-intentioned attempts.
What has not yet been established, and cannot be from his account: what kind of fault it is. A drive that is inaccessible through a docking adapter may be failing electrically, mechanically, or at its firmware, and the docking adapter cannot distinguish them because it only supplies power and passes data.
Why that distinction requires different equipment: current draw across the start-up cycle, whether rotation is achieved, and whether the drive completes its own initialisation are electrical and mechanical observations. No consumer adapter reports any of them, which is why the next step is assessment rather than another connection.
Why the top-level folder arrangement he mentions is useful: everything sits at the root of the volume rather than nested. That makes scoping straightforward — folders can be prioritised individually without needing to reconstruct a deep hierarchy first.
Why his position on scope is sensible: not everything is essential, but if all of it is accessible there is no reason to leave any behind. That is the right way round — recover what can be reached, and prioritise only if the drive's condition forces a choice.
What must not happen: nothing further. The drive is already in the best condition it will be in, and the only way that changes is if somebody powers it again.
On the bench
Minimal powering since failure was credited as preservation of condition — a single external test separating the drive from its host and establishing that the fault travels with it, which requires one attempt and yields nothing on repetition, while an unpowered drive does not degrade further. The consistency check being unable to reach the drive prevented corrections being written to an unassessed volume. Current draw was measured on a controlled bench supply, electrical and mechanical observations being unavailable through a consumer adapter.
The outcome
Minimal powering credited as preservation, the single confirmatory test accepted without repetition, and the drive assessed on a controlled bench supply. 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: you did the right amount of testing and then stopped, which is the part most people get wrong. The drive is in the best condition it will be in — and the only thing that changes that is powering it again.
The right amount of testing after a drive fails
One deliberate test, then stop. Moving the drive to a docking adapter separates it from the machine and establishes that the fault travels with the drive — a real question, worth exactly one attempt. What most people do next is try another cable, another machine, another connection, each repeating a question already answered while spending whatever the drive has left. Don't let a consistency check run either: on an unassessed volume it writes corrections that discard references to intact content. Then disconnect and store it, because an unpowered drive isn't degrading and that's the strongest position available.
That is the right position — call Easy Data Recovery on 028 9002 0144; minimal powering credited as preservation, draw measured on a controlled bench supply, imaged under capped timeouts.
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.