Home / Case Studies / Cameras, Drones & Cards
Cameras, Drones & Cards · case file

The Reader Ejected, and Now the Card Is Unreadable

Her photos were right there, and then they weren't. She inserted an SD card through a reader on her Mac — "the photos were there but then the reader ejected without me shutting down" — and now the card is "not showing at all", unreadable, "no longer reading on my camera when it was before". The Mac tells her to format it, and her instinct is sharp: "I'm worried that will wipe it completely". An unclean ejection mid-read corrupted the card's filesystem, and the format prompt she is being offered is exactly the action that would turn a recoverable card into an empty one — her worry is correct, and declining is the right call.

Memory CardCamera / DroneCorruption / Filesystem
// case at a glance
MediaSD card ejected uncleanly from a Mac card reader mid-access — now unreadable on both the Mac and the camera that read it before, photographs the target
Reported situationCard inserted via a reader, photos initially visible · reader ejected without a proper unmount · card now not showing on the Mac at all · card also unreadable in the camera, which read it previously · macOS prompting to format the card · owner reluctant to format for fear of total loss
Fault classFilesystem corruption from an interrupted read/mount on flash media — the card's structures damaged so no device can mount it, with the photo data expected intact behind them
Equipment usedCard imaged under a hardware write-blocker before any interpretation, and never formatted · filesystem structures parsed from the image in R-Studio, FAT/exFAT backup copies located and compared · signature carving in PhotoRec for images the damaged structure no longer references · card's own health checked, since a failing card can corrupt the same way · recovered photographs validated by rendering and returned to fresh media
// the decode

The decode

Pulling a card mid-access is precisely when its filesystem breaks. Reading or mounting a card involves the device updating and relying on its structural records, and an ejection at that moment leaves those records half-processed and inconsistent. That the reader ejected without a proper unmount is the mechanism exactly: the card was in use when it was cut off, and the interrupted operation corrupted the bookkeeping every device needs to mount it.

Unreadable on both the Mac and the camera confirms it is the card, not the reader. If only the Mac struggled, a reader or port fault might be blamed. But the camera that happily read the card before now cannot either — which points the fault at the card's own structures rather than any one device. The corruption travels with the card, because it is on the card.

Her fear of formatting is well-founded, and it is the crucial instinct. The Mac offers to format because it cannot read the filesystem — the same reason a drive shows as RAW. Accepting would write fresh, empty structures over the card, burying the recoverable photos under a real format. Her reluctance is exactly right: formatting is the one action that converts this recoverable situation into a genuine loss, and it must be declined on every device that offers it.

The photos are almost certainly still there, behind damaged structures. Filesystem corruption damages the small records describing where files live, not usually the much larger area holding the files themselves. The images sit intact and unreferenced, waiting for tools that read past the broken structures. Recovery rebuilds those structures from their backup copies where possible — returning photos organised — and carves the data area by signature for anything the damaged records no longer reach.

Everything happens on an image, which protects a card in a fragile state. The card is imaged once under write-blocking and all work done on the copy, so no recovery attempt writes to a card whose structures are already damaged — and nothing forecloses a second approach. Repair utilities run directly on the card invert this, writing to the patient in the hope of fixing it.

The card's own health is checked, because the cause matters for what comes next. Most such corruption is purely from the ejection, but a failing card can produce the same symptom. The card is assessed at the outset, and if it is genuinely failing, that shapes both the imaging and the honest advice — recover the photos, then retire the card. Either way the prognosis for the images is good, and it is stated before the work.

// on the bench

On the bench

The card was imaged under a hardware write-blocker before anything interpreted it, and never formatted. Filesystem structures were parsed from the image in R-Studio, the FAT/exFAT backup copies located and compared, and PhotoRec carving run for images the damaged structure no longer referenced. The card's own health was checked for an underlying fault, and the recovered photographs validated by rendering and returned to fresh media.

// the outcome

The outcome

Card imaged rather than formatted, structures rebuilt from their backup copies, the data area carved for the rest, and the photos returned. The assessment is free and the quote is a single fixed figure inclusive of VAT; if the data cannot be recovered, there is nothing to pay. The decode: the ejection broke the card's filesystem, and formatting — exactly what your Mac suggested — would have finished the job. You were right to refuse. Your photos sit intact behind the damage, and rebuilt from the card's own backup structures, they come back.

A card that became unreadable and is asking to be formatted

Don't format it — on any device — no matter how insistently the prompt appears; that writes empty structures over photos that are still there. Stop inserting it repeatedly to check, and don't run repair utilities that write to the card. An unclean ejection usually corrupts the filesystem while leaving the images intact behind it, so the card simply needs recovery from an image. Your instinct to refuse the format was exactly the right one — keep the card untouched until it can be imaged.

Sending this in from Staines? Every case starts with a free diagnostic and one fixed written quote before any work — no fix, no fee. If the data is inside a laptop, PC, Mac or server, remove the hard drive or SSD and send us just the drive; we don’t provide an internal drive-removal service, and we don’t recover storage soldered to a motherboard (e.g. Apple Silicon Macs) — only drives that can be removed and sent to us. Post or courier tracked and insured to our Guildford Data Recovery lab — full sending instructions and the shipping form are here.
Start a free diagnostic

Our case files are written up from genuine enquiries our lab has handled for customers across Staines, Surrey and the surrounding area, anonymised to protect client confidentiality. Each one describes the diagnostic and recovery approach our engineers apply to that fault, using the equipment listed.

// related case files

More cases like this one

Browse all case studies →

Got a device with a story like this?

Free diagnostic, fixed quote, no fix no fee — start now or call the freephone.