Public bug reported: Binary package hint: lvm2
Having the root filesystem on LVM fails to boot on current feisty. I am not sure this is a duplicate of either #85617 or #83832. 85617 could be a bootloader misconfiguration and 83832 involves LVM on RAID. What happens: During boot, the system hangs for a couple of minutes and then presents a BusyBox with the only error message being "/bin/sh: can't access tty; job control turned off", which doesn't seem to be related to the problem at hand. At this point there are no lvm devices under /dev. When I do 'lvm vgscan' followed by 'lvm vgchange -ay; exit' the boot process continues as expected and everything is working fine. (Currently I mount usually with 'break=mount' appended to grub's kernel line to circumvent the several minutes long timeout) More details: My root filesystem is on a simple LVM on an IDE harddisc. The bootline from grub's menu.lst is /vmlinuz-2.6.20-8-generic root=/dev/mapper/main_vg-root_lv quiet splash and the rootfs line in /etc/fstab is /dev/mapper/main_vg-root_lv / ext3 noatime,user_xattr,errors=remount-ro 0 1 The problem started 2 or 3 weeks ago. I am sorry that I didn't tracked down which new packages caused this. ** Affects: lvm2 (Ubuntu) Importance: Undecided Status: Unconfirmed -- Root fs on LVM fails to boot https://launchpad.net/bugs/87745 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs