[Bug 147216] Re: System with LVM root filesystem won't boot
I'll confirm this bug. I'm running an LVM2 volume of 2 drives, just for media. They work fine when started manually, but the /dev/mapper items aren't there when fsck checks during boot. In other works, similar to Martin, except I didn't have the nifty workaround. -- System with LVM root filesystem won't boot https://bugs.launchpad.net/bugs/147216 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 147216] Re: System with LVM root filesystem won't boot
This seems to be the bug that's most similar to my own experience. In my case, a Feisty box was upgraded to Gutsy (network upgrade about a week ago), using, because I am old-fashioned, apt-get dist-upgrade. Unlike most (any?) of the other reports, I do NOT use LVM for the root partition (which includes /boot; /usr, /var, /tmp, /home and swap are in LVs), so after some poking I discovered that at the time checkfs.sh was being called the volumes, both physical and logical, were known to the LVM system (eg., pvs and lvs showed everything as it should be), but they had no entries in /dev/mapper. Typing just "vgchange -a y" at the shell prompt, then control-D to resume, completed the boot normally (but without ever running fsck, of course). I'm currently using a modified checkfs.sh, with the vgchange command added to the start) case before do_start, and that seems to workaround the issues for me. Oh, using the Feisty kernel and initfs never did work for me. It's possible that that initfs had been rebuilt, either during the upgrade or during my early thrashing about, and that that somehow confused it. I was able to get the Gutsy image working largely because I had a completely separate image to boot into. BTW, I have another machine that had a similar root=/dev/sda#, rest in LVM setup that got a fresh Gutsy install rather than upgrade (it was running Dapper), which has never had the least trouble with LVM. I've spent some time tryign to find the key difference between them, but so far no luck. -- System with LVM root filesystem won't boot https://bugs.launchpad.net/bugs/147216 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 147216] Re: System with LVM root filesystem won't boot
Basically I suspect that the udev events that are supposed to be getting
triggered duing the boot process in the initramfs are not getting
triggered, hence a vgscan is never done. My guess is based on the
contents of :
[EMAIL PROTECTED]:/etc/udev/rules.d$ cat 85-lvm2.rules
# This file causes block devices with LVM signatures to be automatically
# added to their volume group.
# See udev(8) for syntax
SUBSYSTEM=="block", ACTION=="add|change", ENV{ID_FS_TYPE}=="lvm*|LVM*", \
RUN+="watershed sh -c '/sbin/lvm vgscan; /sbin/lvm vgchange -a y'"
here's the output of pvdisplay
[EMAIL PROTECTED]:/etc/udev/rules.d# pvdisplay
--- Physical volume ---
PV Name /dev/md0
VG Name vg0
PV Size 362,49 GB / not usable 1,25 MB
Allocatable yes (but full)
PE Size (KByte) 4096
Total PE 92797
Free PE 0
Allocated PE 92797
PV UUID OoPCI9-1Lj3-0eU7-3dbE-dLIz-0AKz-sjcJMz
--- Physical volume ---
PV Name /dev/md1
VG Name vg0
PV Size 9,54 GB / not usable 1,81 MB
Allocatable yes (but full)
PE Size (KByte) 4096
Total PE 2443
Free PE 0
Allocated PE 2443
PV UUID 5SndoF-iOPs-kGpy-WQzl-S0BJ-wydK-PSaOC6
--
System with LVM root filesystem won't boot
https://bugs.launchpad.net/bugs/147216
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
