mount: wrong fs type, bad option, bad superblock on /dev/sda1
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.
mount: wrong fs type, bad option, bad superblock on /dev/sda1
I'm trying to mount a possibly corrupted memory chip from a camera so that I can save some vacation photos. I put the chip into a USB multi-card reader/writer and am getting the following error when I try to mount it:
mount -t vfat /dev/sda /mnt/sda
mount: wrong fs type, bad option, bad superblock on /dev/sda
I found a couple of other postings with similar problems. It was recommended to run fdisk on it. So I did and fdisk spits back this:
The number of cylinders for this disk is set to 4294.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Command (m for help):
If I print the partition table I get this:
Command (m for help): p
Disk /dev/sda: 2044 MB, 2044723200 bytes
31 heads, 30 sectors/track, 4294 cylinders
Units = cylinders of 930 * 512 = 476160 bytes
Device Boot Start End Blocks Id System
/dev/sda1 1 4295 1996676+ 6 FAT16
Command (m for help):
If I go to the expert menu and print the partition table I get this:
Expert command (m for help): p
Disk /dev/sda: 31 heads, 30 sectors, 4294 cylinders
Yeah shouldn't the mount command be: mount /dev/sda1 /mnt/sda you seem to be trying to mount the device rather than the partition on the device.. It should detect the file system automatically, I don't usually specify the filesystem when mounting a USB drive, or SD card..
mount: wrong fs type, bad option, bad superblock on /dev/sda1
Quote:
Originally Posted by rupertwh
Actually, your subject is correct. /dev/sda1 is the partition you want to mount. Not /dev/sda which is the whole disk.
Actually, I have tried mount -t vfat /dev/sda1 /dev/sda1 and
mount -t vfat /dev/sda /dev/sda1 and I get the same results - the error message in the subject line.
I meant "mount -t vfat /dev/sda1 /mnt/sda1" and yes, I created the directory in /dev before attempting to mount
Must be another typo. You probably meant that you created the directory in /mnt not /dev. I assume that what you mean by possibly corrupted is that the memory card will not work in the camera.
fdisk creates partitions but will not repair a filesystem. If it is indeed corrupted then you can try to repair using the command dosfsck. Check the man pages for additional information.
dosfsck -v /dev/sda1
I've never attempted to repair a DOS filesystem using dosfsck and do not know how well it works. You might want to make a copy of the partition first just in case.
dd if=/dev/sda1 of=/somewhere/camera.img
Must be another typo. You probably meant that you created the directory in /mnt not /dev. I assume that what you mean by possibly corrupted is that the memory card will not work in the camera.
fdisk creates partitions but will not repair a filesystem. If it is indeed corrupted then you can try to repair using the command dosfsck. Check the man pages for additional information.
dosfsck -v /dev/sda1
I've never attempted to repair a DOS filesystem using dosfsck and do not know how well it works. You might want to make a copy of the partition first just in case.
dd if=/dev/sda1 of=/somewhere/camera.img
Michaelk
Yes, another typo. I did mean /mnt rather than /dev.
I did copy the data from the chip to a camera.img file in my home filesystem using your command. I will read the manpage for dosfsck and see what I can do to repair the filesystem. Thanks! This is what I wanted to do in the first place - save the data from the chip and try and repair things. Can I use dosfsck on the camera.img file I created or do I need to use it on the chip?
Looks like the filesystem is corrupted. Either the filesystem has been corrupted or the chip has failed. As the error message stated here should only be two File Allocation Tables not 255 so basically dosfsck did not know what to do.
Might want to try using a windows recovery program to see if it can rebuild the FAT.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.