SD Card Unmounted Itself and Now Asks to Format: What Should You Do?
Do not format it, and do not keep scanning the original card if you can avoid it. In this r/datarecovery case, a work microSD card used in a DJI Osmo Pocket 3 was readable moments earlier, then unmounted itself while connected to a computer. After that, the camera, two computers, and an iPhone all wanted to format the card, while Disk Drill was still slowly finding files. That means the card is not completely inaccessible, but it has already shown instability.
Protect the Source
Do not format the card, run CHKDSK or First Aid, shoot new footage, or save recovered files back to it. The priority is to preserve the readable sectors that are still available.
Why Can Recovery Software See Files When Devices Want to Format the Card?
A format prompt does not automatically mean the files were erased. It can mean the operating system can still see the storage device but can no longer mount its current file system normally. Recovery software can scan below the normal folder view, which is why Disk Drill may still identify files even when the camera or computer refuses to open the card.
Should You Let Disk Drill Keep Scanning the Original Card?
Because this card already unmounted itself unexpectedly, the safer move is to stop treating the original as a normal healthy card. Disk Drill itself recommends creating a byte-to-byte backup when possible and performing later recovery work from that image instead of repeatedly reading the source. You can use its Byte-to-byte Backup feature, or follow the same imaging principle described in this byte-to-byte backup guide.
Choose the Next Path
- The card stays connected and the image completes: stop working on the original. Scan the image, preview the important files, and recover them to another healthy drive.
- The imaging process stalls, the card disappears again, or read errors increase: stop DIY recovery. Repeated reads can make an unstable card harder to recover, especially when the work files matter.
- The card later mounts normally: do not assume it is healthy again. Copy or image the data immediately, then retire or replace the card after the files are safe.
Do You Need to Know Exactly What Failed First?
No. The exact cause could be file-system corruption, controller or flash instability, or another storage fault, and you do not need to prove which one occurred before protecting the data. For this situation, the important fact is already known: the card has behaved unstably but is still readable enough for low-level scanning. Preserve that readable state first; diagnose or reformat only after the files are safe.