A retired teacher in Atherstone still uses a 64MB thumb drive she was given at a conference in the early years of the century, on the reasonable grounds that it has never let her down. On it are letters to and from a former pupil who went on to write about their correspondence, and a set of notes she has never transcribed. It stopped being recognised, then began appearing with a connection error and a prompt to format it before use. She refused, several times, and rang to ask whether refusing had been the right call.
| Media | A 64MB USB thumb drive of considerable age that stopped being recognised and now produces a connection error and a prompt to format the volume before use. It holds a correspondence archive and handwritten notes. |
| What was reported | 64MB USB thumb drive, in use for around twenty years, stopped being recognised, now shows a connection error and asks to be formatted before use, the owner declining every prompt, no copy of the letters anywhere. |
| Fault class | Filesystem damage rather than a hardware failure. The controller was answering and the memory was readable; what had gone was the small structure describing the volume, so the operating system saw storage it could not interpret and offered the only remedy it knows. The letters were intact and had never been erased. |
| On the bench | Read behind a hardware write blocker from the start, which removed any possibility of an operating system writing a fresh volume onto it. Imaged in a single pass through a controlled reader, with the two slower regions given their own attempts. The volume was then rebuilt from the image in R-Studio, following each surviving directory record rather than guessing at file lengths, and the correspondence was opened, checked for readable text and written to fresh media. |
Refusing the prompt was the whole job, and she deserved to be told so. Formatting writes a new and empty description of the volume over the old one. It does not scrub the memory, but it removes the only surviving record of where each letter begins and ends, which forces everything afterwards to be guessed from content. On a drive of documents that means recovered files with the wrong ending attached.
Connection error is a generic phrase and worth not over-reading. Windows produces it when a device answers but does not behave as expected during initialisation, which covers a failing controller and a volume it cannot parse equally well. The two need different treatment, so the first bench question is always which of them you have, and that is answered by whether the memory reads rather than by the wording of the message.
Twenty-year-old flash fails in the bookkeeping before it fails in the memory. The area holding the volume description is written every time anything changes, while the cells holding a letter written in 2006 have been read many times and written once. Wear is unevenly distributed by design, and the most-written region is the one that gives out first, which is why so many old drives die with their contents perfectly intact.
Small capacity turned out to be an advantage here. A 64MB drive uses simple, early flash with large cells and a straightforward controller, and it holds so little that nothing had ever been overwritten. Almost every file on it was contiguous. The reconstruction was consequently one of the cleanest of the batch, which is not what most people expect when they hand over something two decades old.
The drive answered on a controlled reader behind a write blocker, which settled the first question straight away: the controller was alive and the memory was reachable, so nothing needed to come off the board. It read at its own unhurried pace with two short regions that needed a second attempt, and a complete image was taken.
From the image, the volume description proved damaged past use while the directory area behind it was largely intact. R-Studio rebuilt the volume by reading those records directly and following each file's own chain, and the handful with damaged records were recovered by content signature and flagged rather than presented as equals. Every document was opened and checked for readable text, because a document that opens and shows nothing is not a recovery.
The whole correspondence came back, both sides of it, along with the untranscribed notes and a folder of scanned photographs she had forgotten putting on there. It went out on new media with a second copy, and she was gently advised that a drive from the early two thousands should not be the only home for anything.
A pen drive or stick is £250 + VAT. This was reading rather than repairing, with the casing intact and nothing lifted off a circuit, so no fix, no fee applied and the invoice did not follow until she had read a letter off the new media.
Keep refusing, and take the drive out. That dialog is not offering to repair anything: it is offering to write a new empty index, and the index is the map to everything you want. The same caution applies to the check-and-repair tool Windows suggests afterwards, which will discard records it cannot interpret and can turn a rebuildable volume into a folder of numbered fragments. Do not run a disk utility that offers to fix errors, do not assign it a new drive letter in the hope that helps and do not try it in a machine belonging to somebody who might click yes on your behalf. If the drive is old, that is a point in its favour rather than against it, because old flash usually keeps its contents long after it stops being able to describe them. Post it in a rigid box and say roughly how old it is, since early controllers behave differently from recent ones.
What this job cost, and on what terms. This one was charged at £250 + VAT, the figure agreed in writing before any work began. Paying for a job like this one. Nothing here called for the disk to be opened, a board rebuilt or a chip lifted off, which puts the work on the logical side of the line and under no fix, no fee. Files back, invoice follows; nothing back, nothing owed, and the media goes home either way. Four sorts of work sit outside that promise and only those four: DVR jobs, forensic jobs, chip-level work, and electronic or mechanical failure. The rest keep it, firmware and service-area repair included — both are logical jobs whatever their reputation suggests.
If yours is doing the same thing. This card was read at Oxford Data Recovery on the Oxford Science Park, about fifty-five miles down the M40. Post it tracked and insured, send it by a courier you book yourself, or bring it to the Oxford reception during Mon–Fri 9:00am–5:30pm — there is no collection service and no counter in Coventry. The free look at it takes two working days from booking in and produces one written figure that then holds.
Freephone 0800 689 0668 to talk it through first. The shipping form and what goes in the parcel are on the contact page, and every band is published in full — including which work sits outside no fix, no fee.
These are real enquiries, from households and from businesses in Coventry and out across Warwickshire — Nuneaton and Bedworth, Rugby, Leamington Spa, Warwick, Kenilworth, Solihull, Stratford-upon-Avon, Atherstone and Southam. Names are gone: the customer, the company, the job title, anything at all that would point back at a person. What stays is the reasoning — what turned up, where the fault genuinely sat, which approach it demanded, and which machine on the bench did the work. One of the thirty-six was refused, and it earns a place here as squarely as any of the rest.
A connector that never fitted properly has been working its solder joints loose the whole time
An intermittent contact writes half a change and leaves the index describing something that is no longer there
A camera asking to format a card is a camera admitting it cannot read the index, nothing more
A drive asking to be formatted that you have not formatted? Ring 0800 689 0668. Sticks are £250 + VAT and the assessment is free.