Data Recovery Case File · Cameras, Drones & Cards · The Cheapest Thing to Eliminate

It Disconnected Halfway Through the Import

Her enquiry described a professional afternoon going wrong in stages. After a photoshoot the previous day, with the card in a reader and images being selected for import: "about 30 minutes in, before I'd imported, the card disconnected and I assumed I had nudged the card reader too much. Put it in again and was picking out photos, pressed import, and weirdly the card did not upload any images as per usual." The instinct to blame the nudge was reasonable and may well be right — but it points somewhere most people never look. The card reader is the cheapest component in the chain and the least suspected, and a reader that drops a connection mid-session can damage the card it is holding.

The decode: why the reader matters, and what the disconnection did

Why readers are the weak link: a card reader is often the least expensive item in a professional workflow — a few pounds, bought once, carried everywhere and never thought about again. Their failure modes are exactly the ones that cause this: contacts that wear and lose grip, a socket that no longer holds the card firmly, a cable or connector that has loosened, and cheap controllers that drop out under sustained transfer. A photographer will replace a lens cap more readily than a reader that has been quietly deteriorating for two years.

Why the disconnection is not a harmless event: this is the part that connects the two halves of her afternoon. Even during selection, applications read from the card continuously — generating previews, reading metadata, building caches. A disconnection during that is an interrupted operation, and if the software or the operating system was writing anything at the time, the card's filing structures can be left mid-update. That is very likely why the subsequent import returned nothing: the card was damaged by the disconnection rather than by anything she did afterwards.

What to eliminate, in order, and it costs almost nothing: try the card in a different reader, ideally one known to work, and directly on the computer rather than through a hub. Try the camera itself as a reader, connected by cable, since that removes the reader from the chain entirely. If the card behaves in another reader, the original reader is the fault and should be replaced immediately — it will do this again. If the card fails everywhere, the card has been damaged and the reader is still the likely cause.

Why her timing helps: the shoot was yesterday and she has not reformatted or reshot. The images are almost certainly physically present, with damaged records describing where they are. Reconstruction on an image typically returns the folder structure and filenames, which for a catalogued import matters as much as the files.

What not to do: keep re-importing. Each attempt reads across a card whose structures are inconsistent and risks the software or the system offering to repair it. And the camera will eventually offer to format the card, which would replace the damaged index with an empty one.

The workflow point worth taking: readers are consumables. Replacing one every couple of years costs less than a single recovery, and on a job that cannot be reshot it is worth using the camera's own connection rather than a reader that has been in a bag for years.

On the bench

The reader and interface were eliminated separately from the card, since a reader that drops connections is both a plausible cause and the cheapest thing to rule out — and a card that behaves in other readers points at a component the owner would otherwise keep using. The card was then imaged write-blocked behind the DeepSpar USB Stabilizer 10Gb, and the structures left mid-update by the disconnection were reconstructed on the image rather than the card. Every photograph was validated by rendering at full resolution and ordered by embedded capture time.

The outcome

The reader eliminated as a separate component, the interrupted structures rebuilt from a write-blocked image and the shoot validated and delivered in capture order. Free assessment, one fixed written figure including VAT, no recovery, no fee. The decode, for anyone whose card failed during an import: suspect the reader, because it is the cheapest item in the chain and the least examined — worn contacts, a loose socket and cheap controllers that drop out under sustained transfer are exactly the faults that cause this; a disconnection mid-session is not harmless, since applications read and write continuously during selection and an interruption leaves the filing structures mid-update. Try another reader and the camera's own cable, and stop re-importing.

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.