On Sat, Jan 08, 2011 at 03:29:39PM +0000, Rosario Turco wrote:
> For a correct start of grub with i have compiled the kernel with the support
> of
> ext4 in menuconfig (when we do make LANG=<> LC_CALL= menuconfig).
>
> Now grub starts, I obtain many [OK] on video but then i obtain the error:
>
> 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>
>
>
> So from chroot i have done
> e2fsck -b 8193 <device>
> In my case <device> is /dev/sda2
>
> but i obtain with e2fsck the same error.
>
> What must i see?
> Thanks
>
_if_ you have made a filesystem as ext4, that nasty looking 'error'
is actually normal. I think it is normally followed (in my case) by
a similar message about ext3, before successfully mounting it as
ext4. Unfortunately, these error messages do not get logged so I
can't look back to see exactly what was reported in my case.
I think you need to check three things:
Is what now shows up as /dev/sda2 a valid filesystem ? If it isn't
your root ('/') fs then try commenting it out of the fstab until you
can get in and examine it.
If it is a valid filesystem, or if you think it is your rootfs,
what filesystem type did you use when you created it ? This will
allow you to ask yourself the third question:
Is that filesystem compiled into the kernel ? The ext2, ext3, and
ext4 filesystems are all individual configuration options
[ CONFIG_EXT{2,3,4}_FS ] - if in doubt, set all three of these to
'=y'.
If it isn't your root fs, try specifying 'auto' in your fstab.
ĸen
--
das eine Mal als Tragödie, das andere Mal als Farce
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
