Data Recovery Case File · Cameras, Drones & Cards · Two Different Readers
A Camera Reads Its Own Format Natively and a Computer Has to Be Taught It
This enquiry contains a contradiction that resolves neatly. A professional recording card that produces an error on a computer, where storage management reports it as "uninitialised" — and yet "the camera operator said he could see the footage on the camera." Both observations are true, and together they establish something valuable: the recording exists and is being read successfully by one device and not another.
| Media | Professional recording card — content playable in the originating camera; host storage management reporting the volume as uninitialised |
| Reported situation | Professional card used in a broadcast camera · content reported as visible and playable on the camera by its operator · card producing an error when connected to a computer · host storage management reporting the volume as uninitialised · media transfer required |
| Fault class | Host unable to interpret an appliance-native volume — card and content confirmed readable by the originating device; volume descriptor not recognised by the host |
| Equipment used | Camera playback treated as confirmation that content and card are sound · initialisation refused at the host · card imaged write-blocked at the block level before any interpretation · volume structure identified against the recording format rather than as a generic filesystem · media extracted from the image and validated by playback |
The decode: why one device reads it and the other does not
What the camera playing it back establishes: a great deal. Content readable on the originating device means the card responds, its controller runs, and the recording is physically intact.
Why that removes most of the usual worries at once: the hardware is fine. Nothing about contacts, controllers or memory degradation is consistent with successful playback.
What is left as the difference between the two devices: interpretation. The camera reads the format it wrote; the computer is being asked to read a format it may not implement.
Why professional recording formats differ from ordinary ones: they are built for the recorder. Broadcast cards frequently carry a volume structure designed around continuous high-rate writing rather than around general file storage.
Why a computer reports that as uninitialised: it has no vocabulary for it. Presented with a structure it does not recognise, a host concludes the volume has never been prepared.
Why that message is dangerous rather than merely unhelpful: it invites the fix. The natural response to being told something is uninitialised is to initialise it, and that writes a fresh structure over the recording's own.
Why the driver question is worth asking before anything else: it may be the entire fault. These formats are normally read through software supplied for them, and a machine without it sees nothing interpretable.
What is done here regardless: the card is imaged first. A block-level copy captures the volume exactly as written, and interpretation happens on the copy.
Why that order is worth insisting on even for a healthy card: the card is the only copy. Working from an image means no attempt, correct or otherwise, is made against the original.
What must not happen meanwhile: no initialising and no formatting, on any machine. The footage is confirmed present, and the only way to lose it now is to accept an offer.
On the bench
Camera playback was treated as confirmation that content and card are sound — successful reading on the originating device establishing that the card responds, its controller runs and the recording is intact, which excludes contact, controller and memory faults. The difference between devices is interpretation: professional formats carry volume structures built around continuous high-rate writing, which a host cannot recognise and therefore reports as never prepared. The card was imaged before any interpretation.
The outcome
Camera playback treated as confirmation, initialisation refused at the host, and the volume identified against the recording format on an image. Free assessment, one fixed written figure including VAT; where nothing is recovered, nothing is charged. The decode: both observations are true and together they are good news. The camera reads the format it wrote — the computer is being shown a structure it does not implement, and reports that as never having been prepared.
A card that plays in the camera and not on a computer
Refuse to initialise or format it on any machine — that message is the dangerous one, because the natural response to being told a volume is uninitialised is to initialise it, which writes over the recording's own structure. Take the camera playback as strong reassurance: content readable on the originating device means the card responds, its controller runs and the footage is intact. The difference is interpretation, and professional formats usually need the software supplied for them.
Don't initialise it — call Cambridge Data Recovery on 01223 655015; playback treated as confirmation, card imaged before any interpretation, volume identified against the recording format.
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.