Data Recovery Case File · Trust, Practice & Honest Limits · A Smaller Job That Exists
The List Survives Separately From the Things It Lists
His enquiry asks for something nobody thinks to ask for and it is entirely achievable. A drive he believed held a music collection backed up years ago, where the music is now missing: "I'd be happy if I can only get the file names back that used to be on there." Filenames live in directory records, and those are separate from the content they describe — so recovering the list without the files is a real, smaller and much more likely job.
| Media | External hard drive holding a music collection backed up several years previously — content not present; directory records sought independently of file content |
| Reported situation | Drive believed to hold a music collection copied several years previously · content found absent on recent inspection · corruption suspected · owner requesting recovery of filenames only rather than file content |
| Fault class | Content absent or unrecoverable with directory structures potentially intact — metadata recovery viable independently of content recovery |
| Equipment used | Scope confined to directory records as requested · occupied capacity reconciled against listed entries to establish whether content is present · imaged write-blocked before any reconstruction · directory entries recovered from surviving structures · listing delivered as the agreed output |
The decode: why the list is a separate thing
How a filesystem is arranged: in two parts. Directory records hold names, dates, sizes and pointers, and they occupy a small defined region. The content sits elsewhere, occupying the great majority of the medium.
Why that separation is useful here: the two fail independently. Content can be overwritten, corrupted or never have arrived while the records describing it remain perfectly readable — which is why a drive can list files it cannot open, a situation this archive meets constantly.
So what he is asking for is the more survivable half: records are small, and small structures are less exposed than the large regions holding content. They also frequently exist in more than one place, because filesystems maintain backup copies of their key structures.
Why the request is sensible rather than a consolation: for a music collection, the names are most of the value. A list of several thousand titles is a list of things that can be re-acquired — the recordings themselves are commercially available, and what cannot be reconstructed from memory is which of them he had.
Why that reasoning generalises further than music: a list of what was there is useful for insurance, for reconstructing a photograph collection from other sources, for knowing which documents to request again, and simply for knowing what was lost. People assume recovery is all-or-nothing and it is not.
Why it is a smaller job: the work is confined to a small region rather than the whole medium, no content has to be read, no fragmentation has to be resolved, and nothing needs validating by opening. It is faster, cheaper and far more likely to succeed.
What is worth checking first, and it may change the picture entirely: whether the content is genuinely absent. Comparing the occupied capacity against what is listed settles it — space consumed with nothing visible means the content is present and undescribed, which is the opposite situation and a fully recoverable one.
The general point worth taking: ask for what would actually help. A recovery scoped to less is a recovery more likely to deliver, and nobody suggests it because nobody is asked.
On the bench
Scope was confined to directory records as requested — filesystems separating directory records holding names, dates and sizes from the content they describe, so the two fail independently and small structures held in duplicate survive more readily than the large regions holding content. Occupied capacity was reconciled against listed entries to establish whether content was genuinely absent, consumed space with nothing visible indicating the opposite and fully recoverable situation.
The outcome
Scope confined to directory records, occupied capacity reconciled against entries, and a listing delivered as agreed. 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: filenames live in directory records, separately from the content they describe, and small structures held in duplicate survive far more readily. Asking for the list alone is a real job and a much likelier one.
When a list of what was there would be enough
Ask for it — recovering filenames without file content is a real and much smaller job, and nobody offers it because nobody requests it. Directory records hold names, dates and sizes in a small region, separate from the content they describe, so the two fail independently and the records are held in duplicate by most filesystems. That makes them considerably more survivable. A list is genuinely useful too: for music or anything re-acquirable, knowing what you had is most of the value; and elsewhere it serves insurance, reconstruction from other sources, or simply knowing what was lost. Check occupied capacity first, though — space in use with nothing listed means the opposite problem.
Ask for exactly that — call Oxford Data Recovery on 01865 593000; scope confined to directory records, occupied capacity reconciled against entries first, listing delivered as the agreed output.
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.