Data Recovery Case File · Desktop Externals & Aging Drives · The Reverse of the Usual
The Structures Are in a Good Region and the Content Is Not
His enquiry describes a drive that shows him everything and gives him nothing. Shucked from its enclosure and connected directly, "it spools and shows the index, but still won't copy any files. I've tried recovery software, but it gets stuck and the drive disconnects." Most cases in this archive have damaged structures over intact content. This is the other way round — the directory reads perfectly, which means the regions holding it are healthy and the regions holding the files are not.
| Media | Hard drive removed from an external enclosure — directory structures reading completely; file content not retrievable; host disconnecting during copy operations |
| Reported situation | External drive failing to transfer data · drive removed from its enclosure by the owner and connected directly · directory listing presenting completely · file copying not completing · recovery software stalling · drive disconnecting during attempts · contents required |
| Fault class | Read failure distributed through the data area with structural regions intact — full directory available for loss reporting per file |
| Equipment used | Owner's shucking accepted as enclosure elimination · full directory captured first as a reference inventory · Atola Insight Forensic error-rate assessment · imaged write-blocked under strict per-sector timeouts with retries capped · losses reported per named file against the captured directory |
The decode: what a readable index and unreadable files tell you together
Why the usual pattern is the opposite: filing structures are small, concentrated in specific regions, and written constantly — every file created, renamed or moved updates them. That combination is why they usually break first, and why most recoveries here are about rebuilding a description over intact content.
What his drive is doing instead: presenting a complete directory. So the structural regions read correctly, which means those parts of the surface are in good condition. The failure is in the data area, which occupies the overwhelming majority of the drive — and damage distributed there produces exactly this: a perfect list of files that cannot be opened.
Why that indicates a physical fault rather than a logical one: structures being intact rules out the interrupted writes and unclean dismounts that damage descriptions. Something is preventing the drive returning content from large parts of its surface, and that is a read problem rather than a bookkeeping one.
Why the drive disconnects during copying: a request that is issued and never answered holds a slot in the system's queue while the drive retries — repositioning and escalating through an internal recovery sequence taking seconds per sector. Eventually the host's patience expires and it removes the device, which is what he is seeing as a disconnection.
Why his recovery software gets stuck for the same reason: it reads through the operating system, so it inherits the same timeouts and the same stalls. Its failure is not a comment on the software — no tool operating that way can work on a drive that does not answer.
What is done differently: imaging under strict per-sector timeouts, so a difficult region is given a short budget and deferred rather than allowed to consume the session. The healthy expanse is captured at speed first, and weak areas revisited on later passes — which recovers substantially more, substantially faster, than letting a drive retry freely.
Why the readable directory is genuinely valuable: it is a complete inventory of what should be there. Losses can be reported by name rather than as a percentage — this file returned, this one did not — which almost never happens and which makes the outcome checkable.
On the bench
The owner's shucking was accepted as enclosure elimination. The full directory was captured first as a reference inventory — structural regions reading correctly while the data area does not, which is the reverse of the usual pattern and which makes a complete list of expected files available before capture. The Atola Insight Forensic assessed error rates, imaging ran write-blocked under strict per-sector timeouts with retries capped, and losses were reported per named file against the captured directory.
The outcome
The directory captured first as an inventory, error rates measured and the drive imaged under capped timeouts with losses reported by name. 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: this is the reverse of most cases here. Filing structures are small and constantly written, so they normally break first — yours reading perfectly means those regions are healthy and the fault is distributed through the data area, which is a read problem rather than a bookkeeping one.
Drive that lists everything and copies nothing
Stop copying and stop scanning — both stall for the same reason and both cost you. Your readable directory is informative: filing structures are small and constantly rewritten, which is why they usually break first, so a complete listing means those regions are in good condition and the fault is distributed through the data area instead. That's a physical read problem rather than a bookkeeping one. The disconnections are the host giving up — a request issued and never answered holds a slot while the drive retries for seconds per sector, until the system removes the device. Recovery software inherits the same timeouts, so its failure says nothing about the software.
Stop copying — call Guildford Data Recovery on 01483 901310; directory captured first as an inventory, imaged under capped per-sector timeouts, losses reported per named file.
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.