Hi Jean-Marc, > Do you follow the installation guide from gentoo.org?
There are several documents on Gentoo website. I followed 2 documents: Partitioning HD with LVM Gentoo LVM2 installation http://www.gentoo.org/doc/en/lvm2.xml Installation Gentoo Linux AMD64 Handbook http://www.gentoo.org/doc/en/handbook/handbook-amd64.xml > I mean, do you use a > "standard" scheme? I made some adjustment for my case. I did not emerge LVM2. If fail again. I'll run a final test according their HD config (w/o slave), not running LVM. B.R. SL > > > On 9/5/06, Stephen Liu <[EMAIL PROTECTED]> wrote: > > > > Hi Neil, > > > > > /usr/src contains the source to the kernel (as you'd expect form > the > > > name). The actual kernels live in /boot, this is the version that > > > must > > > match. > > > > Gentoo started booting after changing following line; > > kernel (hd0,0)/boot/kernel-2.6.17-gentoo-r7 root=/dev/hda2 > > to > > kernel (hd0,0)/boot/linux-2.6.17-gentoo-r7 root=/dev/hda2 > > > > But still having following problems; > > > > > > 1) > > Engine: Unable to open the engine block file /var/lock/evms-engine > : > > Read only filesystem. The engine is not protected against other > > instances of the Engine being opened at the same time. Error > returned > > from evms_commit_changes ( ) : No such device [!!] > > > > > > 2) > > Loading module 3c59x .... > > Failed to load 3c59x [!!] > > > > > > 3) > > All > > /dev/vg/usr > > /dev/vg/home > > /dev/vg/opt > > /dev/vg/var > > /dev/vg/tmp > > > > have same problem as listed follow; > > e2fsck: No such file or directory which trying to open /dev/vg/usr. > > The super block 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). There the > > superblock is corrupt, and your might trying e2fsck with an > alternative > > superblock : > > e2fsck -b 8193 > > > > # e2fsck -b 8193 /dev/vg/usr > > fsck.ext3: No such file or directory while trying to open > /dev/vg/usr > > > > Please advise how to fix them. TIA > > > > B.R. > > SL > > -- > > [email protected] mailing list > > > > > > > -- > /JM > -- [email protected] mailing list
