Data Recovery Case File · Portable Drives · Position Matters
How Empty the Drive Is Changes the Odds
His enquiry mentioned a figure almost in passing that turns out to be one of the more useful things anybody reports. A 1TB external drive "with around 10GB of data on it. The drive takes ages to load and I can see the files but can't open or copy them." The symptoms are familiar — a struggling mechanism, structures readable through retries, content that will not follow. But the ratio changes the picture. Ten gigabytes on a terabyte drive means ninety-nine per cent of that surface has never held anything, and the odds improve considerably once you know where the data actually sits.
| Media | 1TB external hard drive holding approximately 10GB — extended delay before listing appears; files visible and failing to open or copy |
| Reported situation | Drive taking a long time to become available · file listing appearing · files failing to open or copy · approximately 10GB of content on a 1TB device |
| Fault class | Read failure with content concentrated in a small leading region — occupied extent identifiable and imaging scopeable to it |
| Equipment used | No repeated access attempts · occupied extent established from filesystem allocation before imaging · imaging scoped to occupied regions under per-sector timeouts (PC-3000 Express with Data Extractor) · files validated by opening |
The decode: where 10GB actually lives, and why that helps
Where a filesystem puts things: not scattered evenly. Filesystems allocate from the beginning of the available space outward, so a drive that has only ever held ten gigabytes has all of it concentrated in a region at the very start of the disk — along with the structures describing it. The remaining terabyte has never been written to at all. It is not empty in the sense of having been cleared; it has simply never held data.
Why that improves his position materially: a failing drive does not fail uniformly. Damage is usually localised — particular tracks, a particular head's surface, a region where contact occurred. If the occupied region is a small band at the start and the damage lies elsewhere, the material may read perfectly once the drive is handled properly. And even where the occupied region is affected, imaging can be scoped to it rather than sweeping the whole disk.
Why scoping matters on a failing mechanism, and this is the practical part: imaging a full terabyte from a struggling drive means hours of continuous work, and every hour is more wear on a mechanism that is already marginal. Imaging ten gigabytes plus the structures around it is a fraction of that — faster, and far less load applied to a drive that may not have many hours left in it. On a marginal mechanism the difference between a targeted image and a full sweep can be the difference between getting everything and running out of drive partway.
Why the delay before listing is still meaningful: it is not slowness. Presenting a volume requires reading a small amount from specific places, which takes under a second on a healthy drive. An extended wait means those reads are failing and being retried until enough is gathered — so the drive is struggling, and the length of the wait measures how much.
Why the files then will not open: the structures are small and concentrated enough to scrape together with retries; the files themselves are much larger and cannot be assembled the same way. That is why a drive can list what it cannot deliver, which looks contradictory and is not.
The thing worth mentioning that nobody does: how full the drive is. It is a fact every owner knows and almost none report, and it changes both the approach and the expectation.
On the bench
No repeated access attempts were made, since each one is a struggling mechanism retrying at full budget for no data. The occupied extent was established from filesystem allocation before imaging — determining exactly which regions had ever held data, since a drive holding ten gigabytes of a terabyte has all of it concentrated near the start and the remainder has never been written. Imaging was then scoped to the occupied regions under per-sector timeouts on the PC-3000 Express with Data Extractor, applying a fraction of the load a full sweep would demand. Files were validated by opening.
The outcome
The occupied extent established first, imaging scoped to it under timeout control and every file validated by opening. 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, for anyone with a nearly empty drive that has failed: say how full it is, because it changes the odds. Filesystems allocate from the start outward, so ten gigabytes on a terabyte drive sits concentrated in a small leading region while the rest has never held anything — which means the damage may be nowhere near your data, and imaging can be scoped to a fraction of the surface rather than sweeping the whole disk on a mechanism that may not last.
Failing drive that's mostly empty
Mention how much data is actually on it — everyone knows this and almost nobody thinks to say it, and it changes both the approach and the odds. Filesystems allocate space from the beginning of a drive outward, so if you've only ever stored ten gigabytes on a terabyte drive, all of it sits concentrated in a small region near the start and the rest has never held anything at all. That matters twice over. Failing drives usually fail in particular places rather than uniformly, so the damage may be nowhere near your data. And imaging can be scoped to the occupied region instead of sweeping the whole surface, which on a struggling mechanism is the difference between hours of load and a fraction of it. Meanwhile stop retrying — the long wait before it appears is the drive failing reads and retrying them.
Say how full it is — call Newcastle Data Recovery on 0191 406 1051; occupied extent established before imaging, work scoped to the regions that hold data, every file checked by opening.
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.