Guest xodeus Posted June 7, 2007 Report Share Posted June 7, 2007 Hi there. I've recently changed from ubuntu to mandriva just to try the desktop out... But I can't mount my ext3 partition. I know it is an ext3. Here's the old line from fstab I've tried with: /dev/sdb1 /media/Shared ext3 rw,user,noauto 0 0 and yes I've the /media/Shared dir. Then I tried to do it manually: [root@suedox mariusz]# mount -t ext3 /dev/sdb1 /media/ext3/ mount: wrong fs type, bad option, bad superblock on /dev/sdb1, missing codepage or other error In some cases useful info is found in syslog - try dmesg | tail or so and the dmesg | tail: VFS: Can't find ext3 filesystem on dev sdb1. The partition editor/configurator in mandrake says that it's hfsplus, but I've never been using this kind of fstype, and I know that last used fs was ext3. I've a lot of backup data there so I hope I can be able to mount it or recover the data... Quote Link to comment Share on other sites More sharing options...
ianw1974 Posted June 7, 2007 Report Share Posted June 7, 2007 Try just mounting it with: mount /dev/sdb1 /media/ext3 and see if that works any better. Once done, just type mount on it's own, and see what properties it assigned for this device. You will then find out if it is actually ext3 or not. Mounting as I've just shown will or should automatically detect the file system. Quote Link to comment Share on other sites More sharing options...
Guest xodeus Posted June 7, 2007 Report Share Posted June 7, 2007 But it's funny, as I cant do it. [root@suedox mariusz]# mount /dev/sdb1 /media/ext3/ mount: you must specify the filesystem type [root@suedox mariusz]# Quote Link to comment Share on other sites More sharing options...
Mhn Posted June 7, 2007 Report Share Posted June 7, 2007 What says # fdisk -l about the partition? Quote Link to comment Share on other sites More sharing options...
Guest xodeus Posted June 7, 2007 Report Share Posted June 7, 2007 Disk /dev/sdb: 122.9 GB, 122942324736 bytes 255 heads, 63 sectors/track, 14946 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/sdb1 * 1 14946 120053713+ 83 Linux And yes I'm sure that it is ext3. [root@suedox mariusz]# fsck.ext3 /dev/sdb1 e2fsck 1.39 (29-May-2006) Couldn't find ext2 superblock, trying backup blocks... fsck.ext3: Bad magic number in super-block while trying to open /dev/sdb1 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> Quote Link to comment Share on other sites More sharing options...
pmpatrick Posted June 8, 2007 Report Share Posted June 8, 2007 The filesystem on sdb1 is probably corrupt or at least mandriva thinks it is. Have you had any hard shutdowns with sdb1 mounted? You may want to try a livecd and see if sdb1 can be read from there. If you have the same issue with a live cd, you know the filesystem on sdb1 is corrupted. Here's an article which goes into recovering data on a corrupted ext2/3 filesystem: http://aniraj.blogspot.com/2006/05/data-re...-corrupted.html It goes into the technique of using dd to make an image of the corrupted partition and working on that instead as well as mounting on backup superblocks. Quote Link to comment Share on other sites More sharing options...
ianw1974 Posted June 11, 2007 Report Share Posted June 11, 2007 The superblock could not be read or does not describe a correct ext2filesystem. 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>[/code] Did you do what it says on the last line? e2fsck -b 8193 /dev/sdb1 you have to fix the superblock if it's corrupt, else you're not gonna get anywhere. If that doesn't work, look at pmpatricks solution in case you can try to recover the data. Otherwise...... Quote Link to comment Share on other sites More sharing options...
Roberto Oropeza Posted May 29, 2008 Report Share Posted May 29, 2008 (edited) WAIT, wait, wait... it just happened almost the same thing to me and I solved it this way: I've just changed some info in my fstab, when the problem arose, these are the lines: This is my /etc/fstab When I couldn't mount my /dev/hdb8: (with the same message about the magic number and super-block as yours) /dev/hdb5 / ext3 relatime 1 1 /dev/hdb8 /home ext3 relatime 1 2 /dev/cdrom /media/cdrom auto umask=0022,users,iocharset=utf8,noauto,ro,exec 0 0 /dev/fd0 /media/floppy auto umask=0022,users,iocharset=utf8,noauto,exec,flush 0 0 /dev/hda1 /mnt/win_c vfat umask=0,iocharset=utf8 0 0 /dev/hdb3 /mnt/win_k ntfs umask=0022,nls=utf8,ro 0 0 /dev/hda5 /mnt/win_d vfat umask=0,iocharset=utf8 0 0 /dev/hdb6 /mnt/win_j ntfs umask=0022,nls=utf8,ro 0 0 /dev/hda6 /mnt/win_e vfat umask=0,iocharset=utf8 0 0 /dev/hda7 /mnt/win_f vfat umask=0,iocharset=utf8 0 0 none /proc proc defaults 0 0 /dev/hdb7 swap swap defaults 0 0 /dev/sda1 /media/hd vfat umask=0022,users,iocharset=utf8,sync,noauto,exec 0 0 I've swaped /dev/hdb7 info with /dev/hdb8 info, like this /dev/hdb5 / ext3 relatime 1 1 /dev/hdb8 swap swap defaults 0 0 /dev/cdrom /media/cdrom auto umask=0022,users,iocharset=utf8,noauto,ro,exec 0 0 /dev/fd0 /media/floppy auto umask=0022,users,iocharset=utf8,noauto,exec,flush 0 0 /dev/hda1 /mnt/win_c vfat umask=0,iocharset=utf8 0 0 /dev/hdb3 /mnt/win_k ntfs umask=0022,nls=utf8,ro 0 0 /dev/hda5 /mnt/win_d vfat umask=0,iocharset=utf8 0 0 /dev/hdb6 /mnt/win_j ntfs umask=0022,nls=utf8,ro 0 0 /dev/hda6 /mnt/win_e vfat umask=0,iocharset=utf8 0 0 /dev/hda7 /mnt/win_f vfat umask=0,iocharset=utf8 0 0 none /proc proc defaults 0 0 /dev/hdb7 /home ext3 relatime 1 2 /dev/sda1 /media/hd vfat umask=0022,users,iocharset=utf8,sync,noauto,exec 0 0 and the problem is almost solved, I can see all my linux drives from linux, the only problem is that I can't mount my /dev/hdb6 (/mnt/win_j) but it it's a Windoze disk that I can use and see from windows, I'll try to fix this when I can. Edited May 29, 2008 by Roberto Oropeza Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.