Installations with multipath/LVM disks sometimes leaves the system in a non-bootable stage
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu on IBM z Systems |
Fix Released
|
Critical
|
Canonical Foundations Team | ||
subiquity |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
While doing some autoinstall tests on an IBM Z / s390x LPAR with FCP/SCSI strorage using multipath (multipath is mandatory in case of using FCP/SCSI) I ran from time to time int a problem where the system does not come up after the post-install reboot and hangs in busybox with the message:
"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)"
"ALERT! /dev/disk/
"SvdIFoSIyDIqQG
"BusyBox v1.30.1 (Ubuntu 1:1.30.
"Enter 'help' for a list of built-in commands."
"(initramfs) [6n"
"ls -l /dev/disk/
7nJ8lO*
"ls: /dev/disk/
"ch file or directory"
"(initramfs) [6n"
"cat /proc/cmdline"
root=/dev/
IFoSIyDIqQG2QpOSk
"(initramfs) [6n"
"ls -l /dev/disk/
7nJ8lOvIK1Svd
"ls: /dev/disk/
"No such file or directory"
"(initramfs) [6n"
"ls -l /dev/disk/
7nJ8lOvIK1Svd
"ls: /dev/disk/
"No such file or directory"
"(initramfs) [6n"
"ls -l /dev/disk/
"ls: /dev/disk/
"(initramfs) [6n"
"ls -l /dev/disk/by-id/"
"lrwxrwxrwx 1 10 wwn-0x600507630
"lrwxrwxrwx 1 10 dm-name-mpatha -> ../../dm-0"
"lrwxrwxrwx 1 10 dm-uuid-
../dm-0
"lrwxrwxrwx 1 10 scsi-3600507630
"lrwxrwxrwx 1 10 lvm-pv-
../../dm-2
"lrwxrwxrwx 1 10 wwn-0x600507630
dm-2
"lrwxrwxrwx 1 10 dm-uuid-
"-> ../../dm-2"
"lrwxrwxrwx 1 10 dm-name-
"lrwxrwxrwx 1 10 scsi-3600507630
dm-2
"lrwxrwxrwx 1 10 wwn-0x600507630
dm-1
"lrwxrwxrwx 1 10 dm-uuid-
"-> ../../dm-1"
"lrwxrwxrwx 1 10 dm-name-
"lrwxrwxrwx 1 10 scsi-3600507630
dm-1
"lrwxrwxrwx 1 9 scsi-SIBM_
"lrwxrwxrwx 1 10 scsi-SIBM_
"lrwxrwxrwx 1 10 scsi-SIBM_
"(initramfs) [6n"
dmsetup ls --tree -o nodevice
mpatha-part2
`-mpatha
mpatha-part1
`-mpatha
It happens in about one out of 4 cases:
1) failed with missing
ALERT! /dev/disk/
2) fine
3) fine
4) fine
5) failed with missing
ALERT! /dev/disk/
6) fine
7) fine
8) ALERT! /dev/disk/
ZEAEHwzpaaoQla3
9) fine
10) /dev/disk/
1mwq8nW0i5DewX1
(I always did exactly the same - just kicking of the autoinstall) on the exact same system with the same disks etc. - so it 'smells' like a race condition...)
I used the daily "19.1" 20.04.3 RC ISO, as referenced in the QA Tracker:
http://
description: | updated |
description: | updated |
summary: |
- autoinstall with multipath/LVM disks sometimes leaves the system in a + Installations with multipath/LVM disks sometimes leaves the system in a non-bootable stage |
Changed in ubuntu-z-systems: | |
importance: | Undecided → Critical |
Changed in subiquity: | |
status: | New → In Progress |
Changed in ubuntu-z-systems: | |
status: | New → In Progress |
Forgot to add that I didn't faced this issue on normal/interactive FCP installations (neither on z/VM nor on LPAR) - so far only when doing autoinstalls.
(And autoinstall using just DASDs seems to work fine.)