------- Comment From y...@cn.ibm.com 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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1906384 Title: [UBUNTU 18.04] lvm boot failure Status in Ubuntu on IBM z Systems: Incomplete Status in linux package in Ubuntu: New Bug description: ---Problem Description--- boot failure with LVM root disk ---uname output--- 4.15.0-91-generic #92-Ubuntu SMP Fri Feb 28 11:07:52 UTC 2020 s390x s390x s390x GNU/Linux Machine Type = 8561 LT1 ---System Hang--- Boot failure with LVM root disk and enter emergency shell ---Debugger--- A debugger is not configured ---Steps to Reproduce--- boot the system *Additional Instructions for Chee Ye/y...@cn.ibm.com: -Attach: /proc/partitions /proc/mounts/ /etc/lvm/lvm.conf dmsetup ls dmsetup table dmsetup targets dmsetup version lvm version During boot, got below error message and then entered emergency shell. I am attaching part of the console log from HMC. "WARNING: PV UbKGJN-sLdU-PeZu-p2hF-ca1W-Gd74-WUISRc prefers device /dev/sdah be" "cause device was seen first." "WARNING: PV UbKGJN-sLdU-PeZu-p2hF-ca1W-Gd74-WUISRc prefers device /dev/sdah be" "cause device was seen first." "WARNING: PV UbKGJN-sLdU-PeZu-p2hF-ca1W-Gd74-WUISRc prefers device /dev/sdah be" "cause device was seen first." "WARNING: PV 3wBaLS-TaW1-IJAI-Akmo-k90H-uT6G-j7XEX3 prefers device /dev/sdh5 be" "cause device was seen first." "WARNING: PV 3wBaLS-TaW1-IJAI-Akmo-k90H-uT6G-j7XEX3 prefers device /dev/sdh5 be" "cause device was seen first." "WARNING: PV 3wBaLS-TaW1-IJAI-Akmo-k90H-uT6G-j7XEX3 prefers device /dev/sdh5 be" "cause device was seen first." "WARNING: PV Ksjsai-Hw03-r9x9-n2Kv-4tqe-GyP9-qVWc2c prefers device /dev/sdcn be" "cause device was seen first." "WARNING: PV Ksjsai-Hw03-r9x9-n2Kv-4tqe-GyP9-qVWc2c prefers device /dev/sdcn be" "cause device was seen first." "WARNING: PV Ksjsai-Hw03-r9x9-n2Kv-4tqe-GyP9-qVWc2c prefers device /dev/sdcn be" "cause device was seen first." "Cannot activate LVs in VG ISVCL1-vg while PVs appear on duplicate devices." done. "mdadm: No arrays found in config file or automatically" "mdadm: No arrays found in config file or automatically" "mdadm: No arrays found in config file or automatically" "mdadm: No arrays found in config file or automatically" "mdadm: No arrays found in config file or automatically" "mdadm: No arrays found in config file or automatically" "mdadm: No arrays found in config file or automatically" "mdadm: No arrays found in config file or automatically" "mdadm: No arrays found in config file or automatically" "mdadm: No arrays found in config file or automatically" "mdadm: No arrays found in config file or automatically" "mdadm: No arrays found in config file or automatically" "mdadm: No arrays found in config file or automatically" "mdadm: No arrays found in config file or automatically" "mdadm: No arrays found in config file or automatically" "mdadm: No arrays found in config file or automatically" "mdadm: No arrays found in config file or automatically" "mdadm: No arrays found in config file or automatically" "mdadm: No arrays found in config file or automatically" "mdadm: error opening /dev/md?*: No such file or directory" "mdadm: No arrays found in config file or automatically" "mdadm: No arrays found in config file or automatically" "mdadm: No arrays found in config file or automatically" "mdadm: No arrays found in config file or automatically" "mdadm: No arrays found in config file or automatically" "mdadm: No arrays found in config file or automatically" "mdadm: No arrays found in config file or automatically" "mdadm: No arrays found in config file or automatically" "mdadm: No arrays found in config file or automatically" "mdadm: No arrays found in config file or automatically" "mdadm: No arrays found in config file or automatically" done. "Gave up waiting for root file system device. Common problems:" "- Boot args (cat /proc/cmdline)" "- Check rootdelay= (did the system wait long enough?)" "- Missing modules (cat /proc/modules; ls /dev)" "chvt: can't open console" "ALERT! /dev/mapper/ISVCL1--vg-root does not exist. Dropping to a shell!" "Couldn't get a file descriptor referring to the console" "/scripts/panic/console_setup: line 133: can't create /dev/tty1: No such device o" "r address" "/scripts/panic/console_setup: line 1: can't open /dev/tty1: No such device or ad" dress "/scripts/panic/console_setup: line 1: can't create /dev/tty2: No such device or" address "/scripts/panic/console_setup: line 1: can't open /dev/tty2: No such device or ad" dress "/scripts/panic/console_setup: line 1: can't create /dev/tty3: No such device or" address "/scripts/panic/console_setup: line 1: can't open /dev/tty3: No such device or ad" dress "/scripts/panic/console_setup: line 1: can't create /dev/tty4: No such device or" address "/scripts/panic/console_setup: line 1: can't open /dev/tty4: No such device or ad" dress "/scripts/panic/console_setup: line 1: can't create /dev/tty5: No such device or" address "/scripts/panic/console_setup: line 1: can't open /dev/tty5: No such device or ad" dress "/scripts/panic/console_setup: line 1: can't create /dev/tty6: No such device or" address "/scripts/panic/console_setup: line 1: can't open /dev/tty6: No such device or ad" dress "BusyBox v1.27.2 (Ubuntu 1:1.27.2-2ubuntu3.2) built-in shell (ash)" "Enter 'help' for a list of built-in commands." "(initramfs) [6n" console-log during boot lvm.conf file Attached the lvm.conf file. Also tried to add filter in the lvm.conf as below. But still failed to boot. filter = [ "a|/dev/mapper/mpath.*|", "r|.*|" ] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1906384/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
