SSD & flash · job file · BHD-2025-8918
It Would Take Nothing New, Then Gave Nothing Back.
A Redditch history group had put everything on one stick: parish log books photographed a page at a time, magazines from the war years, and older residents' recollections typed out across several winters. The decline came in the usual order. Back in March the machine in the library would not take a single new scan
, by June nothing would open at all, and today it manages only USB device not recognized
.
Sounds like yours? Give us a ring.
0800 6890668
What that means.
Windows is reporting a controller that has gone quiet. It is not reporting the scans. What matters here is the sequence, because flash wears out through writing rather than reading — every program cycle costs a cell a little of its life, while reading costs it nothing. Losing saves in March and losing access in June is exactly the shape of worn flash. For as long as spare blocks last, the controller quietly retires the tired ones and parks its translation tables on ground it still trusts. Once that ground is gone, the device drops off the bus entirely.
What did the work here.
The order of the work →| Equipment | The job it did | What it adds |
|---|---|---|
| PC-3000 Flash | Matched the chip to a known part, then dumped it off the board | Goes straight to the NAND chips, checked against a maker-ID library that is kept current |
| Rusolut Visual NAND Reconstructor | Stripped the XOR pattern and restored the page order the dead controller had scrambled | ECC, XOR, page order and reassembly: what makes a raw NAND dump readable |
| R-Studio Technician | Reassembled the FAT volume so the volunteers' own file names came back with it | Broad file-system support, with RAID rebuilds that can be trusted |
What we did.
Which part had died: memory or controller
USB gave back nothing at all, so the casing came off and the board went under probes on the bench. Approached directly, the memory replied straight away and identified itself as a part we hold a profile for. The controller beside it stayed silent. That split was already implied by the way the fault had arrived — saving first, then reading.
Take the pages raw, then unpick the bookkeeping
A raw dump looks nothing like a drive image. Each page comes off with its error-correction bytes attached, each is masked by whatever XOR pattern that controller happened to use, and the sequence they belong in was recorded by a translation layer that is now gone. Correct, unmask, re-order — and only at the end of all that does a file take shape.
Put the volume back, then open every file
Once the dump was corrected and back in order, the FAT tables made sense again and the archive came up with the file names the group had given it. Checking was done by hand, item by item: the log books, the magazines, the typed interviews. A file nobody can open has not really come back, whatever a total says.
How it closed.
All of it went home on new media. The group has since put its own rule in the minutes: three copies of everything, one of them somewhere else entirely. The dead stick stays in the box as a lesson.
Other pages worth a look here.
Alongside SSD & flash.
Is yours behaving the same way?
Switch the device off, post it in, and decide nothing until the diagnosis comes back to tell you where you stand.