Data Recovery Case File · Desktop Externals & Aging Drives · Listing Is Not Reading
A Directory Is Small and the Files It Describes Are Not
His enquiry describes a drive that looks healthier than it is. A twenty-year-old drive that "still shows the files but will not transfer them to my newer drive", with a few hundred gigabytes he would like to keep. Seeing a file list is not evidence that the files can be read — a directory occupies a tiny area, and being able to read it says nothing about the far larger regions holding the content.
| Media | 300GB hard drive approximately twenty years old holding around 220GB — directory listing available, file transfer failing; selected folders required |
| Reported situation | Drive approximately twenty years old · recently beginning to behave unreliably · file listing displaying normally · transfer to newer media failing · around 220GB held · specific folders required · transfer to replacement solid-state media requested |
| Fault class | Directory readable with content regions failing — read degradation concentrated outside the structural areas; age-related surface and component degradation indicated |
| Equipment used | Directory availability distinguished from content readability · drive removed from ordinary use before capture · imaged write-blocked under strict per-sector timeouts with healthy regions taken first · marginal regions revisited across later passes · recovered content transferred to supplied replacement media |
The decode: why one works and the other does not
What listing a folder actually requires: reading the structures that describe its contents. Those are compact records — names, sizes, dates and locations — occupying a small, concentrated area of the drive, and reading them is a brief operation.
What copying a file requires instead: reading every region the file occupies. A folder listing of two hundred gigabytes might be a few megabytes of structure, while the content is the whole of the rest — so the two operations touch vastly different amounts of the drive.
Why that explains his symptom precisely: the small structural area still reads and the large content areas do not. The drive is not lying about the files existing; it simply cannot return them, which is a specific and common failure pattern.
Why it is such a convincing illusion: a complete file list looks like a working drive. Everything is visibly there, with correct names and sizes, and the failure only appears when something is actually asked for.
What twenty years accounts for: both surface degradation and component ageing. Reallocated sectors accumulate over a drive's life until the reserve of spares is exhausted, after which regions that fail can no longer be substituted — and a drive of that age is well past where that becomes likely.
Why an ordinary copy is the worst tool for this: it proceeds in folder order and stops or stalls at the first unreadable region. Hours are spent on a single difficult file while healthy material further down the list is never reached.
What is done instead: the drive is imaged with strict per-sector timeouts so no region absorbs the available time, healthy areas are captured first at full speed, and marginal regions revisited across later passes. A region that fails on one attempt frequently returns on another, and patient repetition recovers what a single pass cannot.
Why his selective scope helps: he wants specific folders rather than everything. Knowing which ones means the regions holding them are prioritised, which matters on a drive whose remaining reads are limited.
Why continued transfer attempts are the risk: each is another sustained read across degrading surfaces. The drive's remaining working life is being spent on attempts that are structurally unable to succeed in the way he is making them.
Why his plan for the destination is right: recovered content goes to new media, never back to the source. A drive of this age should be retired once its contents are elsewhere rather than returned to service.
On the bench
Directory availability was distinguished from content readability — folder listing requiring only compact structural records occupying a small concentrated area, whereas copying requires reading every region a file occupies, so a readable directory with failing transfers indicates degradation concentrated outside the structural areas. Accumulated reallocation exhausting the spare reserve over a drive's life accounts for age-related failure. Imaging ran write-blocked under strict per-sector timeouts with healthy regions taken first.
The outcome
Directory availability distinguished from content readability, the drive imaged under capped timeouts with healthy regions first, and content transferred to supplied replacement media. 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: seeing the list is not evidence the files can be read. A directory is a few megabytes of compact records; the content is everything else — so the small area still reads while the large ones do not.
A drive that lists everything and copies nothing
Stop attempting transfers, because each one is a sustained read across degrading surfaces that cannot succeed the way you're making it. The illusion is convincing: a complete file list with correct names and sizes looks like a working drive. But listing a folder only reads compact structural records in a small concentrated area, while copying a file reads every region it occupies — so the small area works and the large ones don't. An ordinary copy also proceeds in folder order and stalls at the first bad region, spending hours there while healthy material further down is never reached. Say which folders matter.
Stop transferring — call Easy Data Recovery on 028 9002 0144; directory availability distinguished from content readability, imaged under capped timeouts with healthy regions first, marginal 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.