A travel photographer in Melbourne plugged her Micro SD(TF) card into a MacBook Pro after a three-week shoot in New Zealand — 128 GB of landscapes, timelapses and a once-in-a-trip drone session she’d already copied to some of it. Instead of the usual Finder window, macOS greeted her with the dreaded dialog: “The disk you inserted was not readable by this computer.” Three buttons: Initialize…, Ignore, Eject.
The problem
This dialog means macOS cannot mount the card’s file system — the card’s partition table or file allocation structures are damaged, so the Mac literally cannot figure out where files begin and end. It happens after unsafe ejection mid-write, a card reader glitch, or simply flash wear catching up at the worst moment.
The trap is that Initialize looks like the “helpful” button — it opens Disk Utility, where the obvious next step is Erase. Initializing doesn’t just “fix” the card; it writes a fresh file system over the damaged one. It usually won’t destroy your data immediately, but it makes recovery harder and, in some cases, erases critical metadata that a clean recovery would have used. She did the smart thing: clicked Eject, pulled the card, and messaged us the same evening.
What we did
- She made a sector-by-sector disk image of the card at home using Disk Utility on MAC.
- We parsed the raw image and rebuilt the damaged exFAT file system structures from their remnants, restoring the original directory tree.
- Where directory entries were too damaged to reconstruct, we fell back to signature carving — scanning the raw flash for known video, RAW and JPEG file signatures.
- Reassembled fragmented MP4 timelapses and revalidated every recovered file’s structure before delivery.
- Sent her a browsable preview list: 1,642 files recoverable and playable.
✓ Result
1,642 files recovered — all photos, the complete drone session and 8 timelapses at full original quality. Turnaround: 2 days from upload to download link.
What the Eject / Ignore / Initialize dialog actually means
Think of an SD card as a book: the pages (your data) and the table of contents (the file system). macOS reads the table of contents to know where each chapter starts. When that table is torn — corrupted metadata — the Mac can’t open the book at all, and asks whether you want to rip out the old contents page and write a blank one (Initialize), skip the book (Ignore), or put it back on the shelf (Eject).
The pages themselves are usually still intact. That’s why the correct answer to this dialog is almost always Eject — it changes nothing on the card and preserves the scene exactly as it is for professional recovery. “Ignore” is harmless but leaves the card mounted-but-broken, which invites accidental writes; some apps will happily write to a card they can’t read properly.
Takeaways
- See “not readable” with Initialize / Ignore / Eject? Click Eject and stop there. Never Initialize a card you want files back from.
- Don’t re-insert it into the camera and shoot “just a few more” — new recordings overwrite the data you’re trying to save.
- Disk Utility’s First Aid is safe to run (it attempts read-only repair), but if it fails, stop — repeated repair attempts can worsen directory damage.
- Always eject cards in the camera or via Finder before pulling them; 90% of these cases start with an unsafe removal during a write.
- Some recovered clips won’t play perfectly after this kind of damage? That’s normal — we repair the recovered videos as part of the same case.