Data Recovery Case File · Solid State & Flash · The Good Kind of Failure
It Shows Up and Will Not Open
His enquiry contains a distinction that is easy to miss and decides the outlook. A USB stick holding all his work: "yesterday afternoon it worked fine, but then the laptop I was on crashed. I tried to copy the files from this USB to another and it failed to copy anything, and now it shows up when I plug it into a laptop or PC but cannot be opened." Those two halves — shows up and cannot be opened — sit either side of an important boundary. The hardware is working and the filing structures are not, which is the more recoverable of the two failures by a considerable margin.
| Media | USB flash drive holding work files — enumerating on multiple hosts; volume failing to mount following a host crash while connected |
| Reported situation | Stick working normally until the host machine crashed while it was connected · subsequent copy attempt transferring nothing · device enumerating on multiple computers · volume not opening · work content held |
| Fault class | Filesystem structure damage from an interrupted write — device hardware functional, content intact beneath damaged structures |
| Equipment used | No repair or format permitted · imaged write-blocked before any reconstruction (DeepSpar USB Stabilizer 10Gb) · structures rebuilt on the image including surviving backup copies · signature carving alongside · files validated by opening |
The decode: what the split means, and why the crash caused it
Why enumerating is genuinely good news: for the stick to appear when plugged in, it must accept power, start its controller, complete the introduction its interface requires, and identify itself. That is the whole hardware chain working — memory package, controller, connector and all. Devices with failed controllers or damaged memory do not get that far. On multiple machines, no less, which eliminates the host as well.
What is failing instead: the operating system reads the volume's filing structures and cannot make sense of them, so it declines to mount rather than presenting something it does not trust. The files themselves are untouched — they sit exactly where they were written. What is damaged is the index describing where they are, which is a much smaller and much more reconstructable thing.
Why the crash did it: a machine failing while a device is connected interrupts whatever write was in flight. Filesystems used on removable media generally have no journal — no running record of intended changes that can be replayed or unwound on the next mount. So an interrupted write leaves the structures half-updated, with nothing available to reconcile them. Journalled filesystems recover from this automatically; the ones used on sticks and cards cannot, which is why a crash is far more damaging to removable media than to a system drive.
Why the copy attempt transferred nothing: consistent with the above rather than a separate problem. There was no readable volume to copy from, so the operation had nothing to work with. It is not evidence that the files are gone.
The critical instruction: refuse every offer to repair or fix the drive. Windows will propose scanning and fixing a volume it cannot read, and repair utilities write their conclusions back — discarding whatever they cannot parse and, on a damaged structure, frequently producing a mountable volume with most of the contents missing. A failed repair is recoverable; a successful one often is not. The same applies to formatting, which is the other thing that will be offered.
Why the outlook is good: filesystems keep backup copies of their key structures at known positions, and rebuilding from one typically returns files with their folders and original names intact.
On the bench
No repair or format was permitted, since the system's offer to scan and fix writes its conclusions back and a successful repair on damaged structures commonly yields a mountable volume missing most of its contents. The stick was imaged write-blocked behind the DeepSpar USB Stabilizer 10Gb before any reconstruction, and the structures rebuilt on the image — including the backup copies filesystems maintain at known positions, which is what allows files to return with folders and original names rather than as an unnamed heap. Signature carving ran alongside, and files were validated by opening.
The outcome
The stick imaged before anything was repaired, structures rebuilt from their surviving backup copies and every file validated by opening. 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 stick appears but will not open: that split is good news. Appearing means the whole hardware chain works — controller, memory, connector — on multiple machines. Not opening means the filing structures are damaged while your files sit untouched beneath them. A host crash does this because removable filesystems have no journal, so an interrupted write is left half-finished with nothing to reconcile it. Refuse every offer to scan and fix.
USB stick that appears but won't open
Say no to every offer to scan and fix it, and don't format it. The two halves of what you're seeing are actually encouraging: appearing when plugged in means the controller, memory and connector all work, and doing so on more than one machine rules out the computer too. Not opening means the filing structures are damaged while your files sit exactly where they were written underneath. That's the recoverable failure. A host crash causes it because the filesystems used on sticks and cards have no journal — no running record of intended changes that can be replayed afterwards — so an interrupted write is simply left half-finished. The danger now is repair tools, which write their conclusions back and often produce a volume that mounts with most of the contents missing. A failed repair is far better than a successful one.
Refuse the repair prompt — call Newcastle Data Recovery on 0191 406 1051; imaged write-blocked before any reconstruction, structures rebuilt from surviving backup copies, files checked by opening.
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.