Data Recovery Case File · Cameras, Drones & Cards · Test the Other Variable
Something Dropped the Connection, and It Was Not Necessarily the Card
Her enquiry contains a component most people would not think to mention. A card holding photographs from a trip: "plugged in to laptop to transfer files and got a message saying disk not ejected properly. After this the card stopped working and now says no images when plugged back into the camera. I was using a multi-card r"eader. That message means the host lost the device mid-operation — and on a cheap multi-format reader, the reader is at least as likely a culprit as the card.
| Media | SD card holding trip photography — connection lost during transfer through a multi-format card reader; card subsequently not presenting content on camera or computer |
| Reported situation | Card connected to a laptop through a multi-format reader · transfer in progress · host reporting the device was not ejected properly · card not working afterwards · camera reporting no images · photographs from a recent trip held |
| Fault class | Structure damage from an interrupted transfer — connection loss origin between reader and card to be distinguished; content unaffected |
| Equipment used | Card assessed on a direct reader rather than the original multi-format unit · imaged write-blocked (DeepSpar USB Stabilizer 10Gb) · structures reconstructed on the image from surviving copies · media validated by rendering |
The decode: what that message reports, and who probably caused it
What "not ejected properly" actually means: the device disappeared from the bus while the system still had it mounted. It is worded as though the user did something, and it appears just as often when the user did nothing at all — because from the system's position, a card pulled out and a connection dropped look identical.
Why a multi-format reader is worth suspecting: those units carry several slots, a controller handling all of them, and frequently the cheapest possible construction. Loose slot contacts, a marginal controller, or a poor solder joint on the USB connector will all produce exactly this — an intermittent drop under the sustained load of a transfer, at the worst possible moment. A card sitting in a slot with imperfect contact is being read through a connection that can interrupt itself.
Why that matters practically: if the reader dropped the connection, the card was healthy until that moment and its damage is purely the consequence of an interrupted write to its structures. That is a better position than a card that failed on its own, and it also means the reader should not be used again with anything valuable.
The test worth running before concluding anything, and it costs almost nothing: try the card in a different reader — ideally a single-slot one, or a camera's own connection. If it behaves differently, the reader was involved. Most people replace the card and keep the reader, which is precisely backwards if the reader is the weak component.
Why the camera now reports no images: the interrupted write left the filing structures inconsistent, and a camera is stricter than a computer about what it will accept. It reads the structures, cannot reconcile them, and reports nothing rather than showing a partial list. The photographs are untouched — a transfer was reading them, not replacing them.
What must not happen: no format, from either device. The camera will very likely offer one on the next power-up, and the computer will too.
The habit worth adopting: where a transfer matters, use a reader you trust, and verify the copy before the card leaves the bag. A cheap reader in the path is an unnecessary participant in something irreplaceable.
On the bench
The card was assessed on a direct reader rather than the original multi-format unit — those units carrying several slots through one controller with frequently marginal construction, so a dropped connection under sustained transfer load is as likely to originate there as in the card. It was imaged write-blocked behind the DeepSpar USB Stabilizer 10Gb, structures reconstructed on the image from their surviving copies, and media validated by rendering.
The outcome
The card assessed on a direct reader, imaged write-blocked and the structures rebuilt from their surviving copies. 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: that message means the device vanished from the bus while still mounted, and it appears just as often when nobody touched anything. A multi-format reader — several slots, one controller, cheap construction — is a common cause. Your photographs were being read, not replaced.
Card that failed during a transfer through a card reader
Try the card in a different reader before assuming the card is at fault — ideally a single-slot one or the camera's own connection. That "not ejected properly" message means the device disappeared from the bus while still mounted, and it's worded as though you did something when it appears just as often when nobody touched anything. Cheap multi-format readers are a common cause: several slots through one controller, often with marginal contacts or a poor solder joint, which drops the connection under the sustained load of a transfer. Most people replace the card and keep the reader, which is backwards. Meanwhile refuse every offer to format, from the camera and the computer both.
Try another reader first — then call Guildford Data Recovery on 01483 901310; assessed on a direct reader, imaged write-blocked, structures rebuilt from their surviving copies.
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.