SSD & flash · case log · MKD-2025-4918
No New Scans in March, No Files by June.
It failed in the usual order. In March the library machine refused to take the new scans at all
; by June it would not give files back; today it manages only the balloon reading USB device not recognized
. Everything a heritage group near Winslow had gathered lived on that stick — log books shot page by page, wartime parish magazines, typed-up interviews with older residents.
Same fault? Start here.
0800 6890668
Without the jargon.
Flash wears out on the write, not the read. Writing to a cell wears it far harder than any read ever will, so saving failing before reading is not a coincidence — it is the sequence. A controller keeps shuffling worn blocks aside while it still has sound space for its own mapping tables. Once that space runs out it stops presenting itself as a device at all. The balloon Windows shows is describing that silence. It says nothing at all about whether the scans behind it are still readable.
The kit this job needed.
See how a job runs here →| Kit | Why it was used | What it gives us |
|---|---|---|
| PC-3000 Flash | Named the memory chip off its markings and read it direct | Pulls data straight off the flash chips, matching each part to a constantly updated ID library |
| Rusolut Visual NAND Reconstructor | Reversed the masking and page shuffling that the failed controller had imposed | Takes a raw flash dump to readable files: ECC, XOR, page order, reassembly |
| R-Studio Technician | Put the FAT volume back so the filenames the group typed survived | Copes with almost any file system; dependable array rebuilds |
What happened on the bench.
Work out which half had stopped talking
USB offered nothing, so the housing came apart and the board went on the bench. Probed directly, the memory identified itself against the library on the first attempt; the part that would no longer come up was the controller. Writes dying before reads had already predicted that division of labour.
Take the raw pages, then reverse the tidying
A raw dump looks nothing like a disk. Error-correction bytes run through every page, the controller has masked each one with an XOR pattern, and the order the pages belong in was held in a translation map that has gone. Correct, unmask, re-sequence — and only then does anything resembling a file appear.
Rebuild the volume, then open every file
The FAT structures came back together over the corrected dump, and the archive appeared under the names its volunteers had given it. Checking meant opening things one at a time — log books, magazines, transcripts — since a file nobody can open counts as lost, not recovered.
The outcome.
The whole archive travelled home on fresh media. The group has since written a rule into its minutes: three copies, one of them off the premises. The dead stick is kept as a warning.
Other jobs from the casebook.
More from SSD & flash.
Does that sound like your device?
One lesson runs through the lot: cut the power, let us look for free, then decide with the facts in hand.