Data Recovery Case File · Second Fixes & Trade Handoffs · Size of Files, Not Size of Drive
Many Small Files Depend on Structures Far More Than a Few Large Ones Do
This trade enquiry supplies the detail that shapes the whole job. A client drive that developed bad blocks before it stopped being recognised, holding "around 1.4 terabytes of data, mostly small files like documents and pictures." That last clause matters more than the capacity, because the difficulty of a recovery is set by how many separate objects there are and how much describing they require, not by how many bytes.
| Media | 2TB hard drive holding approximately 1.4TB predominantly in small files — bad blocks reported before the drive ceased to be recognised; no physical damage reported |
| Reported situation | Client drive failing · bad blocks identified by the referring party before failure · drive subsequently not recognised by their tools · no physical damage reported · approximately 1.4TB of content held · content described as predominantly small documents and images |
| Fault class | Progressive surface degradation reaching the point of non-presentation — large numbers of small files placing correspondingly heavy dependence on directory structures |
| Equipment used | File-size profile assessed as the determinant of structural dependence · drive addressed with imposed timeouts outside any host storage stack · imaged under strict per-sector timeouts with structure regions prioritised over content regions · directory records recovered with their duplicate copies before carving was considered · recovered set reconciled by count against the reported quantity |
The decode: why file size changes the recovery, and what the prior findings establish
Why a terabyte of large files is easier than a terabyte of small ones: the count differs enormously. The same capacity in video files might be a few hundred objects, and in documents and photographs it is hundreds of thousands.
Why the count is what matters: every object needs describing. Each file has a directory record, and hundreds of thousands of records occupy substantial structure that must itself be readable.
What follows when those structures are damaged: small files suffer disproportionately. A large file can be located by its own recognisable shape even without records; a small document frequently cannot.
Why that is the crux for this drive specifically: the fallback works poorly here. Carving recovers video and images tolerably and small office documents badly, because they are short, similar to one another and often not contiguous.
What that dictates about the capture: structures come first. The regions holding directory records are prioritised over content, because losing them costs far more than losing an equivalent area of file data.
Why fragmentation compounds it: small files scatter. A drive that has been filled and partly emptied over years places small files wherever space allowed, so a record is often the only thing that knows where a file continues.
Now what the referring party established, which is useful: bad blocks preceded the failure. That confirms progressive surface degradation rather than a sudden electronic fault.
Why progressive degradation is the more workable case: it is regional. A drive that declined gradually has failed in areas rather than everywhere, and the majority typically still reads.
Why it stopped being recognised at the end: degradation reached the reserved region. Once the drive cannot read its own configuration it cannot identify itself, regardless of the state of the recording.
What is worth agreeing in advance for a set this size: how completeness is measured. A count against the expected quantity is more meaningful than a byte total when the files are small.
On the bench
The file-size profile was assessed as the determinant of structural dependence — equivalent capacity comprising hundreds of objects in video or hundreds of thousands in documents and images, each requiring a directory record, so structural damage costs small files disproportionately. Carving recovers images tolerably and short office documents badly, being brief, similar and often non-contiguous. Structure regions were prioritised over content regions during imaging.
The outcome
The file-size profile assessed as determining structural dependence, structure regions prioritised during capture, and the set reconciled by count. 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: mostly small files is the important part of your description. The same capacity in documents is hundreds of thousands of objects, each needing a record — so the structures matter far more than usual.
Describing a drive for recovery
Say what kind of files, not just how much data — it changes the approach materially. A terabyte of video is a few hundred objects; a terabyte of documents and photographs is hundreds of thousands, each with its own directory record. That makes structural damage disproportionately costly, because a large file can be found by its own recognisable shape while a short document usually cannot. Agree in advance that completeness will be measured by file count rather than by bytes.
Say so up front — call Cambridge Data Recovery on 01223 655015; file-size profile assessed as determining structural dependence, structure regions captured first, results reconciled by count.
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.