esfsck error on boot

Kevin Lyles kevinlyles at comcast.net
Mon Feb 28 00:02:00 PST 2005


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I figured it'd be something like that.  So, should I compile that while
booting from my rescue disk, and just chroot into my LFS partition?

Kevin

Steve Crosby wrote:
| Kevin Lyles <kevinlyles at comcast.net> wrote in news:4222869E.30604
| @comcast.net:
|
|
|>-----BEGIN PGP SIGNED MESSAGE-----
|>Hash: SHA1
|>
|>Hello all,
|>
|>I get an error from e2fsck every time I boot into my (brand new) LFS
|>partition:
|>
|>     Mounting root file system in read-only mode             [  OK  ]
|>     Checking file systems...
|>     fsck.ext3: Filesystem has unsupported feature(s) (/dev/hda7)
|>     e2fsck: Get a newer version of e2fsck!
|>     File system errors were encountered that couldn't be
|>     fixed automatically.  This system cannot continue to boot
|
|
| <snip>
|
|>As far as I can tell, the version of e2fsck on the LFS partition and on
|>my FC3 partition (which was the host for the LFS build) are identical;
|>1.35.  I can mount, unmount, and run e2fsck on /dev/hda7 from FC3 and
|>the rescued CD I have without problems or errors detected.  I used nALFS
|
|
| Although FC3 reports the version as 1.35, they have actually applied some
| patches that add new functionality not supported by the stock LFS
| e2fsprogs. The *safest* way to fix this is to update your LFS parition to
| e2fsprogs 1.36, which has the FC3 extensions included.
|
| -- -
| Steve Crosby
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFCIs/40Fe8dbVCDxARAvxgAJ9tzq61A5QNeHUgopcRg/HYiT9vcwCbBhgX
UHpIrCqRZsACpmkLbmFx4NE=
=BvDk
-----END PGP SIGNATURE-----



More information about the lfs-support mailing list