SD Card, no read, bad superblock, no response - read on phone
Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
SD Card, no read, bad superblock, no response - read on phone
Hello there,
I have an SD card that is mainly used in the phone. Unfortunately it has problems with it, I could not copy anything to it. Nevertheless, I was able to paste items from the card into the phone and start exploring it.
I can't access it from GParted. Below is the result of some commands used.
Code:
$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
mmcblk0 179:0 0 28.9G 0 disk
└─mmcblk0p1 179:1 0 28.9G 0 part
$ sudo fdisk -l
Device Boot Start End Sectors Size Id Type
/dev/mmcblk0p1 8192 60506111 60497920 28.9G c W95 FAT32 (LBA)
$ sudo mount /dev/mmcblk0 /mnt/SD-Ruf
mount: /mnt/SD-Ruf: wrong fs type, bad option, bad superblock on /dev/mmcblk0, missing codepage or helper program, or other error.
$ sudo fsck /dev/mmcblk0
fsck from util-linux 2.33.1
e2fsck 1.44.5 (15-Dec-2018)
/dev/mmcblk0 is in use.
e2fsck: Cannot continue, aborting.
$ sudo mkfs.ext4 /dev/mmcblk0
mke2fs 1.44.5 (15-Dec-2018)
Found a dos partition table in /dev/mmcblk0
Proceed anyway? (y,N) y
/dev/mmcblk0 is apparently in use by the system; will not make a filesystem here!
$ sudo dmraid -r
no block devices found
$ sudo mdadm --stop /dev/mmcblk0
mdadm: /dev/mmcblk0 does not appear to be an md device
$ sudo mount /dev/mmcblk0 /mnt/SD-Ruf
mount: /mnt/SD-Ruf: /dev/mmcblk0 already mounted or mount point busy.
/dev/mmcblk0 is the entire device. The beginning contains the MBR which is the partition table.
The device contains 1 partition /dev/mmcblk0p1. This is where the filesystem is located and all the data. To access the data you need to mount partition 1.
All the commands you posted with errors were using the wrong device ID.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.