Data Recovery Case File · Desktop Externals & Aging Drives · Know What You Already Hold
The Rescued Material Is a Baseline and Almost Nobody Writes It Down
Her enquiry describes a partial success followed by a complete failure. A drive dropped onto a hard floor, from which she "managed to get quite a lot off before it died, but not all, and there are still a lot of work files on there that I need. It's starting up and shows up in the disk utility, but I can't mount it." What she already has determines what still has to be recovered — and listing it turns an open-ended job into a target.
| Media | External hard drive following impact — substantial content copied off before failure; device enumerating; volume not mounting |
| Reported situation | Drive dropped onto a hard surface · substantial content copied off subsequently · drive failing during or after that process · device appearing in the host disk utility · volume not mounting · remaining work files required |
| Fault class | Impact damage with progressive degradation under copy load — device enumerating while structures fail to read; scope reducible against material already rescued |
| Equipment used | Rescued material listed and reconciled against requirements before any work · scope confined to the outstanding gap · laminar flow bench inspection before any spin attempt · imaging sequenced to the identified gap first · losses mapped per file |
The decode: the step before the technical one
What almost nobody does after a partial rescue: writes down what came off. The material sits in a folder somewhere and the enquiry that follows asks for everything, because nobody has separated what is safe from what is missing.
Why that costs something real: a recovery aimed at everything spends effort — and, on a damaged drive, limited reading opportunities — on files she already has. Every minute reading something safely stored elsewhere is a minute not spent on the gap.
How to produce the list without much effort: most systems will write a folder tree to a text file. That listing, set against what she knows was on the drive, produces a target — and for work files, the folders she cannot account for are usually obvious once written out.
Why scoping matters more here than on a healthy drive: this one is damaged and its remaining reading is finite. Capture sequenced to reach the missing material first means the important part is confirmed early, rather than at the end of a full traversal that may not complete.
What her symptoms indicate now: the device appears and the volume will not mount. So the electronics work and the region holding the filesystem structures is not reading — which on a drive that has been dropped is consistent with head damage affecting particular areas.
Why the copying is likely to have contributed: a drop can damage a head without stopping the drive, and copying is sustained reading across the whole surface. The rescue and the deterioration were the same process — she was reading the drive with a damaged head, which is how it went from working to not.
Why that is not a reason for regret: without the copying she would have nothing. The material she has is real and was worth having, and the alternative was a drive that failed later with none of it saved.
What must stop now: further connection and further copying attempts. The remaining reads are limited and should happen under controlled conditions, sequenced to what she actually needs.
On the bench
Rescued material was listed and reconciled against requirements before any work — a partial rescue establishing a baseline that reduces the outstanding scope, where an unscoped recovery spends limited reading opportunities on content already held. Scope was confined to the outstanding gap and imaging sequenced to it first, so the required material is confirmed early rather than at the end of a traversal that may not complete. Inspection ran under the laminar flow bench.
The outcome
The rescued material listed and reconciled first, scope confined to the gap, and imaging sequenced to reach it early. Free assessment, one fixed written figure including VAT, 50% of parts and labour upfront with the balance only on successful recovery. The decode: write down what you already have. A damaged drive has limited reading left, and a recovery aimed at everything spends it on files that are already safe — listing the rescue turns this into a target rather than an open request.
After getting some files off a failing drive
List what came off before commissioning anything — most systems will write a folder tree to a text file, and setting that against what you know was there produces a target. It matters more than it sounds: a damaged drive has a limited amount of reading left in it, and a recovery aimed at everything spends that on files already sitting safely in a folder. Scoped to the gap, capture can reach what you actually need first and confirm it early. And don't regret the copying, even if it contributed — without it you'd have nothing, and the alternative was failing later with none of it saved.
List what you have — then call Oxford Data Recovery on 01865 593000; rescued material reconciled against requirements first, scope confined to the gap, imaging sequenced to reach it early.
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.