Data Recovery Case File · Cameras, Drones & Cards · Get Through the Rest of the Trip
The Card Is Not Fixable Where You Are
This enquiry arrived from a long way from home with days of the trip still to run. On the fifth day, "our camera suddenly showed the error message 'card error'. We've inserted the card into several different computers, but none of them will even identify that the card is inserted, meaning that currently we've lost the many photos that we've taken." Nothing about this can be resolved where they are — and what matters now is the rest of the trip, because a good decision today protects the photographs still to be taken.
| Media | SD card from a digital camera — reported as faulty by the camera and not enumerated by any computer; content from the first days of an extended trip held |
| Reported situation | Card in normal use in a camera during an extended trip · camera reporting a card error on the fifth day · card not identified by several computers · no host recognising the card as present · photographs from the trip to date held · trip continuing |
| Fault class | Device-level failure to enumerate — controller not presenting; content held in memory pending direct read |
| Equipment used | Card isolated and not reinserted for the remainder of the trip · read at chip level past the controller on return · translation layer reconstructed in software · media validated by rendering |
The decode: what the symptom means, and what to do for the next week
Why "not even identified" is the important phrase: most failing cards appear as a device and refuse to present a volume. This one is not being seen at all. That places the fault at the controller — the card is not completing the introduction that would let a computer know something is there, which is below any filesystem question and out of reach of anything software could do.
Why the photographs are almost certainly intact: a controller that cannot introduce itself has not erased anything. Images are held as trapped charge in the memory inside the package, and the component that failed is the one that interprets it. The pictures are behind a broken doorway, not gone.
Why nothing can be done in the field, and this is worth saying plainly: reading the memory past a failed controller requires bench equipment. There is no travel-friendly version, no application that helps, and no shop abroad likely to have the tooling. Every hour spent looking for one is an hour not spent on the trip.
So what to do today, in order. Put the card in a case or an envelope and do not put it back in the camera — a camera meeting media it cannot interpret may offer to format it, and that is a confirmation away. Buy a new card. Almost anywhere sells them, any reputable brand at a modest capacity is fine, and the cost is trivial against the days remaining.
Then change how the rest of the trip is handled: offload to a laptop, a phone or a cloud service at the end of each day, and use more than one card rather than filling a single large one. The exposure in this case is that five days lived on one card — and the same arrangement is about to carry the remaining days unless something changes.
On getting it home: carry the failed card in hand luggage, in something rigid. It is small, it is the only copy, and it should not be in a checked bag.
What happens on return: the memory is read directly through the manufacturer's test points, bypassing the failed controller entirely, then descrambled, error-corrected and reassembled in software. Cards in this condition are among the more routinely recoverable devices in this archive.
On the bench
The card was isolated and not reinserted for the remainder of the trip — a camera meeting uninterpretable media offering to format it, which is one confirmation from ending the case. On return it was read at chip level past the controller, the fault being the controller's failure to introduce itself rather than anything affecting stored charge. The translation layer was reconstructed in software and media validated by rendering.
The outcome
The card kept isolated for the rest of the trip and read at chip level past the controller on return. 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: a card no computer will even see has failed at the controller, which is below any filesystem question — so nothing software can do reaches it, and nothing can be done while travelling. Your photographs are held as charge in the memory behind it. Buy a new card and carry on.
Card that fails partway through a trip
Put it in an envelope, buy a new card, and carry on shooting — there is nothing you can do about it where you are, and hours spent looking for a shop that can help are hours off your holiday. A card no computer will even detect has failed at its controller, which is below any filesystem question and out of reach of software entirely; the photographs are held as charge in the memory behind it and nothing has erased them. Don't put it back in the camera, which may offer to format it. For the remaining days, offload to a laptop or phone each evening and use several smaller cards rather than one large one. Carry the failed card home in hand luggage, in something rigid.
Buy a new one and carry on — then call Guildford Data Recovery on 01483 901310; read at chip level past the controller, translation layer reconstructed, media validated by rendering.
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.