Data Recovery Case File · Portable Drives · Scoped Before Anybody Asked
He Said What He Needed and What He Did Not
His enquiry does in four lines what most never do at all. A 2TB drive that will not mount, where "I'm told by IT colleagues that the files are readable. The files are mostly documents and photographic images, of which there are about 15,000. There are a few video files but these are much less important. I do not need to recover all" of it. A count, a set of types, and an explicit statement of what can be left behind — which turns an open-ended job into one with an end.
| Media | 2TB portable external hard drive — not mounting on the host; contents reported as readable by a third party; approximately 15,000 images and document files required, video content deprioritised |
| Reported situation | Drive not mounting on the owner's machine · colleagues reporting the content as readable · approximately 15,000 photographic images held · document files held · a small quantity of video held and described as less important · complete recovery not required |
| Fault class | Volume not mounting with content readable — structural fault with the medium responding; scope defined by the owner in advance |
| Equipment used | Third-party readability finding accepted as evidence of a structural rather than device fault · capture sequenced to prioritised file types · imaged write-blocked before any reconstruction · structures rebuilt from surviving copies · completion verified against the stated count and types |
The decode: what readable-but-not-mounting means, and what the scope buys
What his colleagues established: that the content is there and can be read. That separates two situations which look identical from the outside — a drive whose medium is failing, and a drive whose medium is fine while the description of its contents is damaged. Theirs is the second, which is the more recoverable of the two by a considerable margin.
Why a volume can fail to mount while its contents read perfectly: mounting requires the system to interpret the filesystem structures and accept them as consistent. Those structures occupy a small defined region, and damage confined to them leaves every file physically intact and correctly located while the system declines to present any of it.
Why the scope changes the work rather than just the price: capture can be sequenced. Reaching the images and documents first means confirmation arrives early — he knows the important material survived before the rest is touched, rather than at the end of a full reconstruction.
Why the count is the most useful number in the enquiry: fifteen thousand images is something to check against. A recovery that returns fourteen thousand has a gap that can be named, and one that returns fifteen thousand is demonstrably complete. Without a figure, the only report available is a quantity of data, which tells nobody whether anything is missing.
Why saying what does not matter is worth as much as saying what does: the video is deprioritised, which means effort and, if the drive proves difficult, remaining margin are not spent on it. Most enquiries ask for everything because nobody has suggested the alternative, and everything cannot be prioritised.
Why file type matters practically here: images and documents are small and generally written contiguously, so they reconstruct cleanly. Video is large and frequently fragmented, which makes it the harder material — so his priorities happen to align with what is straightforward, which is fortunate rather than planned.
What must not happen meanwhile: no repair, and no acceptance of any prompt to initialise or format. The structures his colleagues could read around are exactly what those operations replace.
On the bench
The third-party readability finding was accepted as evidence of a structural rather than device fault — content reading while a volume declines to mount indicating damage confined to filesystem structures, which occupy a small defined region while files remain physically intact and correctly located. Capture was sequenced to prioritised file types so confirmation arrived early, and completion verified against the stated count and types rather than reported as a quantity of data.
The outcome
The readability finding accepted, capture sequenced to the owner's priorities and completion verified against his own 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: readable but not mounting is the good version — the structures describing your files are damaged while the files themselves are intact. And your count is the most useful thing in the message, because it makes the result checkable.
Making a recovery request that can be confirmed
Say how many, what types, and what you can do without — those three things turn an open-ended job into one with an end. A count is the most useful figure you can supply, because it's something to check the result against: a recovery that returns fourteen thousand of fifteen thousand images has a gap that can be named, where a report of so many gigabytes tells you nothing about whether anything is missing. Naming what doesn't matter is worth as much, since it means effort and any remaining margin aren't spent there. And if someone has already established your files are readable, say so — that distinguishes a structural fault from a failing medium.
Bring your count and priorities — call Oxford Data Recovery on 01865 593000; capture sequenced to your priorities, structures rebuilt from surviving copies, completion verified against your own figures.
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.