Data Recovery Case File · Desktop Externals & Aging Drives · A Sequence of Giving Up
No Capacity Reported Means the Drive Was Asked and Did Not Answer
Her enquiry sets out a sequence rather than a symptom. A drive where "the computer recognises that something is plugged in, but does not give me any information such as the capacity", which crashes the file browser on opening, and — if left alone — "will eventually ask to format the disk." Each of those is the system giving up at a later stage, and the first one is the most precise finding in the enquiry.
| Media | External hard drive — detected on connection without capacity reported; host file browser destabilised on access; formatting prompted after a delay |
| Reported situation | External drive connected · host detecting a device · no capacity or usage information presented · file browser crashing when the drive is opened · formatting prompted if the drive is left connected without being opened · behaviour reproduced on several computers · content required |
| Fault class | Enumeration completing without capacity or volume information — device responding at identification and failing on subsequent queries; formatting prompt following timeout |
| Equipment used | Absent capacity reporting interpreted as identification succeeding and subsequent queries failing · repeated host connection stopped · current draw measured across the start-up cycle on a controlled bench supply · service area and capacity descriptors read under strict timeouts · imaging under capped timeouts with volume regions revisited across passes |
The decode: three observations in order, and what each one adds
What being detected establishes: the device answered its introduction. Power arrived, the drive responded, and the host accepted it as present — so the connection and the most basic exchange both work.
What no capacity reported adds, and it is the sharpest of the three: the next question failed. Having accepted the device, the system asks how large it is, and a drive that cannot answer has failed to read its own configuration — which is stored on the platters in a reserved area.
Why that is a narrow and useful finding: it brackets the failure between identification and configuration. Everything before works and the reserved area cannot be read, which is a small region and says nothing about where her content sits.
What the crash on opening adds: the system attempted to go further anyway and the device stopped responding mid-request. A file browser waiting indefinitely on an unanswered request can take the interface down with it — the crash is the host's reaction rather than the drive's.
What the delayed format prompt adds: the last stage of giving up. Having failed to obtain capacity and failed to read a volume, the system concludes the drive is unprepared and offers the only remedy it has.
Why that prompt is the dangerous one: it appears after a wait, when nothing else has worked and accepting feels like progress. Preparing the disk writes new structures over the region a reconstruction needs, and it would not fix the underlying fault in any case.
Why testing on several machines was worth doing: the same sequence everywhere places the behaviour in the drive. She has removed the computer, the port and the operating system — and further testing adds nothing.
Why a drive can fail this way while remaining largely intact: the configuration area is separate from the user data area. A drive unable to read its reserved region never reaches the point of offering content, though the content itself is untouched by that failure.
Why some of these are addressed without opening the drive: the reserved area is reachable in the drive's own diagnostic modes over its interface. Where the fault lies there, no donor parts and no entry into the sealed assembly are required.
What must not happen: no accepting the format prompt on any machine, and no leaving the drive connected waiting to see what it offers. Each wait ends in the same suggestion.
On the bench
Absent capacity reporting was interpreted as identification succeeding and subsequent queries failing — detection establishing that the device answered its introduction, after which the host asks its size, an answer derived from configuration held in a reserved area of the platters, so failure there brackets the fault between identification and configuration. Browser destabilisation reflects an unanswered request rather than drive behaviour, and the delayed format prompt is the host's final conclusion. Service area and capacity descriptors were read under strict timeouts.
The outcome
Absent capacity reporting read as identification succeeding and configuration failing, repeated connection stopped, and the reserved area read under strict timeouts. 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: the missing capacity is the finding. Your drive answered its introduction and could not answer how large it is — which means it failed to read its own configuration, in an area separate from your files.
A drive detected without its capacity showing
Refuse the format prompt on every machine, and don't leave the drive connected waiting to see what it offers — every wait ends in the same suggestion, and it arrives when nothing else has worked and accepting feels like progress. Read the three symptoms in order: being detected means the device answered its introduction; no capacity reported means it then failed to read its own configuration, held in a reserved area of the platters; and the crash on opening is your computer waiting on a request that was never answered. That reserved area is separate from where your files sit.
Refuse the format prompt — call Manchester Data Recovery on 0161 871 0788; absent capacity read as configuration failure, draw measured across the start-up cycle, reserved area read under strict timeouts.
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.