mount: wrong fs type, bad option, bad superblock on /dev/sda1
UbuntuThis forum is for the discussion of Ubuntu 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 a novice Linux guy with a big problem. I've been using a second hard drive in a Dell Latitude system running Ubuntu Natty (11.04) as my primary OS. On the second Hard Drive formatted as ext4, I hold all of the disk images needed by VirtualBox to run the various VMs that i use daily.
I recently got a new Windows 7 64-bit machine and wanted to use the VMs on that system. I installed the drive as a second HD in my windows system, and when it didn't recognize the drive, I went to the Disk Management App and chose to bring the drive "online". This allowed windows to see the drive, but not access it. Thinking I might be screwed, I installed the drive back into my ubuntu system so that I could move all the files off it, format the disk for windows, and then move them back.
When I try to mount the drive in ubuntu I get the subject error message. Am I screwed? I really need the data on that drive!!
1. Dell Latitude system running Ubuntu Natty. I am assuming Ubuntu is running on first hdd.
2. Second hdd on the same system formatted as ext4 which holds your VM images.
3. New machine runs Windows and you tried to put the second hdd of your Ubuntu machine to Windows machine.
4. When it didnt work you put it back on, on Ubuntu machine.
5. Now, second hdd partition is not mounting on Ubuntu. Is that the case?
If yes then here are the questions for you:
1. Did you tried to do anything when you brough that disk online on Windows?
2. How you are trying to mount the partition? Let us know the command you are using?
3. Did you try to run fsck on the partition and then tried to mount it?
4. Any other changes.
Your recap of my scenario is correct. When it was in the windows machine, besides bringing it online (which made it show as available in Win Explorer), I attempted to open it and received a message indicating that the drive was inaccessible and needed to be formatted. I did not choose to format the disk, and then proceeded down the path of re-installing the drive into the ubuntu machine.
There is no command I'm using to mount the drive. the drive shows in Nautilus file explorer and by double clicking on it, the system attempts the mount. this is the procedure that I've been using since I started using this setup.
This is the output for "sudo fsck /dev/sda1"
fsck from util-linux-ng 2.17.2
e2fsck 1.41.14 (22-Dec-2010)
fsck.ext2: Superblock invalid, trying backup blocks...
fsck.ext2: Bad magic number in super-block while trying to open /dev/sda1
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
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>
sudo fsck.ext4 /dev/sda1
e2fsck 1.41.14 (22-Dec-2010)
fsck.ext4: Superblock invalid, trying backup blocks...
fsck.ext4: Bad magic number in super-block while trying to open /dev/sda1
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
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>
mount: wrong fs type, bad option, bad superblock on /dev/sda1,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
Are you sure that /dev/sda1 was formatted as ext4?
Run the following command as that might help us in finding the filesystem on /dev/sda
Code:
sudo parted -l
I am surprised that /var/log/messages file is not there. As it is there in my Ubuntu 10.04. Never tried 11.04 so not sure if they do have this file on 11.04 or not.
I'm fairly sure it was ext4, although i'm not certain now that there seems to be some doubt? That is what I remember, but again that ext4 doesn't really mean anything to me, so i can't say i'm certain. Besides if it were fat32 or something, woudn't it have just worked in Windows? Sorry if that is a dumb question...
Here is the output you asked for...
sudo parted -l
Model: ATA WDC WD5000BEKT-7 (scsi)
Disk /dev/sda: 500GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 1049kB 500GB 500GB primary
Model: ATA INTEL SSDSA2M040 (scsi)
Disk /dev/sdb: 40.0GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 1049kB 35.7GB 35.7GB primary ext4 boot
2 35.7GB 40.0GB 4291MB extended
5 35.7GB 40.0GB 4291MB logical linux-swap(v1)
Model: WD My Passport 0730 (scsi)
Disk /dev/sdc: 750GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 1049kB 750GB 750GB primary ntfs
I would try the following commands to trying mounting the partition:
1.
Code:
mount -t vfat /dev/sda1 /mnt
2.
Code:
mount -t msdos /dev/sda1 /mnt
Not sure about the msdos command because never tried that before. As far as I know Windows 7 does not support FAT file system so that might be the case that it didnt recognize.
sudo mount -t vfat /dev/sda1 /mnt
mount: wrong fs type, bad option, bad superblock on /dev/sda1,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
sudo mount -t msdos /dev/sda1 /mnt
mount: wrong fs type, bad option, bad superblock on /dev/sda1,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
Thanks for your thoughts so far. Any other ideas? I really need to fix this. I've loaded testdisk and started messing around with it, but it's like a foreign language to me right now
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.