MicroSD - disconnects after reading bad block

Using TestDisk to undelete files
Forum rules
When asking for technical support:
- Search for posts on the same topic before posting a new question.
- Give clear, specific information in the title of your post.
- Include as many details as you can, MOST POSTS WILL GET ONLY ONE OR TWO ANSWERS.
- Post a follow up with a "Thank you" or "This worked!"
- When you learn something, use that knowledge to HELP ANOTHER USER LATER.
Before posting, please read https://www.cgsecurity.org/testdisk.pdf
User avatar
Posts: 1
Joined: 24 Jun 2015, 16:08
Location: Severn, MD USA

MicroSD - disconnects after reading bad block

#1 Post by pquesinb »

I'm trying to recover photos and a couple of movie files which suddenly disappeared from an 8GB Kingston MicroSD card being used in a smartphone (Samsung Galaxy S5). I'm noticing the following behavior:

Data may be read from the card until you hit a bad block, then it's like the card is disconnected, no more data can be read until I physically unmount and remount the card in the card reader. Right now I'm attempting the recovery using a Windows machine but I may switch over to a Linux machine to see if I can pull the data off the card with dd without being disconnected.

Does this behavior make sense to anyone? is this the Windows OS or driver, the card reader (also Kingston), or could this be happening in the card itself?


- Phil

User avatar
Site Admin
Posts: 5432
Joined: 18 Feb 2012, 15:08
Location: Le Perreux Sur Marne, France

Re: MicroSD - disconnects after reading bad block

#2 Post by cgrenier »

Yes, disconnection happens sometimes when there are bad blocks/bad memory areas for device connected via USB.
Instead of using dd to copy the memory card, use ddrescue (ie "ddrescue /dev/sdb sdb.dd sdb.log"). Using the log file, ddrescue should be able to resume the recovery even if the disk is disconnected.