A food writer in Richmond had spent the day on a MacBook working off a stick, as she always does, saving as she went. It behaved perfectly until about nine in the evening, when it stopped mounting and never mounted again. On it were a book manuscript at second-draft stage and the photographs to go with it.
| Media | A USB flash drive used daily on a MacBook that stopped being readable partway through an evening's work. It holds a manuscript and its accompanying photography. |
| What was reported | USB stick, had been working normally on a MacBook all day, suddenly would not read, nothing since, manuscript and photographs needed, recovery sought. |
| Fault class | Logical. The stick still enumerated and its memory read at full speed, so the controller was alive. The volume's index had been damaged, most likely by a write that did not complete when the stick was removed, so macOS could see a device and not a filesystem. |
| On the bench | Read behind a hardware write blocker with every repair prompt refused, the stick confirmed to enumerate and read at speed so that no chip-level work was needed, imaged in one pass, the volume parsed in R-Studio from the image with the damaged index rebuilt, remaining documents and images carved by content signature, everything validated by opening it and written to fresh media. |
The first question is whether the stick still answers, and it decides the price. A stick that enumerates has a working controller, which means the memory can be read through it and the job stays logical. A stick that has gone silent needs its memory reading directly at chip level, which is physical work under different terms. One test separates them, and it is the first thing done.
This one answered, so the fault was above the hardware. The device appeared, reported its correct capacity and read from end to end without a weak page. What macOS could not do was interpret what it read, which places the damage in the volume's index rather than in the memory.
Working all day and then failing is normal for this fault. An index is only rewritten when something changes. It can sit half-damaged for hours while everything appears fine, because nothing has needed to consult the damaged part, and then one save reads the wrong record and the whole volume stops mounting.
The habit behind it is the real problem. Working directly off a stick means every save is a write to a small device with a simple controller and no redundancy of any kind. It is a working method rather than a storage method, and a second-draft manuscript deserves better than a device you can lose in a coat pocket.
The first test was the one that mattered: behind a hardware write blocker, the stick enumerated, identified itself and read at full speed across its whole capacity with no weak pages. That confirmed a working controller and healthy memory, so nothing had to be desoldered and the job stayed a logical one.
It was imaged in a single pass and the original set aside. R-Studio parsed the volume out of the image, where the index was damaged in one region and intact elsewhere. Most of the directory rebuilt from the surviving records; the remainder, including several versions of the manuscript, was carved by content signature. Everything was opened and read before being written to fresh media.
The manuscript came back at its last save, along with two earlier drafts she had forgotten existed and the whole photographic set. She now writes to the laptop and copies to the stick, which is the correct way round.
Sticks and cards are £250 + VAT. Because the controller was alive and the fault was confined to the filesystem, this was logical work and ran under no fix, no fee, invoiced after she had opened the recovered draft.
Take it out and stop putting it back in. Every remount is another chance for the operating system to try to help, and both macOS and Windows will offer to repair or format a volume they cannot read. Eject properly when you do use a stick, because removing one mid-write is the usual cause of this fault, and a Mac in particular buffers writes for longer than people expect. Do not run a disk repair utility, which writes its conclusions to the device. And do not work directly off a stick with anything that matters: use it to carry copies, not to hold originals.
These files are written up from genuine enquiries taken from households and businesses in Bracknell, across Berkshire and Surrey and into London, with names, firms and anything else identifying stripped out. Each one sets down how the fault was reasoned through, the method it actually needed and the equipment it was worked on. One of them is a job that was turned away, which belongs here as much as the rest of them.
A format prompt is the machine admitting it cannot read the index, not an instruction to obey
Corrupted details followed by no recognition at all is a controller failing in two stages
A cracked card can still be recovered, provided the break missed the memory die itself
Examining it is free and takes 2 working days from arrival, the figure goes to you in writing and does not move afterwards, and a logical fault carries no fix, no fee. Start online or ring the freephone.