SSD & flash · case file · SDR-2025-0918
It Stopped Saving, Then Stopped Reading.
The stick failed by instalments, and politely. First it refused to save anything new
and started throwing eject warnings; before long reading had gone the same way; now the MacBook simply reports that the disk inserted was not readable
. Aboard it, the cargo these things always seem to carry alone: a village history archive.
Seeing the same thing yourself?
0800 6890668
The translation.
Flash wears unevenly, and writing does the wearing: putting data into a cell costs it far more than reading one does, so a stick that loses saving ahead of reading is failing in the ordinary sequence. Once the controller cannot assemble enough sound blocks to hold its mapping tables together, it stops initialising at all. The Mac's complaint describes a conversation it can no longer hold with that controller. It says nothing about whether the scans are still held in the flash behind it.
Kit used on this job.
What happens in a case →| Platform | Its role in this case | Why we use it |
|---|---|---|
| PC-3000 Flash | Recognised the flash and read it beneath the failed controller | Pulls data straight from memory chips, with a current library that identifies them automatically |
| Rusolut Visual NAND Reconstructor | Reversed the scrambling and page interleave the controller had applied to the dump | Rebuilds files from a raw NAND image: ECC, XOR, page transforms, reassembly |
| R-Studio Technician | Put the FAT structures back and returned files under their own names | Wide filesystem support, with RAID rebuilds you can trust |
In the lab.
Establish whether the blockage is the controller or the flash itself
The stick was examined at chip level rather than through a USB interface it had stopped answering on. The memory matched its entry in the chip database without difficulty; the part failing to complete initialisation was the controller, exactly as the order of the symptoms predicted.
Take the flash raw, then unpick what the controller did
A raw dump came off the memory itself. What comes off is not a filesystem: it carries error-correction data, the controller commonly XOR-scrambles it, and pages sit in an order only the translation layer ever understood. All three had to be stripped back before anything file-shaped appeared.
Rebuild the filesystem, then open what came out
With page order sorted and error correction applied, the FAT structures were reconstructed and the archive recovered under its original filenames. Every scan and document was opened rather than tallied, because a file that will not open has not been recovered.
The result.
The scans and transcriptions came back and went out on fresh media, along with a gentle word about the phrase 'only copy' which appears to have landed.
Similar cases on the index.
Also from SSD & flash.
Does this sound like your own drive?
The rule holds as in every case above: switch it off, and let a free diagnosis come before any decision.