Call us — 0161 871 0788
Mon–Fri · 9am–5:30pm · No fix, no fee
Start a free diagnostic →

Data Recovery Case File · Solid State & Flash · Identity Without Capacity

A Controller That Names Itself and Reports No Media Has Lost Its Own Map

His enquiry contains a diagnostic most people never reach. A stick reported as having "no media" in volume management, invisible to two recovery packages, but where a chip identification tool "is able to detect the USB and gives me the serial number." Those two facts together are precise: the controller is alive enough to introduce itself, and cannot tell the system how much storage it has.

Media32GB USB flash drive — reported as having no media by volume management; controller responding to identification with descriptors returned
Reported situationFlash drive not accessible · volume management reporting no media present · two recovery packages unable to see the device · chip identification utility detecting the device and returning identifying information · owner seeking assistance
Fault classController enumerating without reporting capacity — translation layer or capacity descriptor lost; memory not implicated by the point of failure
Equipment usedIdentification without capacity interpreted as translation layer loss rather than absent memory · device addressed through hardware with imposed timeouts rather than the host stack · controller state assessed in vendor technological modes · memory read past the controller with translation layer reconstructed in software · recovered content validated by opening

The decode: what each observation establishes, and why they fit together

What the identification tool proves: the controller is running. It powered, executed its program, and answered a request for its identity with its manufacturer, model and serial number — none of which a dead device manages.

Why that eliminates a great deal: the connection works, the power path works, and the controller's basic function works. Everything up to and including introducing itself succeeded.

What no media specifically reports: the system asked how much storage is available and was told none. It is the same answer a card reader with no card inserted gives — the device is present and reports having nothing to offer.

Why that combination is so informative: the controller can describe itself and cannot describe its storage. Those are separate pieces of information, and only the second has been lost.

What that points at: the tables recording how content is distributed across the memory. A controller reads them during start-up and derives its usable capacity from them — so a controller that cannot read them has no capacity to report and says so.

Why the recovery packages found nothing: they work through the operating system, which was told there is no media. Software cannot scan storage the system does not believe exists, so their result reflects the report rather than the memory.

Why the memory is very likely intact: the failure is in the map, not the territory. Content written to the memory remains there regardless of whether the controller can still describe where it put things.

What is done about it: the memory is read directly, bypassing the controller's inability to report capacity, and the distribution scheme reconstructed from the data itself. Working out how the original controller must have arranged things is exactly what replaces the lost tables.

Why his identification of the controller is genuinely useful: the manufacturer and model narrow how content was likely arranged. Different controller families use different schemes, and knowing which one shortens the reconstruction.

What must not happen: no controller reprogramming or mass-production utilities, which are widely suggested for exactly this symptom. Those rewrite the tables rather than recover them, and a device restored to working order that way comes back empty.

On the bench

Identification without capacity was interpreted as translation layer loss rather than absent memory — a controller answering an identity request with manufacturer, model and serial number establishing power, execution and basic function, while a no-media report indicates the device stating it has no available storage. Capacity is derived from the tables recording content distribution, read during start-up, so a controller unable to read them reports none. Memory was read past the controller with the translation layer reconstructed in software.

The outcome

Identification without capacity read as translation layer loss, the device addressed through hardware, and the memory read past the controller. Free assessment, one fixed written figure including VAT; where a chip has to be removed, 50% of parts and labour is payable upfront with the balance only on success — otherwise no recovery, no fee. The decode: your two observations fit together precisely. The controller can describe itself and cannot describe its storage — which points at the tables recording where content sits, not at the memory holding it.

A device reporting no media that a chip tool can still identify

Don't run any controller reprogramming or mass-production utility — those are widely suggested for this exact symptom, and they rewrite the tables rather than recover them, so a device restored to working order that way comes back empty. Your two observations are a precise diagnosis: the controller answering an identity request proves it powers and runs, while a no-media report means it told the system it has no available storage. Capacity comes from the tables recording where content sits, so it has lost the map rather than the memory. Recovery software can't help, since the system believes there's nothing there.

Device identified by a chip tool but reporting no media?
Don't reprogram the controller — call Manchester Data Recovery on 0161 871 0788; identification without capacity read as translation layer loss, addressed through hardware, memory read past the controller.
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.