Data Recovery Case File · Second Fixes & Trade Handoffs · Two Classes of Problem
His Earlier Successes Taught Him a Lesson That Does Not Extend
His enquiry describes a tool that has served him well and has now stopped serving. A drive holding thirty years of work that simply failed, where "I have successfully used recovery software in the past, but when I tried again this time it wouldn't" run. The software has not become worse — his previous problems were of one kind and this one is of another, and no program of that sort crosses the line between them.
| Media | 2TB hard drive holding approximately thirty years of accumulated work — device-level failure; consumer recovery software unable to proceed |
| Reported situation | Drive holding approximately thirty years of work · drive failing during a period of extended use at home · consumer recovery software previously used successfully on other occasions · software unable to proceed on this occasion · contents required |
| Fault class | Device-level failure beyond the reach of host-mediated software — prior successes attributable to logical faults of a different class |
| Equipment used | Prior successes attributed to logical faults before any conclusion about the tool · device addressed through hardware with imposed timeouts rather than through the host stack · Atola Insight Forensic error-rate assessment · imaged write-blocked under strict per-sector timeouts |
The decode: the line those tools cannot cross
What his previous problems almost certainly were: logical. Deleted files, an emptied bin, a formatted volume, a filesystem that stopped mounting — situations where the drive works perfectly and the description of its contents is damaged or removed.
Why software is exactly right for those: the medium can be read normally, so a program can scan it, find content the filesystem no longer references, and write it out. That is a genuine and well-solved problem, and consumer tools do it competently. His successes were real.
What is different this time: the software would not run. Not that it ran and found nothing — it could not proceed, which means it could not read the device.
Why no program can help with that: recovery software asks the operating system to read the drive. It inherits the system's timeouts, its error handling and its behaviour when a device stops answering — so a drive that hangs, errors or fails to present defeats every program running on that system equally, regardless of quality or price.
So the distinction worth carrying: if the drive appears and behaves normally while the files are missing or unreachable, software is the right tool. If the drive does not appear, stalls, or produces errors, the problem is below the level software operates at — and trying more programs is trying the same approach repeatedly.
Why his experience made the wrong lesson so easy to draw: the tool worked several times, so it became the answer to "drive problem" rather than the answer to a specific class of drive problem. Nothing in his previous experience marked the boundary, because he never met it.
What works instead, and the difference is hardware rather than better software: the drive addressed directly with imposed short timeouts, so an unanswered request is abandoned rather than hung on, with difficult regions deferred and revisited. The operating system is removed from the path entirely.
What must stop: further attempts with more programs. Each is a full-surface read attempt on a failing drive, spending margin on an approach that cannot work.
The other thing worth saying: thirty years of work on a single device. Whatever comes back should go to two places.
On the bench
Prior successes were attributed to logical faults before any conclusion about the tool — consumer recovery software operating through the host, scanning a readable medium for content the filesystem no longer references, which is competent for deletion, formatting and mount failures. Software cannot address a device that hangs or fails to present, since it inherits the system's timeouts and error handling. The drive was addressed through hardware with imposed timeouts rather than through the host stack.
The outcome
Prior successes attributed correctly, the device addressed through hardware rather than the host stack, and error rates measured before any figure. 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: the software did not fail you. It works where the drive reads normally and the description of your files is damaged — and it cannot reach a drive the operating system itself cannot read.
Recovery software that worked before and will not now
Stop trying more programs — each attempt is another full-surface read on a failing drive, spending margin on an approach that can't work. There's a line those tools cannot cross. If the drive appears and behaves normally while files are deleted, formatted away or unreachable, software is exactly right and works well. If the drive doesn't appear, stalls, or throws errors, the problem is below the level software operates at, because every program asks the operating system to do the reading and inherits its timeouts and error handling. Your earlier successes were real; they just didn't mark where the boundary was.
Stop trying others — call Oxford Data Recovery on 01865 593000; addressed through hardware with imposed timeouts rather than the host stack, error rates measured, imaged under strict per-sector limits.
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.