You are not logged in.
Pages: 1
Topic closed
Hi,
I am not able to mount my SD card anymore. It's a SD card I use in my camera to take pics and there are some pics I don't want to lose on it.
» sudo mount /dev/mmcblk0p1 /mnt/leatmp 8 ↵
mount: wrong fs type, bad option, bad superblock on /dev/mmcblk0p1,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so.\» sudo fsck /dev/mmcblk0 8 ↵
fsck from util-linux 2.24.2
e2fsck 1.42.10 (18-May-2014)
ext2fs_open2: Bad magic number in super-block
fsck.ext2: Superblock invalid, trying backup blocks...
fsck.ext2: Bad magic number in super-block while trying to open /dev/mmcblk0
The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem. If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
or
e2fsck -b 32768 <device>What can I do? ![]()
water vapor is invisible
Offline
Bonjour,
Look at the messages in 'dmesg' concerning the SD card after you plugged it in.
fsck takes a file system argument like mount; surely 'dev/mmcblk0' is not one.
What is the file system type on the SD card?
Do you have an entry for it in '/etc/fstab'?
Offline
Bonjour berbae ![]()
(I put the fsck result without knowing what the program was really doing, thought it could help. apparently it doesn't ^^)
here is the result of dmesg when I plug it in:
[24874.131902] mmc0: new high speed SDHC card at address b368
[24874.132125] mmcblk0: mmc0:b368 NCard 7.46 GiB
[24874.133074] mmcblk0: p1fdisk -l:
» sudo fdisk /dev/mmcblk0 -l 1 ↵
Disk /dev/mmcblk0: 7.5 GiB, 8018460672 bytes, 15661056 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/mmcblk0p1 8192 15661055 7826432 b W95 FAT32lsblk:
» lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 465.8G 0 disk
├─sda1 8:1 0 1007K 0 part
├─sda2 8:2 0 20G 0 part /
├─sda3 8:3 0 300M 0 part /boot
├─sda4 8:4 0 12G 0 part /var
├─sda5 8:5 0 300G 0 part /home
├─sda6 8:6 0 16G 0 part [SWAP]
└─sda7 8:7 0 117.5G 0 part
sdb 8:16 0 111.8G 0 disk
├─sdb1 8:17 0 100M 0 part
└─sdb2 8:18 0 111.7G 0 part
mmcblk0 179:0 0 7.5G 0 disk
└─mmcblk0p1 179:1 0 7.5G 0 part water vapor is invisible
Offline
The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem. If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:I believe this. Most cameras don't use ext file systems. Mayhaps if you mounted it as fat32?
Edit: Actually, the -t switch for mount is vfat
Last edited by ewaller (2014-07-28 17:33:49)
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way
Offline
Run lsblk --fs to display filesystem info.
But whether the Constitution really be one thing, or another, this much is certain - that it has either authorized such a government as we have had, or has been powerless to prevent it. In either case, it is unfit to exist.
-Lysander Spooner
Offline
@alphaniner: lsblk --fs doesn't give me any information about my /dev/mmcblk0p1:
» lsblk --fs
NAME FSTYPE LABEL UUID MOUNTPOINT
sda
├─sda1
├─sda2 ext4 0fdbf91c-fda9-4cf6-8ca0-212a41e2b5cf /
├─sda3 ext2 3777d412-3607-4309-8de6-ffd8fbf5ab05 /boot
├─sda4 ext4 47130517-c2d6-479c-ba4c-dbbf931a579f /var
├─sda5 ext4 82fdf3db-5045-44e5-82fa-67bbb1a26d74 /home
├─sda6 swap 6d91e1c4-0d3e-48b0-8d53-88f96d575cbb [SWAP]
└─sda7
sdb
├─sdb1 ntfs System Reserved B6208E21208DE927
└─sdb2 ntfs 6210917410915041
mmcblk0
└─mmcblk0p1mount -t vfat:
» sudo mount -t vfat /dev/mmcblk0p1 /mnt/leatmp
mount: wrong fs type, bad option, bad superblock on /dev/mmcblk0p1,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so.@firecat53: yup I rebooted after recent kernel upgrade. Actually my sister tried to mount it on her macbook and it didn't work, that's why I'm trying manually on arch.
thank you all for your replies. If anyone has any idea about how I could retrieve these pics... (pics of my sister's trip to Lahos and Birmania, beautiful ones, would be sad to lose them)
water vapor is invisible
Offline
Before you do anything, copy the entire sdcard, not just the partition to a file with dd.
Offline
Have a look at photorec.
https://wiki.archlinux.org/index.php/File_recovery
Last edited by Slithery (2014-07-28 20:58:52)
Offline
@Awebb: done ![]()
water vapor is invisible
Offline
Look to the package TestDisk https://www.archlinux.org/packages/extr … /testdisk/
Offline
maybe you forgot to make the fs?
mkfs.ext4 /dev/mmcblk0p1 #exactly like when you installed arch-linux
lsblk --fs #now must show a ext4 fs in the partition 1
try to mount it
Offline
The thread is 5 years old. Please don't necrobump.
Offline
Indeed. Closing.
Offline
Pages: 1
Topic closed