Data Recovery Case File · Desktop Externals & Aging Drives · A Result, Not a Conclusion
A Scan Reporting Unreadable Areas Has Reported What It Could Not Read
Her enquiry quotes a technical finding and reads it as an outcome. A drive that was dropped, where "another company looked into the problem and found the media integrity scan failed. It suffered media corruption which led to inaccessible sectors and unreadable areas." That describes what happened during a scan — and a region a scan could not read under its conditions is not necessarily a region that cannot be read at all.
| Media | 2TB portable hard drive following impact — surface integrity scan reporting unreadable regions; prior assessment by a third party |
| Reported situation | Drive dropped · assessed by a previous provider · surface integrity scan performed and reported as failed · unreadable regions and inaccessible sectors reported · owner seeking a further assessment |
| Fault class | Surface read failures following impact — extent and recoverability under altered read conditions to be established; scan result indicating difficulty rather than absence |
| Equipment used | Prior scan result interpreted as conditions-dependent rather than definitive · laminar flow bench inspection with surface assessment before any spin attempt · Atola Insight Forensic error-rate assessment · imaged under strict per-sector timeouts with marginal regions re-read across multiple passes · losses mapped per file |
The decode: what a failed scan establishes and what it leaves open
What a surface integrity scan does: reads across the medium and records which regions respond and which do not. It is a measurement taken under particular conditions — a particular timeout, a particular number of retries, a particular temperature — and its result describes what happened under those conditions.
Why that matters: a marginal region is one that sometimes reads. The same sector may fail on one attempt and succeed on the next, or fail at speed and succeed when approached differently. A single pass records a snapshot rather than a permanent property.
So what "unreadable areas" means precisely: areas the scan did not manage to read. That is a real finding and it is not the same as areas containing nothing recoverable — and the distinction is the entire question here.
What frequently changes the result: multiple passes over the same regions, with capped timeouts so no single sector consumes the session, and revisiting difficult areas after the healthy expanse is safely captured. Regions that failed on a first pass routinely yield on a third or fourth.
Why that is not a criticism of the previous provider: a scan is a diagnostic, and its job is to establish extent. They measured and reported honestly, and the finding is useful — it says the surface has problems, which after an impact is what one would expect.
What the scan has already cost, and this is the part worth weighing: a full-surface read on a drive that has been dropped. If the impact damaged a head, every pass is that head travelling the surfaces, and there is a limit to how many such passes a damaged drive supports before regions genuinely do become unreadable.
Why the impact history matters more than the scan result: whether the drive was running when it fell, and whether it has been powered since. A head that made contact generates debris, and unreadable regions after a drop may be scoring rather than marginality — which is the difference between recoverable and not.
What is established before anything spins: surface condition under filtered air. That distinguishes damage from difficulty, and it is the finding the scan could not supply.
On the bench
The prior scan result was interpreted as conditions-dependent rather than definitive — a surface scan recording which regions responded under a particular timeout, retry count and temperature, so a marginal sector may fail on one attempt and succeed on another. Inspection ran under the laminar flow bench with surface assessment before any spin attempt, distinguishing physical damage from read difficulty, and imaging performed with marginal regions re-read across multiple passes.
The outcome
The prior result read as conditions-dependent, surfaces assessed before any rotation, and marginal regions re-read across passes. Free assessment, one fixed written figure including VAT, 50% of parts and labour upfront with the balance only on successful recovery. The decode: a scan reports what it could not read under its own conditions. Marginal regions fail on one pass and succeed on another — so unreadable during a scan and unrecoverable are different findings, and only inspection separates them.
Told a scan found unreadable areas
Ask whether the surfaces were inspected, not just scanned — that's the finding a scan can't supply and it's the one that matters after a drop. A surface scan measures which regions responded under a particular timeout and retry count, so a marginal sector may fail on one pass and succeed on another; unreadable during a scan isn't the same as unrecoverable. Multiple passes with capped timeouts routinely yield regions a single pass missed. But be aware what scanning costs on a dropped drive: if the impact damaged a head, every pass is that head travelling the surfaces, and there's a limit.
Call Easy Data Recovery on 028 9002 0144; prior result treated as conditions-dependent, surfaces assessed before any spin attempt, marginal regions re-read across multiple passes.
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.