if multilib-support is deactivated lvm and device-mapper fail to start. /etc/init.d/lvm start * Caching service dependencies ... [ ok ] * The lvm init-script is written for baselayout-2! * Please do not use it with baselayout-1!. * ERROR: lvm failed to start emerge --info Portage 2.1.4.4 (default/linux/amd64/2008.0/no-multilib, gcc-4.2.4, glibc-2.7-r2, 2.6.25-gentoo-r4 x86_64) ================================================================= System uname: 2.6.25-gentoo-r4 x86_64 AMD Athlon(tm) Dual Core Processor 4450e Timestamp of tree: Tue, 03 Jun 2008 11:15:01 +0000 app-shells/bash: 3.2_p33 dev-lang/python: 2.4.4-r13 dev-python/pycrypto: 2.0.1-r6 sys-apps/baselayout: 2.0.0 sys-apps/openrc: 0.2.5 sys-apps/sandbox: 1.2.18.1-r2 sys-devel/autoconf: 2.61-r1 sys-devel/automake: 1.10.1 sys-devel/binutils: 2.18-r1 sys-devel/gcc-config: 1.4.0-r4 sys-devel/libtool: 1.5.26 virtual/os-headers: 2.6.23-r3 ACCEPT_KEYWORDS="amd64" CBUILD="x86_64-pc-linux-gnu" CFLAGS="-O2 -march=athlon64 -pipe -fomit-frame-pointer" CHOST="x86_64-pc-linux-gnu" lvm seems to check for /lib/librc.so /etc/init.d/lvm: [..] start() { if [ ! -e /lib/librc.so ]; then eerror "The $SVCNAME init-script is written for baselayout-2!" eerror "Please do not use it with baselayout-1!". return 1 fi [..] but it's located in /lib64 ls -la /lib64/librc.so lrwxrwxrwx 1 root root 10 2008-06-03 22:19 /lib64/librc.so -> librc.so.1 Reproducible: Always Steps to Reproduce: 1. use no-multilib profile with baselayout 2 2. emerge -N world and reboot 3. start lvm Actual Results: /etc/init.d/lvm start * Caching service dependencies ... [ ok ] * The lvm init-script is written for baselayout-2! * Please do not use it with baselayout-1!. * ERROR: lvm failed to start Expected Results: /etc/init.d/lvm start * Caching service dependencies ... [ ok ] * Setting up the Logical Volume Manager ... [ ok ]
(unrelated, but regressions have been found in upstream lvm2 2.02.36 and I'm not recommending people use it except on test systems)
Your /lib should be a symlink to /lib64. If it's not then your system is broken. We have to check /lib simply because it's the only relable way for all platforms.
(In reply to comment #2) maybe this is a bug in gentoo baselayout or do i have to do this symlink on my own? the only content inside of /lib is the folder 'grub'.
glua: all the gentoo stage tarballs ship with a symlink from /lib to /lib64.
(In reply to comment #4) > glua: all the gentoo stage tarballs ship with a symlink from /lib to /lib64. i tested it with 2008 beta2 amd64 stage 3 tarball, you're right, the symlink is there. maybe it's a problem of grub-static (because the only content in this folder is grub/i386-pc)
(In reply to comment #5) > i tested it with 2008 beta2 amd64 stage 3 tarball, you're right, the symlink is > there. maybe it's a problem of grub-static (because the only content in this > folder is grub/i386-pc) Don't guess, test it and report back :)
