Data Recovery Case File · Memory Cards · Broke During the Rescue

It failed while he was saving it: the copy that didn't break the card — it found the break

The cruellest-feeling failure timing there is: this customer was partway through doing the right thing — copying hundreds of photos off his 128GB SD card to the desktop — when Windows stopped mid-operation to announce the card "didn't use a recognised file system" and offered a format. He declined, correctly, knowing it would cost him everything. But the damage seemed done: the card no longer worked in his cameras either. His enquiry carried the question this timing always plants: did copying it kill it?

DeviceSanDisk Extreme 128GB SD card; hundreds of photographs
Reported eventsCopy to desktop began normally, then failed with "not a recognised file system" and a format prompt (declined); card subsequently rejected by cameras as corrupted
Fault classFilesystem structures corrupted on marginal media — surfaced, not caused, by the sustained read
Equipment usedWrite-blocked imaging · ACE Lab Data Extractor (filesystem reconstruction)

Did the copy break it? The honest mechanics

Reading doesn't damage flash in any way that matters — but a full copy is the most thorough read a card ever gets, and thoroughness is exactly what exposes rot that lighter use skated over. A card can carry quietly-corrupted filing structures or weakening cells for months while a camera writes new files into healthy regions and previews only recent shots; then the rescue copy arrives, marches methodically through everything, and hits the bad patch that daily use never touched. Mid-march, the volume's structures failed to parse, Windows threw its hands up — "not a recognised file system" is its phrase for a filing system it can see the shape of but no longer read — and the cameras, meeting the same broken paperwork, refused the card too. So the answer he needed first: no — the copy was the messenger. The corruption predated it, the photos behind the paperwork were never the casualty, and his one genuinely important decision — refusing the format — kept them exactly where the copy found them.

The recovery

The card still presented at raw level, so it was imaged once, write-blocked, and everything after that happened to the copy. In Data Extractor, the volume's damaged structures were rebuilt from the redundant records the filesystem keeps — the corrupted primaries reconciled against their backups — and where the paperwork was beyond reconciling, the photographs were recovered by what they are rather than where they were listed, carved by signature and re-ordered by their own internal dates. The library came off essentially complete: hundreds of photos, the overwhelming majority with names and folders intact, the remainder whole but renamed — verified by opening frames across the shooting history, and delivered on new media alongside a retired card and a completed copy, at last.

Outcome

Effectively full recovery — and absolution for the copy, which deserves it, because the fear this case answers stops people making rescue copies at all. The refined version of the lesson: copy early and copy watchfully — a transfer that stalls, slows drastically or errors partway is a card confessing, and the correct response is to stop, keep what's already across, decline every repair and format offer, and bring the card in with the confession noted. And for the card itself: any card that's thrown a filesystem error retires on the spot, whatever a reformat later makes it claim. Cards are consumables that carry treasure; the treasure moves on, the consumable doesn't get a second act.

When a copy fails partway

Stop the transfer and don't restart it repeatedly — each full pass grinds the same weak patch. Keep whatever copied successfully, decline format and repair prompts on the card, and don't run consumer recovery apps that write their findings back to the same card. The photos almost certainly survive behind the broken paperwork; they need the paperwork rebuilt on a copy, not the card interrogated further.

Card died mid-rescue?
The rescue found the fault — it didn't cause it. Call Bristol Data Recovery on 0117 332 1137 and we'll finish the copy properly.
Request a quote online →

Our case files are drawn from genuine enquiries received by our laboratory over the past ten years, anonymised to protect client confidentiality. Each one describes the diagnostic and recovery procedure our engineers apply to that fault, using the equipment listed.

Call us — 0117 332 1137
Mon–Fri · 9am–5:30pm · No fix, no fee
Start a free diagnostic →