Public bug reported:

---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|.*|" ]

** Affects: linux (Ubuntu)
     Importance: Undecided
     Assignee: Skipper Bug Screeners (skipper-screen-team)
         Status: New


** Tags: architecture-s39064 bugnameltc-189833 severity-medium 
targetmilestone-inin---

** Tags added: architecture-s39064 bugnameltc-189833 severity-medium
targetmilestone-inin---

-- 
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/+source/linux/+bug/1906384/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to