------- Comment From [email protected] 2021-01-14 04:48 EDT------- Thanks! I remember that the system was installed on a single path. Later on, more paths were added. And no initramfs was rebuilt. I think that's the case. Is there any procedure for Ubuntu to deal with such case for boot LVM device? Thanks!
(In reply to comment #15) > Do you remember what happened just prior to the reboot - have you been > upgrading the system with a new kernel and/or updated packages? > (Btw. the kernel 4.15.0-91 is a bit outdated, current is 4.15.0-124.) > There's maybe a file /etc/lvm/lvm.conf.dpkg-dist available from a previous > upgrade. > > Or have you added more or changed FCP or iSCSI disks to the system, that may > have let to a name clash or device (path) discovery order issues? > And was the initramfs rebuild? > > Such an issue can also happen due to temporarily unavailable paths or > devices, and there seem to be some of them in that system. > Do you have LUN masking (zoning) in your SAN in place, so that the host can > only see the LUNs it's supported to see? > > Btw. I think in your filter rule you also want to accept the sd* (SCSI/FCP) > devices, so: > filter = [ "a|/dev/sd*|", "a|/dev/mapper/mpath*|", "r|.*|" ] > and you may add the same as global filter: > global_filter = [ "a|/dev/sd*|", "a|/dev/mapper/mpath*|", "r|.*|" ] > for system level scans. > According to the logs the system seems to expect '/dev/mapper/ISVCL1--vg', > so looks you have LVM on top of multipath? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906384 Title: [UBUNTU 18.04] lvm boot failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1906384/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
