No Media, Zero Bytes, No Partitions

The decode

"No media" with zero bytes is a precise symptom that names the controller. The drive appearing in Disk Management at all means it enumerates — it announces itself to the USB bus. But "no media, 0 bytes, no partitions" means that having announced itself, it cannot expose any actual storage. That gap — present on the bus, but presenting no memory — is the signature of a controller fault: the controller is alive enough to be listed but not enough to make the memory behind it available.

This is exactly why chkdsk and recovery software fail, and it is not a dead end. Both chkdsk and recovery software need the drive to expose its storage before they can do anything — chkdsk checks a filesystem, recovery software scans a volume, and here there is no accessible volume to check or scan. Their inability to see the drive is not evidence the data is gone; it is a direct consequence of the controller not exposing the memory. The fault is below the level any software can operate.

The data is very likely intact in the memory behind the controller. A controller fault stops the memory being presented, but it does not erase the NAND where the files live. The data sits in memory the failed controller can no longer expose — and reaching it means restoring the controller's function on professional equipment, or reading the memory directly. As with any controller fault, the problem is access, not existence, which keeps recovery realistic.

The route runs from controller access to chip-off. The drive is first addressed on professional flash equipment that can talk to the controller in its service modes — reaching the memory the controller is failing to present, and reading it through the controller where it part-responds. This is the less invasive route. Where the controller is genuinely dead and cannot be revived, chip-off follows: removing the memory chip to read it directly, bypassing the failed controller entirely.

The honest prognosis is cautiously good, given the fault. A controller fault with intact memory — which the "no media" symptom strongly indicates — typically returns the data, through controller access or chip-off. The genuine unknown is whether the memory itself was damaged, which is established from the read, with the recoverable extent confirmed at assessment before any charge. A drive that shows as empty everywhere is a frustrating symptom, but it is a recoverable one.

On the bench

The drive was inspected under stereo microscope for physical and contact damage, then addressed on PC-3000 Flash. The controller was accessed in its service modes to expose the memory it was failing to present, the NAND read through it where it part-responded, with chip-off reading where the controller was dead, the raw dump reconstructed in specialist flash software. The recovered files were validated by rendering.

The outcome

Controller accessed to expose the memory, or the NAND read directly by chip-off where it could not be, and the files reconstructed and validated. The diagnostic costs nothing and completes within two working days of arrival, and the quote is one fixed written figure with VAT already in it; if the data can't be brought back, no charge is made. The decode: "no media, zero bytes" is a controller that enumerates but can't expose its memory — which is why chkdsk and software see nothing. Your data is very likely intact in the memory behind it, reachable through controller access or chip-off.

Our case files are written up from genuine enquiries our lab has handled for customers across Swansea and South Wales, anonymised to protect client confidentiality. Each one describes the diagnostic and recovery approach our engineers apply to that fault, using the equipment listed.