Re: can't mount my root partition (rescue mode)

[kiehl@nerim.net]

> Did you try 'dmesg | tail' like it suggested?
EXT3-fs: hda4: couldn't mount because of unsupported optional features
(2000200).

> Usually if you can't mount a filesystem it's because it got corrupted
> somehow,
> in this case it might be a "bad superblock" like it says.  dmesg will
> provide
> info on exactly why the mount is failing.  If you haven't done so, try
> using
> '-t auto' or not using -t at all.
Right, it's maybe because it's corrupted. I was succesfully able to mount
my second /dev/hda5 filesystem, using previously fsck.ext3 /dev/hda5 :-)

But fsck.ext3 doesn't work on /dev/hda4 :-(. I got this error message :
fsck.ext3 file system revision too high while trying to open /dev/hda4.
The file system is appalently too high for this version of e2fsck (or the
filesystem superblock is corrupt).

The superblock could not be read or does not contain a correct ext2 file
system. If the device is valid and it really contains an ext2 filesystem
then the superblock is corrupt and you might try running e2fsck with an
alternate superblock. "e2fsck -b 8193 <device>"

So I tried e2fsck -b 8193 /dev/hda4 and I got again this message :
fsck.ext3 file system revision too high while trying to open /dev/hda4.
The file system is appalently too high for this version of e2fsck (or the
filesystem superblock is corrupt).

The superblock could not be read or does not contain a correct ext2 file
system. If the device is valid and it really contains an ext2 filesystem
then the superblock is corrupt and you might try running e2fsck with an
alternate superblock. "e2fsck -b 8193 <device>"

So what can I do ?

   Pascal
--
root@3[knoppix]# file -s /dev/hda4
/dev/hda4: Linux rev 33554945.512 ext3 filesystem data (needs journal
recovery)