Data Recovery Case File · Solid State & Flash · Present, and Reporting Nothing
USB Not Recognised: Please Insert a Disk
Her enquiry described a message that sounds like a joke at the owner's expense. An old USB stick "coming up as 'lost partition' and telling me to 'insert disk'" — while inserted. It holds childhood photographs, and she would like them recovered and moved onto a newer stick. The message is not a glitch and it is not the computer being obtuse. It is a precise report of an unusual state: the stick has introduced itself successfully and then declared that it contains no media. That combination is specific, it is informative, and it sits somewhere better than the sticks elsewhere in this archive that produce no response at all — because something inside is still answering.
| Media | Older USB flash drive holding family photographs — enumerates to the host but reports no media present; scanning tools report a lost partition; contents required on replacement media |
| Reported situation | Stick recognised as a device but prompting for a disk to be inserted · scan tools reporting no readable partition · childhood photographs held without other copies |
| Fault class | Controller responding at device level but unable to address its memory — partial controller failure; chip-level access typically required |
| Equipment used | Write-blocked access attempt behind DeepSpar USB Stabilizer 10Gb · PC-3000 Flash with Spider Board chip-level read where the controller cannot address its memory · Rusolut VNR pinout, XOR and ECC reconstruction · photographs validated by rendering and delivered on new media |
The decode: what the message reports, and what it leaves
Why a computer asks for a disk that is present: the message dates from removable media — floppy drives and card readers, where the reader and the disk were separate things, and the reader could be connected while empty. Modern systems still use the same logic. A USB stick presents itself to the computer as a storage device, and the computer then asks that device how much media it contains and how large it is. If the device answers zero — no media, no capacity — the system reports exactly what it has been told: there is a reader here, please insert a disk.
What that means about the stick: two things, and the combination is the diagnosis. The controller is alive enough to conduct the introduction — it powered up, identified itself, and negotiated with the operating system, which is more than a completely dead controller manages. But it cannot address its own memory, so when asked what it holds, it has nothing to report. That is a partial controller failure: the front half working, the half that talks to the NAND not. It also explains the second message, since a scanning tool asked to examine a device reporting zero capacity finds no partition to read.
Why that is a workable position: the memory itself is almost certainly untouched. Her photographs are written in the NAND, and the reason they cannot be reached is that the chip responsible for fetching them has partly failed. The route goes around it: the memory is read directly through the device's own internal contacts, bypassing the controller entirely, and the raw data is then descrambled, error-corrected and reassembled in software until a filesystem stands up. That is routine work with good odds, and a stick reporting zero capacity is a better starting point than one producing no response at all.
What to avoid meanwhile: the message invites two responses, and both are wrong. Windows will offer to format a device it considers empty — decline it every time, because on the rare occasion the controller partially recovers, formatting would write over the structures describing her photographs. And repeated reinsertion adds nothing: the answer will be the same, and each attempt powers a failing controller for no return.
Her actual request, answered: she asked for the files moved onto a newer stick, which is exactly right and is standard practice — recovered data never goes back to the device it came from. One honest note to go with it: a memory stick is the least durable storage most people own, and childhood photographs deserve better than a single copy on one. Onto a new stick by all means, and also somewhere that is backed up.
On the bench
Access was attempted first behind the DeepSpar USB Stabilizer 10Gb, write-blocked — a controller that can be coaxed into addressing its memory changes the route entirely and makes everything below unnecessary, so it is always tested. It could not. The chip-level road followed: the memory read directly on the PC-3000 Flash Spider Board with the pinout confirmed against the Rusolut VNR database, bypassing the controller rather than persuading it. Reconstruction ran the full pipeline — XOR descrambling, ECC correction and translation rebuild — until the filesystem stood back up, and her photographs were validated by rendering rather than counted before delivery on new media.
The outcome
The memory read at chip level past a partially failed controller, the photographs validated and delivered on new media. 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, for anyone whose computer asks for a disk that is already in: the message is inherited from removable media and it means your device introduced itself and then reported zero capacity — so the controller is alive enough to talk but cannot address its own memory; that is a partial failure and a better position than total silence, because the memory holding your photographs is untouched behind it; and decline the format offer that follows, since it is aimed at a device the system believes is empty.
Computer asking you to insert a disk that is already inserted
The message makes more sense than it looks: your stick introduced itself to the computer successfully and then reported that it contains no media, so the system asked for a disk. That tells you the controller is alive enough to talk but can no longer reach its own memory — a partial failure, and a better position than a stick nothing sees at all, because the memory holding your photographs is behind the failed part and normally untouched. Decline every offer to format it: your computer believes the device is empty, and formatting would write over exactly what a recovery needs if the controller ever partially responds. Stop reinserting it too — the answer won't change and each attempt powers a failing chip for nothing. And when you get the files back onto a new stick, put a second copy somewhere else as well; a memory stick is the least durable storage you own.
That is a specific fault with a route — call Leeds Data Recovery on 0113 322 3083; access tested first, memory read at chip level past the controller, photographs validated and delivered on new media.
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.