------- Comment From [email protected] 2016-02-03 19:24 EDT------- Hi @mathieu-tl,
As we just talked on IRC, the multipathd -B patches did not help here. I'm pasting the comments about that (sorry, I forgot to mark those as external). [reply] [-] Comment 13 Mauricio Faria De Oliveira 2016-01-25 10:39:23 BRST Hi Manju, (In reply to comment #12) > Installed the suggested packages and rebooted the lpar, issue still occurs: Thanks for verifying. Can I check the LPAR? <...> [reply] [-] Comment 17 Mauricio Faria De Oliveira 2016-01-25 15:55:04 BRST Hm, guess I got it. This differs slightly from the other bug. It seems that the async discovery of LVM and multipath devices is not well serialized, causing some inconsistencies with the access to the partitions (e.g., /boot). Checking a bit more. <...> [reply] [-] Comment 19 Mauricio Faria De Oliveira 2016-01-25 17:55:23 BRST The problem matches the suspicion: the LVM detection is happening before multipathd grabs the individual paths, and then the creation of the multipath map /dev/mapper/mpath0 fails, then /boot fails to mount as it's specified as /dev/mapper/mpath0-part2 in /etc/fstab: -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1540401 Title: ISST-LTE: Ubuntu14.04.4 lpar fails to boot after installation: "The disk drive for /boot is not ready yet or not present" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1540401/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
