lfs65 at cruziero.com
Wed Dec 9 07:58:16 PST 2009
20091209: mathan kumar <newindian2005 at gmail.com> wrote:
> When i boot my BLFS i got the following error and i cant go further. Once i
> press enter key the system gets powered off.
> "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> "
I got exactly this on a recent LFS-6.5 build. Turns out the host system
(Slackware 13.0) was naming hard-disk devices/partitions as /dev/hda,
/dev/hda1, ..., /dev/hda4, etc. Whereas the newly-compiled LFS kernel,
was calling the same devices/partitions as /dev/sda, /dev/sda1, ...,
I gather/guess that the converse can happen: i.e. your host sytem
uses '/dev/sda...' naming system, and your newly-compiled LFS-kernel
is looking for 'dev/hda', etc; depends on your kernel config.
As is the way of these things, the problem you're getting may of
course be due to something else. But, hth ...
More information about the lfs-support