Data Recovery Case File · Desktop Externals & Aging Drives · A Drive That Won't State Its Size

Disk Shows as Unknown With No Capacity

His enquiry contained a detail that most people would not think to mention and that decides the diagnosis. A Transcend 1TB external drive holding around 100GB: "showing as unknown, uninitialised, and has no capacity details. When first plugged in, the drive prompts for initialisation." The words unknown and uninitialised appear constantly in these enquiries and usually mean partition damage — a recoverable, ordinary fault. But "no capacity details" is different, and it is the more informative of the three. A drive reports its own size during identification, before any partition or filesystem is involved. If the host cannot display a capacity, the drive is not reporting one — and that points below the filesystem entirely, to the drive's own firmware.

The decode: capacity versus unallocated, and why the distinction matters

What happens before any partition is read: when a drive is connected, it identifies itself — reporting its model, serial and, critically, its capacity. That exchange happens at a level far below partitions and filesystems, and it depends on the drive successfully reading its own internal management data. Only after it has stated a size does the host look for partition structures on it.

Why "no capacity" is not the same as "unallocated": the distinction worth carrying. A drive showing its correct size but reporting the space as unallocated has identified itself perfectly and simply has damaged partition structures — an ordinary, highly recoverable logical fault. A drive showing no size at all, or an obviously wrong one such as zero, has failed at the earlier stage: it is not reporting its geometry, which means it could not read the internal data that tells it what it is. That is a firmware or service-area problem, not a filesystem one, and no partition tool or recovery program can address it — because there is nothing yet for them to scan.

Why the drive still appears at all: because the enclosure's bridge board is working and announcing a device, and because the drive responds enough to be present without completing a proper identification. That is why his computer offers to initialise it: faced with a device it cannot characterise, the operating system proposes writing a fresh structure onto it.

Why that prompt is the danger: accepting initialisation writes new partition structures onto a drive whose real ones are still there — and on a drive that is not correctly reporting its geometry, a write can land in the wrong place entirely. It is the single most damaging thing available on his screen, and he was right to decline it. So was leaving the drive alone rather than running scanning software, which on a drive with no reported capacity has nothing to work with anyway.

Why it is recoverable: service-area faults are addressed through the manufacturer's own technological modes — the reserved region read directly and its damaged modules repaired or regenerated until the drive identifies itself properly and reports its true capacity. At that point the partitions and filesystem are usually found intact, because nothing about this fault touched them. His 100GB is very likely sitting exactly where he left it.

On the bench

The Atola Insight Forensic established what the drive was actually reporting during identification — whether it was failing to answer, answering incorrectly, or not completing the exchange — which separates a geometry fault from partition damage without writing anything. Access followed through the PC-3000 Express in the drive's technological modes: the service area read directly and its damaged modules repaired until the drive identified itself correctly and reported its true capacity. Imaging then ran under Data Extractor, and with the geometry restored the original partition structures were found and the volume rebuilt from the image. His files were verified by opening and delivered on fresh media.

The outcome

The service area repaired, correct identification restored, and the volume rebuilt from the image and verified. 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 seeing an unknown disk: read the capacity field, because it separates two very different faults — a drive showing its correct size with unallocated space has identified itself properly and has partition damage, which is ordinary and recoverable, while a drive showing no size has failed to report its own geometry, which is a firmware or service-area fault below the filesystem entirely; recovery software cannot help with the second, because there is nothing yet to scan; and the initialisation prompt is the one thing on your screen that can make it permanently worse.

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.