Data Recovery Case File · Portable Drives · The Boundary Is the Finding
Reading the Top Level and Failing Below It Places the Damage at a Specific Depth
His enquiry is set out as numbered steps, and the sequence locates the fault precisely. A drive that spools up on a known-good cable, where "I can view the top level directory and all the folders in it" and then "the drive crashes when attempting to access a folder" — with the sound stopping when it does. The boundary between what reads and what does not is the diagnosis: the outermost structures return and the ones describing their contents do not.
| Media | 1TB portable hard drive — root directory listing successfully; drive ceasing activity when subdirectory content is requested; behaviour consistent across attempts |
| Reported situation | Drive connected using a cable known to be sound · drive spinning up normally · top-level directory listing completely · drive ceasing activity when a folder is opened · rotation stopping at that point · some folders opening before the same result follows · recovery sought |
| Fault class | Read failure at defined depth — root structures readable and subdirectory regions failing; drive halting rather than returning errors, indicating recovery-stall behaviour |
| Equipment used | Failure depth treated as locating the damage rather than as general unreliability · no further host access permitted · imaged write-blocked under strict per-sector timeouts with readable regions taken first · stalled regions deferred and revisited across later passes with controlled power cycling · directory structures reconstructed from their duplicate copies |
The decode: what the boundary means, and why the drive stops rather than erring
How a filesystem is arranged in layers: the root describes folders, each folder describes its contents, and those describe files. Reading deeper means reading further structures, each held somewhere else on the surface.
Why listing the top level succeeded: the root sits in a known location and is small. It is among the most frequently read regions on any drive and among the first written, and it returned intact.
Why opening a folder fails: that requires a different region. Each folder's contents are recorded elsewhere, so opening one asks the drive to read somewhere it has not yet been asked to go.
Why that makes the depth diagnostic: the failure is regional rather than general. The drive reads what it is asked for until it is asked for the wrong place, and the boundary maps where those places are.
Why some folders open and others do not: their structures sit in different regions. The pattern follows the physical layout rather than anything about the folders themselves, and it is reproducible.
Why the drive stops rather than reporting an error, and this is the important part: it is attempting recovery. A drive encountering a region it cannot read enters an internal routine, and if that does not resolve it halts rather than returning.
Why the sound stopping confirms it: rotation ceases. The drive has taken itself out of service rather than continuing, which is protective and also why nothing further can be read until power is cycled.
Why ordinary copying cannot work around it: a copy walks the directory. It will reach the same regions in the same order and stall in the same place every time.
What is done instead: imaging by region rather than by file, with strict timeouts so a stall is abandoned rather than waited on, and controlled power cycling to resume. Readable areas are captured first and difficult ones revisited.
Why the outlook is reasonable: the great majority of the surface has not been tested. A drive that stalls on particular structures may hold most of its content in regions that read normally, and the directory can be rebuilt from duplicates.
On the bench
Failure depth was treated as locating the damage rather than as general unreliability — filesystems recording folder contents in regions distinct from the root, so opening a folder requires reading somewhere not previously requested, and a reproducible boundary maps those regions. Drives encountering unreadable areas enter internal recovery routines and halt rather than returning errors, ceasing rotation. Ordinary copying walks the directory and stalls identically. Stalled regions were deferred and revisited with controlled power cycling.
The outcome
Failure depth treated as locating the damage, host access stopped, and readable regions captured first with stalls 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: the boundary is the diagnosis. Your root directory reads and the structures describing folder contents do not — and the drive halting rather than erring is it taking itself out of service.
A drive that lists folders and stalls when you open one
Stop trying, and don't attempt an ordinary copy — it walks the directory in the same order and will stall in the same place every time, power-cycling the drive repeatedly for nothing. Your numbered account is genuinely useful: the root directory sits in a known location and reads, while each folder's contents are recorded elsewhere, so the boundary between what opens and what doesn't maps the damaged regions. The drive stopping rather than reporting an error is it entering a recovery routine and taking itself out of service.
Don't attempt a copy — call Cambridge Data Recovery on 01223 655015; failure depth treated as locating the damage, imaged by region under capped timeouts, stalls deferred and revisited.
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.