acrane1
April 24th, 2008, 08:26 PM
I recently installed another Hard drive on my computer. I am running Ubuntu Gusty. the hard drive was working fine except for the fact that it would not auto mount after reboot and mount have to remount. The hard drive is an internal 500gb western digital formated to extended ext3 with a single partition. My friend who is much more knowledgeable with linux than me tried to fix the auto mount problem. what i think he did was mount it using the command mount -a -o auto. now after restart i am getting this warning message when i try to mount the drive since it is still not auto mounting.
The waring i got was cannot mount volume.
details
mount:wrong fs type, bad option, bad superblock on /dev/sdb5, missing codepage or header program, or other error. In some cases useful info is found in syslog -try dmesg | tail or so
I typed in dmesg | tail and got
[ 33.200000] hda-intel: Invalid position buffer, using LPIB read method instead.
[ 46.496000] eth0: no IPv6 routers present
[ 74.540000] JBD: Clearing recovery information on journal
[ 77.796000] kjournald starting. Commit interval 5 seconds
[ 77.796000] EXT3-fs warning: mounting fs with errors, running e2fsck is recommended
[ 77.800000] EXT3 FS on sdd1, internal journal
[ 77.800000] EXT3-fs: mounted filesystem with ordered data mode.
[ 107.664000] EXT2-fs: sdb5: couldn't mount because of unsupported optional features (4).
[ 147.380000] EXT2-fs: sdb5: couldn't mount because of unsupported optional features (4).
[ 538.704000] EXT2-fs: sdb5: couldn't mount because of unsupported optional features (4).
I've got no idea how to fix it any ideas???
The waring i got was cannot mount volume.
details
mount:wrong fs type, bad option, bad superblock on /dev/sdb5, missing codepage or header program, or other error. In some cases useful info is found in syslog -try dmesg | tail or so
I typed in dmesg | tail and got
[ 33.200000] hda-intel: Invalid position buffer, using LPIB read method instead.
[ 46.496000] eth0: no IPv6 routers present
[ 74.540000] JBD: Clearing recovery information on journal
[ 77.796000] kjournald starting. Commit interval 5 seconds
[ 77.796000] EXT3-fs warning: mounting fs with errors, running e2fsck is recommended
[ 77.800000] EXT3 FS on sdd1, internal journal
[ 77.800000] EXT3-fs: mounted filesystem with ordered data mode.
[ 107.664000] EXT2-fs: sdb5: couldn't mount because of unsupported optional features (4).
[ 147.380000] EXT2-fs: sdb5: couldn't mount because of unsupported optional features (4).
[ 538.704000] EXT2-fs: sdb5: couldn't mount because of unsupported optional features (4).
I've got no idea how to fix it any ideas???