Data Recovery Case File · Portable Drives · The Number Is the Finding
An Estimate in Months Measures How Little of the Time Is Spent Transferring
His enquiry contains a figure that diagnoses the drive without anybody looking at it. A 2TB external where the system reports that it cannot repair the disk and advises making a copy — "when I try to do so, I'm given a timeline of something between 56 and 200 days." That is a few hundred kilobytes a second on a drive that should manage a hundred megabytes, which means it is spending almost all of its time retrying rather than reading.
| Media | 2TB external hard drive — host repair declined with a copy advised; copy throughput collapsed to a small fraction of normal; estimate fluctuating widely |
| Reported situation | External drive not repairable according to the host utility · host advising a copy be made first · copy attempted · completion estimated between 56 and 200 days · estimate varying widely during the attempt · contents required |
| Fault class | Severe read degradation with throughput collapse — host retry behaviour consuming the available time; fluctuating estimate indicating scattered rather than uniform failure |
| Equipment used | Throughput estimate interpreted as a retry measurement rather than a transfer rate · host copy abandoned before proceeding · Atola Insight Forensic error-rate assessment across the surface · imaged write-blocked under strict per-sector timeouts with retries capped and difficult regions deferred |
The decode: what that estimate is actually measuring
Why the advice to copy was correct: the system found a volume it could not repair and told him to preserve the contents before attempting anything further. That is the right order, and it is unusual for a host utility to say so.
What the estimate reveals: arithmetic. Two terabytes across two hundred days is a few hundred kilobytes per second — roughly a thousandth of what a healthy drive of that kind sustains. A drive moving data at that rate is not transferring slowly; it is barely transferring at all.
Where the time is actually going: retries. When a read fails, the system reissues it, waits for a timeout, reissues again, and works through its full retry sequence before moving on — and each of those cycles takes seconds. A drive with many failing regions spends nearly all of its time in that loop.
Why the estimate swings so widely: the figure is projected from recent throughput. Between 56 and 200 days means the rate is fluctuating by a factor of several as the copy crosses readable and unreadable areas — which is characteristic of scattered failures rather than uniform degradation, and it means substantial healthy regions remain.
Why the copy must not be attempted: it would mean months of continuous operation on a drive already struggling. No failing drive survives that, and it would stop long before finishing, having spent its remaining reads on whatever happened to be near the beginning.
What is done differently, and it is the whole difference: per-sector timeouts capped in milliseconds rather than seconds, so a failing region is abandoned immediately instead of consuming a full retry sequence. The healthy majority is captured at speed first, and difficult regions are revisited afterwards across separate passes.
Why that turns months into hours for most of the content: the time was never in the reading — it was in waiting for failures to give up. Removing the waiting removes the estimate.
What is genuinely encouraging here: the drive is still reading. A rate that is poor is a rate, and scattered failures with healthy regions between them is a considerably better position than a drive that returns nothing.
On the bench
The throughput estimate was interpreted as a retry measurement rather than a transfer rate — two terabytes across two hundred days representing a small fraction of normal throughput, which indicates time consumed by the host's retry sequence rather than by reading, with a widely fluctuating projection indicating scattered rather than uniform failure. The host copy was abandoned before proceeding, and imaging performed under strict per-sector timeouts with retries capped and difficult regions deferred.
The outcome
The estimate read as a retry measurement, the host copy abandoned, and imaging performed under capped timeouts with difficult regions deferred. 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: that estimate is the diagnosis. It measures time spent waiting for failed reads to give up, not time spent transferring — and a figure swinging between 56 and 200 days means substantial healthy regions remain.
A copy the system estimates in weeks or months
Cancel it — that estimate is a measurement rather than a schedule, and attempting it means months of continuous operation on a drive already struggling, which no failing drive survives. Work out what the figure means: terabytes across hundreds of days is a small fraction of normal throughput, and the time is going into retries, where each failed read works through a full timeout sequence taking seconds. A widely swinging estimate is actually encouraging, since it means the rate fluctuates across readable and unreadable areas rather than being uniformly poor. Capped timeouts abandon a failing region in milliseconds instead.
Cancel it — call Easy Data Recovery on 028 9002 0144; estimate read as a retry measurement, error rates assessed across the surface, imaged under capped per-sector timeouts with difficult regions deferred.
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.