[Touch-packages] [Bug 1351528] Re: LVM based boot fails on degraded raid due to missing device tables at premount

** Summary changed: - 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 ** Summary changed: - LVM based boot fails on degraded raid due to missing device

[Touch-packages] [Bug 1351528] Re: boot fails on degraded raid (mdraid) due to LVM root (combined / + /boot) missing device tables at mount time

attached dmesg output for normal boot up to premount ** Attachment added: "dmesg_upto_premount_normal.txt" https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1351528/+attachment/4168674/+files/dmesg_upto_premount_normal.txt -- You received this bug notification because you are a member of

[Touch-packages] [Bug 1351528] Re: boot fails on degraded raid (mdraid) due to LVM root (combined / + /boot) missing device tables at mount time

The primary difference that I see for degraded boot is this error just ahead of activating volume group 'dataone' 'watershed sh -c '/sbin/lvm vgscan; /sbin/lvm vgchange -a y''(err) ' device-mapper: reload ioctl on failed: Invalid argument' and also after that point the 55-dm and 56-lvm rules d

[Touch-packages] [Bug 1351528] Re: boot fails on degraded raid (mdraid) due to LVM root (combined / + /boot) missing device tables at mount time

attached dmesg output for degraded boot up to premount ** Attachment added: "dmesg_upto_premount_degraded.txt" https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1351528/+attachment/4168673/+files/dmesg_upto_premount_degraded.txt -- You received this bug notification because you are a membe

[Touch-packages] [Bug 1351528] Re: boot fails on degraded raid (mdraid) due to LVM root (combined / + /boot) missing device tables at mount time

adding kernel parameter lvmwait=2 also works around this issue (source of idea http://serverfault.com/questions/567579/boot-failure-with-root-on-md-raid1-lvm-udev-event-timing) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to

[Touch-packages] [Bug 1351528] Re: boot fails on degraded raid (mdraid) due to LVM root (combined / + /boot) missing device tables at mount time

** Summary changed: - 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 -- You received this bug notification because you are a member of Ubuntu Touch seeded package

[Touch-packages] [Bug 1351528] Re: boot fails on raid (md raid1) + LVM (combined / + /boot) + degraded

here is an interesting find: replacing the missing disk (mdadm --add /dev/md0 /dev/sdb1) and waiting for sync to complete leads to proper booting system the system continued boot even after I --failed and --removed the second disk. I could not return the system to it's original boot fail state u

[Touch-packages] [Bug 1351528] [NEW] boot fails on raid (md raid1) + LVM (combined / + /boot) + degraded

Public bug reported: 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 wi