Call us — 01223 655015
Mon–Fri · 9am–5:30pm · No fix, no fee
Start a free diagnostic →

Data Recovery Case File · Desktop Externals & Aging Drives · Reading Two Different Amounts

Listing a Directory Reads Kilobytes and Copying a File Reads Everything It Contains

His enquiry separates two behaviours that people usually report as one fault. An old internal drive holding archives held nowhere else, taken from a machine unused for years and connected through a caddy, where "I can see the file structure but whenever I try and copy anything the drive freezes." Those are different demands on the same drive, and the gap between them is the diagnosis rather than an inconsistency.

MediaInternal hard drive removed from a long-unused machine and connected through an adapter — directory structures listing normally; copy operations causing the drive to stop responding
Reported situationInternal drive removed from a machine unused for several years · drive connected externally through an adapter · file structure listing correctly · copy operations initiated · drive ceasing to respond during each copy · archived content held nowhere else
Fault classStructures readable with content regions degraded — brief small reads succeeding where sustained transfer fails; long idle storage a contributing factor
Equipment usedListing success distinguished from transfer success as differing read demands · copying through the host stopped immediately · drive addressed with imposed timeouts outside any operating system storage stack · imaged under strict per-sector timeouts with healthy regions taken first · degraded regions revisited across later passes with results compared

The decode: why the two behaviours differ, and what years of storage contribute

What listing a directory actually reads: very little. Structures describing an entire folder occupy kilobytes and sit in one place, so a listing is a short read of a small region.

What copying a file demands instead: everything in it. Every sector the file occupies must be read successfully, and a large file spans a wide area of the surface.

Why that difference produces exactly what he describes: the small read succeeds. A drive whose structures sit in a healthy region lists perfectly while its content regions cannot be traversed.

Why the drive freezes rather than reporting an error: it is retrying. A sector that does not read is attempted repeatedly, and the operating system waits without any imposed limit.

Why that appearance of a freeze is misleading: the drive is working hard. Nothing has stopped — it is repositioning heads and re-reading, and the host has nothing to display while it does.

Why cancelling and retrying is the worst pattern: nothing accumulates. Each cancelled copy abandons the file, so repeated attempts spend the drive's working life reaching the same point and stopping.

Now the years of storage, which is a real factor: drives do not like standing. Lubricant migrates, and heads resting against surfaces for long periods can leave residue.

Why that particularly affects a first use after long idleness: the first spin-up is the hardest. A drive returning to service after years faces its greatest mechanical demand at the moment it starts.

Why he has nonetheless already had the best of it: it started and listed. A drive that spun up and returned its structures has passed the difficult moment.

What must happen now: no more copy attempts. The listing has already told him what is there, and every further attempt is spent on the regions least able to bear it.

On the bench

Listing success was distinguished from transfer success as differing read demands — directory structures for a whole folder occupying kilobytes in one place, so a listing is a short read of a small region, while copying requires every sector a file occupies across a wide area. Apparent freezing is sustained retrying without an imposed limit rather than a stopped drive. Long idle storage makes the first spin-up the greatest mechanical demand. Healthy regions were captured first.

The outcome

Listing distinguished from transfer as differing demands, copying through the host stopped, and healthy regions captured first under capped timeouts. Free assessment, one fixed written figure including VAT, 50% of parts and labour upfront with the balance only on successful recovery where the drive is opened. The decode: the two behaviours are one finding. A listing reads kilobytes from one place and a copy reads every sector a file occupies — so your structures are in a good region and your content is not.

A drive you can browse but not copy from

Stop trying to copy, and don't cancel and retry — each cancelled copy abandons the file, so repeated attempts spend the drive's working life reaching the same point. The two behaviours aren't contradictory: listing a folder reads kilobytes from one small region, while copying reads every sector a file occupies across a wide area. The apparent freeze is the drive retrying without any imposed limit. After years idle, the fact that it spun up and listed at all is the hard part passed.

Can list the files but not copy them?
Stop copying — call Cambridge Data Recovery on 01223 655015; listing distinguished from transfer as differing demands, addressed outside the operating system stack, healthy regions captured first.
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.