Activity log for bug #1351528

Date Who What changed Old value New value Message
2014-08-02 01:27:07 uxeng bug added bug
2014-08-02 01:29:22 uxeng affects cryptsetup (Ubuntu) lvm2 (Ubuntu)
2014-08-02 13:46:20 uxeng summary boot fails on raid (md raid1) + LVM (combined / + /boot) + degraded boot fails on degraded raid (mdraid) due to LVM root (combined / + /boot) missing device tables at mount time
2014-08-03 13:24:34 uxeng attachment added dmesg_upto_premount_degraded.txt https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1351528/+attachment/4168673/+files/dmesg_upto_premount_degraded.txt
2014-08-03 13:29:40 uxeng attachment added dmesg_upto_premount_normal.txt https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1351528/+attachment/4168674/+files/dmesg_upto_premount_normal.txt
2014-08-04 22:39:14 uxeng summary boot fails on degraded raid (mdraid) due to LVM root (combined / + /boot) missing device tables at mount time LVM based boot fails on degraded raid due to missing device tables at premount
2014-08-04 22:40:18 uxeng summary LVM based boot fails on degraded raid due to missing device tables at premount boot fails for LVM on degraded raid due to missing device tables at premount
2014-08-04 22:43:16 uxeng description Trusty installation is combined root + /boot within LVM on top of mdraid (type 1.x) RAID1 with one missing disk (degraded). [method: basically create the setup in shell first then point install at the lvm. at end of install create a chroot and add mdadm pkg] boot fails with the following messages: Incrementally starting RAID arrays... mdadm: CREATE user root not found mdadm: CREATE group disk not found Incrementally starting RAID arrays... and slowly repeats the above at this point. workaround: - add break=premount to grub kernel line entry - for continue visibility of boot output also remove quiet, splash and possibly set gxmode 640x480 now @ initramfs prompt: mdadm --detail /dev/md0 should indicate a state of clean, degraded, array is started so this part is ok lvm lvs output attributes are as follows: -wi-d---- (instead of the expected -wi-a----) lvs manpage this means device tables are missing (device mapper?) FIX: simply run lvm vgchange -ay and exit initramsfs. This will lead to a booting system. This is a Trusty installation with combined root + /boot within LVM on top of mdraid (type 1.x) RAID1. Raid1 was built with one missing disk (degraded). [method: basically create raid/VG/LV setup in shell first then point installer at the lvm. At the end of the install create a chroot, add the mdadm pkg, and update-initramfs before reboot.] The boot process fails with the following messages:  Incrementally starting RAID arrays...  mdadm: CREATE user root not found  mdadm: CREATE group disk not found  Incrementally starting RAID arrays... and slowly repeats the above at this point. workaround: - add break=premount to grub kernel line entry - for continued visibility of text boot output also remove quiet, splash and possibly set gxmode 640x480 now @ initramfs prompt: mdadm --detail /dev/md0 should indicate a state of clean, degraded, array is started so this part is ok lvm lvs output attributes are as follows: -wi-d---- (instead of the expected -wi-a----) lvs manpage this means device tables are missing (device mapper?) FIX: simply run lvm vgchange -ay and exit initramsfs. This will lead to a booting system.
2014-11-12 21:37:40 Launchpad Janitor lvm2 (Ubuntu): status New Confirmed
2014-11-13 12:16:01 Mark Thornton bug added subscriber Mark Thornton
2015-08-07 14:55:36 Raulo bug added subscriber Sven Ehret