Data Recovery Case File · Desktop Externals & Aging Drives · Certain, Not All
Failing on Particular Files Means the Damage Sits in Particular Places
His enquiry contains one word that does most of the diagnostic work. A 3TB drive behaving strangely for months, working intermittently and freezing "when reading certain files" — with the disk utility reporting no issues and the behaviour getting worse. Certain rather than all is the finding: the drive reads the majority of its surface and stops dead on specific regions, which makes the damage mappable.
| Media | 3TB external hard drive — reading the majority of content while consistently failing on specific files; host applications suspending during those reads; utility reporting no fault |
| Reported situation | External drive behaving abnormally over several months · drive working intermittently · reads of certain files causing the drive and host applications to suspend · owner eventually disconnecting the drive to recover the host · host utility reporting no issues found · condition described as worsening · recovery sought |
| Fault class | Localised unreadable regions on an otherwise functional surface — failures reproducible per file; progressive extension of affected areas indicated |
| Equipment used | Reproducibility per file interpreted as regional rather than general degradation · no further host access permitted · imaged write-blocked under strict per-sector timeouts with readable regions taken first · unreadable regions mapped and revisited across later passes · recovered content reconciled against the directory |
The decode: what certain files establishes, and why the utility found nothing
Why the word certain matters so much: it means the failure is reproducible and specific. The same files fail and other files do not, which is a very different finding from a drive that is generally slow or generally unreliable.
What that establishes about the surface: most of it reads. The mechanism works, the heads position correctly, and the great majority of regions return data — so this is not a failing drive in the general sense.
What it establishes about the damage: it occupies particular places. Files fail because the regions holding them cannot be read, and a file is simply a name for a set of regions.
Why that makes it mappable: a fault confined to locations can be surveyed. Imaging identifies exactly which areas do not return, and everything outside them is recoverable at full speed.
Why the freezing is the host rather than the drive: an ordinary read has no mechanism for giving up. The application waits indefinitely for a response that is not coming, and the wait propagates until he disconnects the device.
Why pulling it out to recover the machine is costly: disconnecting a drive mid-operation is an abrupt removal. It is the only option a frozen application leaves, which is a reason to stop reaching that point rather than a criticism.
Why the utility found no issues: it checks the filesystem's own consistency rather than reading every region. A volume whose structures are intact reports as healthy while individual content areas are unreadable — the check never touches them.
Why that is worth stating plainly: a clean report from a disk utility is not a clean bill of health. It answers a narrower question than most people take it to.
Why getting worse is the important half: localised damage that spreads is different from localised damage that sits still. Regions currently readable are becoming unreadable, so the proportion recoverable is falling while the drive stays in use.
What follows from that: the window is now. Imaging captures the readable majority first and returns to the difficult areas afterwards — the opposite of an ordinary copy, which stops at the first region that will not answer.
On the bench
Reproducibility per file was interpreted as regional rather than general degradation — consistent failure on specific files with others reading normally establishing that the mechanism, positioning and the majority of the surface function, while the affected files occupy regions that do not return. Host suspension reflects an ordinary read waiting indefinitely rather than drive behaviour. Filesystem utilities verify structural consistency without reading content regions. Imaging took readable regions first with unreadable areas revisited across later passes.
The outcome
Reproducibility read as regional degradation, further host access stopped, and readable regions captured first under capped timeouts. 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: certain rather than all is the diagnosis. Most of your surface reads, the damage sits in particular places, and it is mappable — but it is spreading, which is why the window is now.
A drive that fails on some files and not others
Stop using it and have it imaged now, because localised damage that's spreading means the recoverable proportion is falling while you keep reading it. The pattern is genuinely good news as a diagnosis: consistent failure on particular files with others fine means the mechanism works and most of the surface reads, so the damage occupies specific places and can be mapped. Don't be reassured by a disk utility reporting no issues — it checks the filesystem's structural consistency and never reads your content regions at all.
Stop using it — call Manchester Data Recovery on 0161 871 0788; reproducibility read as regional degradation, imaged under capped timeouts with readable regions first, unreadable areas revisited across 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.