Data Recovery Case File · Desktop Externals & Aging Drives · Capacity Is Reported, Not Measured
A Drive That Cannot Read Its Own Configuration Cannot Say How Large It Is
His enquiry contains a number that locates the fault precisely. A damaged disk, where he would be content with the photographs alone, that "is detectable sometimes in the command prompt, but it will only show 0 bytes on it." A drive's capacity is not measured from its platters — it is read from the drive's own firmware and reported. Zero means it enumerated, was asked how large it is, and could not answer.
| Media | Hard drive enumerating intermittently and reporting zero capacity — service area or firmware read failure indicated; user data region unaffected |
| Reported situation | Drive reported as unusable · detected intermittently at the command line · capacity reported as zero when detected · photographic content sought as a scoped priority |
| Fault class | Firmware or service area read failure — capacity reported from the drive's own configuration, which it cannot read; user data region separate and intact |
| Equipment used | Zero capacity interpreted as a self-description failure rather than an empty medium · service area addressed in the drive's technological modes · firmware modules assessed and repaired · addressing restored before imaging · imaging under strict per-sector timeouts |
The decode: where a capacity figure actually comes from
What people assume the figure means: that the computer looked at the drive and found nothing on it. A drive reporting zero reads as an empty drive, which is alarming and is not what has happened.
Where the number really comes from: the drive's own firmware. Every drive holds its model, serial number, capacity and calibration data in a reserved region — the service area — which is on the platters but outside the space anybody's files occupy. When a host asks how large a drive is, the drive reads that region and answers.
So what zero establishes: the drive powered up, spun, connected, and entered the exchange in which it identifies itself — and then failed to supply a capacity, because it could not read its own configuration.
Why that is genuinely hopeful: the service area is a small reserved region and it is not where his photographs are. The fault is in the drive's ability to describe itself, and the user data region is entirely separate — untouched by whatever has gone wrong.
Why the drive will not present its contents regardless: a host that has been told a drive is zero bytes will not attempt to read from it. The addressing has to be restored before anything else is possible, which is why software cannot help at all here.
What the intermittent detection adds: the drive sometimes gets far enough to be seen and sometimes does not. Each successful enumeration is one of an unknown number, and repeated attempts to check spend them.
What the route is: the service area is addressed in the drive's own technological modes — a maintenance interface separate from ordinary reading — where damaged firmware modules are assessed and repaired. Once the drive can read its configuration, it reports its capacity and behaves normally, and imaging proceeds.
Why his scoping helps: asking for the photographs alone means capture can be sequenced to reach them first, which matters on a drive whose reliable operating time is unknown.
What must stop: repeated connection to see whether it appears today. It may, and that appearance is worth more spent on capture.
On the bench
Zero capacity was interpreted as a self-description failure rather than an empty medium — a drive holding its model, serial, capacity and calibration in a reserved service area outside the user data region, and reporting capacity by reading it, so a zero figure indicates successful enumeration followed by failure to read its own configuration. The service area was addressed in the drive's technological modes, firmware modules assessed and repaired, and addressing restored before imaging.
The outcome
The zero figure read as a self-description failure, the service area addressed in technological modes, and addressing restored before imaging. Free assessment, one fixed written figure including VAT, 50% of parts and labour upfront with the balance only on successful recovery. The decode: capacity is reported from the drive's own firmware rather than measured from the platters. Zero means it powered up, identified itself, and could not read its own configuration — which is a small reserved region, and not where your photographs are.
Drive reporting a capacity of zero
Stop reconnecting it to see whether it appears today — each successful detection is one of an unknown number and is worth more spent on capture. And don't read zero bytes as an empty drive. Capacity isn't measured from the platters; it's read from the drive's own firmware, held in a reserved region outside the space your files occupy, and reported when a host asks. So zero means the drive powered up, spun, identified itself, and then couldn't read its own configuration. That places the fault in a small reserved area rather than where your photographs are — which is why software can't help until the addressing is restored.
Stop reconnecting it — call Oxford Data Recovery on 01865 593000; the figure read as a self-description failure, service area addressed in technological modes, addressing restored before imaging.
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.