When I try to boot using the kernel gentoo-sources 2.4.19-r10 in a system 1.4_rc2 with LVM partitions, the kernel hangs trying to mount root device, while a vanilla-sources 2.4.20 works properly. Reproducible: Always Steps to Reproduce: 1. Install the system using 1.4_rc2 boot cd 2. Create a volume group name diskvg 3. Create an LVM root filesystem 4. Compile the gentoo-sources 2.4.19-r10 kernel 5. reboot the system Actual Results: I have a volume group nemed diskvg and some logical volumes named rootlv, usrlv, varlv, tmplv and homelv. Follow the last boot messages: Mounted devfs on /dev vgscan -- readinf all physical volumes vgscan -- found inactive volume group "diskvg" vgscan -- "/etc/lvmtab" and "/etc/lvmtab.d" succesfully created vgscan -- WARNING: This program does not do a VGDA backup of your volume group vgchange -- volume group "diskvg" succesfully activated VFS: Cannot open root device "diskvg/rootlv" or 00:0d Please append a correct "root=" boot option kernel panic: VFS: Unable to mount root fs on 00:0d Expected Results: Should boots. The system is an Athlon 750MHz with 256MB RAM on an ASUS K7M, 40GB HDD IDE, CDD, FDD, ATI RAGE 128. Boot CD gentoo-grp-athlon-1.4_rc2.iso. The partitions are ReiserFS except the boot partition (ext3, no LVM). I tryed to boot after the first installation and after an emerge -u system with the same results.
This doesn't look like the same problem, but it is similar to the one I'm having. I've had LVM running under Gentoo for a while, very reliably. After a recent upgrade (emerge world), my system won't boot. I suspect that the init sequence is fscked. I played with it a bit, but haven't had time to fix it yet. However: The first signs of the problem is a message saying: /sbin/rc: line 256: /var/state/init.d/softlevel: No such file or directory /var on my system is an LVM mounted partition. Also, when the root partition is mounted read-only, vgscan can't work, because it can't rewrite lvmtab or enable a group. The next message I get is: install: cannot create directory '/var/state': Read-only file system * ERROR: runlevel sysinit does not exist; exiting... It then goes into the services sequence, and halts after "devfsd" with: * For Gentoo Linux to function properly, "/var/state/init.d" need to exist. * Please mount your root partition read/write, and execute: * # mkdir -p /var/state/init.d I can get the VG enabled and access the system with the following commands: mount -o remount,rw / vgscan vgchange -a y bean mount -a However, on reboot, it repeats the error. I *suspect* that the problem is that the root partition is being mounted read-only, although the fstab doesn't say so. I expect I'll have this fixed before I hear back from the bug trackers; if so, I'll describe my fix, but I won't be able to reproduce the problem. Since I'm guessing at which versions you may need: baselayout = 1.8.5.8 lvm-user = 1.0.6 kernel = 2.4.20-gentoo-r1 (although, that kernel has been working for a while. I think the problem occurred after a baselayout upgrade, but I'm not sure... there have been several emerges since the last reboot.)
Forget it. My own stupidity. I ran that last emerge overnight and forgot to do an etc-update :-/ Everything works. Mia culpa.
reopen if needed
