Data Recovery Case File · Cameras, Drones & Cards · Deformation Around the Slot
It Introduces Itself, So the Impact Missed What Mattered
His enquiry describes serious physical damage and a symptom that is quietly reassuring. A card in an action camera "smashed into some rocks. The camera was dented and pushed the insides. The card looks physically fine, but it says error on my other camera and my computer says the disk is unreadable." Being called unreadable means it was read enough to be found — the device presented itself, which is the question physical damage usually decides.
| Media | 64GB card from an action camera subjected to severe impact — camera body deformed; card enumerating; filesystem not interpretable; approximately 20GB written |
| Reported situation | Action camera struck against rocks · camera body dented with internal deformation · card removed and visually undamaged · card producing an error in an alternative camera · host reporting the volume as unreadable · approximately 20GB of 64GB capacity written |
| Fault class | Filesystem damage from an interrupted write during impact — card enumerating, internal routing intact; contact edge to be examined for slot deformation damage |
| Equipment used | Enumeration accepted as evidence of surviving internal routing · contact edge examined under magnification for deformation damage · imaged write-blocked under strict timeouts · structures reconstructed from surviving copies · signature carving across the written extent · media validated by rendering |
The decode: what presenting itself proves, and what to check anyway
Why the message is good news: for a computer to report a volume as unreadable, it must first have detected a device, powered it, and had it report a capacity. All of that requires the fine internal routing between the memory package and the contacts to be intact — which is exactly what physical damage destroys when it destroys anything.
So the biggest question is already answered: the impact did not sever the card's connections. What it did instead is damage the filesystem, which is a description rather than the images themselves.
How impact damages a filesystem: the camera was recording. An abrupt stop cuts power and interrupts whatever write was in progress — almost always a structure update, since cameras write file records continuously as footage grows. A record half-written is internally inconsistent, and a system meeting one declines to mount the volume.
What is worth examining despite the card looking fine: the contact edge. A card slot is a row of sprung contacts, and a body crushed hard enough to push its internals can bend them or press them against the card — leaving marks, scoring, or slight deformation on the contact strip. That is visible under magnification and not to the eye, and it affects whether the card should be inserted anywhere again.
Why the other camera reporting an error agrees: a device meeting a filesystem it cannot interpret reports a card error, which is the same finding in different words. Two devices agreeing confirms the card rather than either of them.
Why the written proportion matters a great deal: around 20GB of a 64GB card means roughly two thirds has never been written. Recorded footage on a freshly-used card is laid down contiguously from the start, so the material occupies a known, continuous region and carving through it is straightforward — with no risk of confusion from older overwritten content.
What must not happen: no further insertion into either camera. A device meeting an uninterpretable card may offer to format it, and action cameras in particular tend to do so with minimal ceremony.
On the bench
Enumeration was accepted as evidence of surviving internal routing — a host reporting a volume as unreadable having detected the device and received a capacity, which requires the fine connections between memory package and contacts to be intact. The contact edge was examined under magnification for deformation damage, a crushed body being able to bend the slot's sprung contacts against the card. Imaging ran write-blocked under strict timeouts, with structures reconstructed from surviving copies and signature carving across the written extent.
The outcome
Enumeration accepted as proof the routing survived, the contact edge examined under magnification, and the written extent carved after structure reconstruction. 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: being told the disk is unreadable means it was found — the card presented itself and reported a capacity, so the impact missed the internal connections. What it damaged is the filesystem, because the camera was writing when it stopped.
Card from a camera destroyed by impact
Keep it out of both cameras — a device meeting a card it can't interpret may offer to format it, and action cameras tend to do that with very little ceremony. Take encouragement from the wording though: for a computer to call a volume unreadable it first had to detect the device and receive a capacity, which needs the fine internal connections between the memory and the contacts intact. That's the question physical damage usually decides, and yours survived it. What broke is the filesystem, because the camera was writing when it stopped. Worth having the contact edge looked at under magnification, since a crushed body can bend the slot's contacts against the card.
Don't put it back in — call Oxford Data Recovery on 01865 593000; enumeration accepted as proof the routing survived, contact edge examined under magnification, imaged under strict timeouts.
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.