Case file · SSD & flash · BDR-2025-0918
It Couldn't Save, Then It Couldn't Read.
The stick's decline was orderly, almost polite. It began with being unable to save anything
and awkward ejects; then reading joined writing on the casualty list; now the laptop announces the disk inserted was not readable
. On it, the kind of cargo USB sticks always seem to carry alone: important university work.
Same symptoms on your desk?
01273 964902
The decode.
Flash memory wears out asymmetrically — writing degrades cells far faster than reading does, so a stick that loses saving before reading is failing in the textbook order. When the controller can no longer find enough good blocks to maintain its translation tables, it starts refusing to initialise at all. 'Not readable' means the computer can no longer negotiate with the controller; it says nothing about whether the coursework is still sitting in the memory behind it.
Equipment on this case.
How a case runs →| Platform | What it did here | Why this tool |
|---|---|---|
| PC-3000 Flash | Identified the memory and read it below the failing controller | Reads memory chips directly, with a current chip database for automatic identification |
| Rusolut Visual NAND Reconstructor | Undid the controller's scrambling and page ordering on the raw dump | Turns a raw NAND dump back into files: ECC, XOR, page transformation, reassembly |
| R-Studio Technician | Rebuilt the FAT structures and recovered named documents | Broad filesystem coverage and dependable RAID reconstruction |
On the bench.
Confirm the controller is the obstacle, not the memory
The stick was assessed at chip level rather than through the USB interface it had stopped honouring. The memory identified normally against the chip database; the controller was the component failing to complete initialisation, exactly as the symptom sequence had suggested.
Read the memory directly, then undo what the controller did
A raw dump was taken from the memory itself. Raw NAND is not a filesystem — it carries error-correction codes, is frequently XOR-scrambled by the controller, and stores pages in an order only the controller's translation layer understands. All three had to be undone before anything resembling a file appeared.
Rebuild the filesystem and check the documents open
With page order and error correction resolved, the FAT structures were reconstructed and the coursework recovered with filenames intact. Each document was opened rather than counted, because a recovered file that won't open is not a recovered file.
The outcome.
Essays and coursework recovered and returned — plus one unsolicited piece of advice about the phrase 'sole copy', delivered gently and, by all accounts, taken.
Related on the index.
More from SSD & flash.
Recognise your own drive in this story?
Same rule as every case above: power it down, and let the diagnosis be free before any decision has to be.