Pascal Kiehl wrote:
I used e2fsck -b 32769 /dev/hda4 and all worked well.
Many inodes corrupted, but after the fix I could mount my filesystem :-)
might be time for a new disk?
I don't really now... The reason is because I used my laptop and
sudently my hardrive was disconnected... I don't k
I used e2fsck -b 32769 /dev/hda4 and all worked well.
Many inodes corrupted, but after the fix I could mount my filesystem :-)
might be time for a new disk?
I don't really now... The reason is because I used my laptop and
sudently my hardrive was disconnected... I don't know if this it's
de
On Tue, 03 Jan 2006 23:19:28 +0100
Pascal Kiehl <[EMAIL PROTECTED]> wrote:
> > 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 th
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 cont
> 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
> i
[EMAIL PROTECTED] wrote:
> The problem is that I can't mount my root partition (which is /dev/hda4)
>
> [EMAIL PROTECTED] mount -t ext3 /dev/hda4 /mnt/hda4
> mount: wrong fs type, bad option, bad superblock on /dev/hda4,
>missing codepage or other error
>In some cases useful info i
6 matches
Mail list logo
