Data Recovery Case File · Cameras, Drones & Cards · Once It Fails, It Goes in an Envelope
The Highest Stakes in This Archive
His enquiry has no margin in it at all. A professional-grade card that "worked yesterday in the camera, and I went to offload the footage from it today and the computer couldn't read it. I put it back in the camera and now the camera cannot read it. It has the full wedding on it." A wedding is one day, once, with an obligation attached. And the middle step — putting a card that had just failed back into the camera — is the one to look at, because it is the reflex everybody has and it risks everything for nothing.
| Media | High-speed professional SD card holding complete single-event wedding coverage — unreadable on a computer at offload, subsequently unreadable in the originating camera |
| Reported situation | Card functioning normally in the camera the previous day · offload attempted the following day · computer unable to read the card · card returned to the camera by the owner · camera also unable to read it · complete coverage of a single unrepeatable event held |
| Fault class | Filesystem structure damage on high-bitrate media — content present; further device insertion presenting avoidable exposure |
| Equipment used | Card removed from all devices and not reinserted · imaged write-blocked (DeepSpar USB Stabilizer 10Gb) · structures reconstructed on the image from surviving copies · format-aware carving for camera containers alongside · footage validated by playback and reported by ceremony segment |
The decode: the reflex, and the rule that should replace it
What putting it back in the camera risked: three things, none of which had any chance of helping. A camera meeting a card whose structures it cannot interpret will very often offer to format it — one confirmation away from ending the case. It may write its own folder structure onto media it considers uninitialised. And it will certainly attempt to read and index, which on a card with damage means working the failing regions again.
Why it almost certainly did not cause the second failure: the card was already unreadable on a computer before it went back. The camera failing too is confirmation rather than consequence — the same structures, read by a second device, producing the same result. So he has not made it worse; he has taken a risk that happened not to land. That distinction is worth being clear about, because self-blame is not useful and the exposure was real.
The rule that replaces the reflex, and it is one sentence: once a card fails to read on any device, it does not go back into a camera. It goes into a case or an envelope. The instinct to check whether it still works in the original device is universal and it buys nothing — a card that failed on a computer will fail on a camera, and the camera is the device most likely to offer to fix it.
Why the outlook is genuinely reasonable: the card was working the previous day, so the content was written successfully. Structure damage of this kind removes the description rather than the recordings, and professional cards used for high-bitrate video hold large, continuous files with distinctive headers — which carve exceptionally well even where no index survives.
What is done differently for footage of this kind: validation by playback rather than by file count, and reporting by segment — the ceremony, the speeches, the first dance — because a client needs to know which parts of the day are accounted for, not how many files came back.
The professional point, said plainly: tell the couple early and factually if there is any doubt. An honest early conversation is survivable; a silence followed by a gap is not.
The practice worth adopting afterwards: offload to two destinations and verify before the card leaves the bag. A single card holding a whole event is the exposure this case is made of.
On the bench
The card was removed from all devices and not reinserted — a camera meeting uninterpretable media offering to format it, potentially writing its own folder structure, and certainly working the failing regions again. It was imaged write-blocked behind the DeepSpar USB Stabilizer 10Gb, structures reconstructed on the image from their surviving copies, with format-aware carving for camera containers alongside. Footage was validated by playback and reported by ceremony segment rather than by file count.
The outcome
The card taken out of every device, imaged write-blocked and the structures rebuilt with carving in parallel, validated by playback and reported by segment. Free assessment, one fixed written figure including VAT; where a chip has to be removed, 50% of parts and labour is payable upfront with the balance only on success — otherwise no recovery, no fee. The decode, and the rule worth keeping: once a card fails on any device, it goes into an envelope rather than back into a camera. The camera is the device most likely to offer to format it, and checking whether it still works there buys nothing.
Professional card that failed before offload
Once a card fails to read on any device, don't put it back in the camera — that reflex is universal and it buys you nothing. A camera meeting media whose structures it can't interpret will very often offer to format it, may write its own folder structure onto what it considers uninitialised media, and will certainly work the failing regions again while trying to index. A card that failed on a computer will fail in a camera too, so there's no information to gain. Put it in an envelope instead. The outlook is reasonable: it was working the day before, so the footage was written successfully, and structure damage removes the description rather than the recordings. Tell the client early and factually.
Keep it out of the camera — call Guildford Data Recovery on 01483 901310; imaged write-blocked, structures rebuilt with carving in parallel, footage validated by playback and reported by segment.
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.