Data Recovery Case File · Trust, Practice & Practicalities · The Process Question

"Is your success rate the same as others?" — the honest answer to the archive's most reasonable question, and a whining drive recovered by the process itself

His report needed no translation. A 2TB hard drive that "sometimes shows up as a mapped drive but cannot be accessed"; File Explorer running "extremely slow" and hanging whenever it was connected; "a whining sound when powered on." His response to all that was the single best sentence in the enquiry: "Haven't connected it back to the PC since failure, to preserve it as much as possible." He added a self-diagnosis with a twist — the drive had been shucked, taken out of an external casing and pressed into desktop service, "so I guess it wasn't built for as much up-time as it had in my PC" — and never dropped. And then he asked the two questions that give this case file its place in the archive: "I'm curious as to what your process is, as the site states the process you use is different to that used by other companies. Is your success rate the same as others?" Fair questions deserve straight answers, in public, which is what the rest of this page is.

The decode: what the symptoms were saying — and his shucking theory, graded

The trio, translated: a whine at power-up is the mechanism speaking — spindle or head assembly labouring where it once ran silent. "Mapped but inaccessible" and a hanging Explorer are the same fact seen from the software side: the drive answers the register, then takes so long over each difficult read that the system's patience collapses. Together they describe a drive in mechanical decline, still capable of reads but paying more for each one — the classic profile of a patient with limited performances left.

His theory, graded: partial credit, generously given. Externals and their re-housed innards aren't fundamentally different species, but duty cycle is real — a drive designed around intermittent use, run hard on desktop hours for years, has simply spent its wear budget faster. The deeper truth is kinder to him: age and accumulated hours were coming for this drive in any housing. What mattered most was what he did at the end — he stopped. Every symptom in his list gets worse with operation, and "preserve it as much as possible" is precisely the professional instinct.

The process question, answered plainly: the difference is that a failing drive here is never asked to serve files to an operating system at all. It is connected once to hardware imagers that read at sector level with error tolerance — skipping and returning to difficult regions, adjusting to the drive's weak areas, prioritising what matters, stopping the moment the mechanism protests — until a complete image exists. All recovery then happens on the copy, where nothing can be made worse. An operating system copies files and demands perfection; an imager harvests a failing drive and accepts what each pass can safely give.

The success-rate question, answered honestly: a single universal percentage is marketing, not measurement — success varies by fault class, and any figure quoted without that context should lower your confidence, not raise it. What can be said honestly: for a drive in this condition, outcomes are decided mostly by how little it is asked to do before imaging — which is why his early stop mattered more than any statistic — and the incentives are aligned in writing: free assessment, one fixed figure including VAT, and no recovery, no fee, which makes overpromising a losing strategy for the lab, not the customer.

The recovery: the process, applied

The drive was imaged on hardware imagers exactly as described above — gently, in drive-friendly order, its whine monitored as a health telemetry of its own. The mechanism held for one disciplined pass; the image completed; and the estate was extracted and verified entirely from the copy, the original never again asked for a file.

The outcome

His years of files delivered on new media, his quote honoured as asked, and his two questions answered the same way in private as this page answers them in public. The drive was retired with its whine intact — a distinguished veteran of rather more up-time than its designers imagined.

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.