[Bug 1051354] New: "zypper up" after installing 42.3 causes boot to fail (dracut-initqueue timeout due to missing LVM devices)
http://bugzilla.opensuse.org/show_bug.cgi?id=1051354 Bug ID: 1051354 Summary: "zypper up" after installing 42.3 causes boot to fail (dracut-initqueue timeout due to missing LVM devices) Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.3 Hardware: x86-64 OS: openSUSE 42.3 Status: NEW Severity: Critical Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening@forge.provo.novell.com Reporter: rebecca@bluestop.org QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- After installing Leap 42.3 I ran "zypper up" and got the following updates (there are a few others, but aren't relevant): The following 10 packages are going to be upgraded: dracut 044-21.7 -> 044.1-23.2 libsystemd0 228-27.2 -> 228-29.1 libsystemd0-32bit 228-27.2 -> 228-29.1 libudev1 228-27.2 -> 228-29.1 systemd 228-27.2 -> 228-29.1 systemd-32bit 228-27.2 -> 228-29.1 systemd-bash-completion 228-27.2 -> 228-29.1 systemd-logger 228-27.2 -> 228-29.1 systemd-sysvinit 228-27.2 -> 228-29.1 udev 228-27.2 -> 228-29.1 There's something in there that causes the next boot to fail due to dracut-initqueue not being able to find /dev/mapper/system-root. Looking at /dev/mapper the only file in there is 'control'. Running "lvm_scan" causes the volumes to be found and /sys-root to be mounted. The install is on a single 4TB SATA disk with 3 LVM volumes: system-root (Btrfs), system-swap and system-home (xfs). -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1051354
http://bugzilla.opensuse.org/show_bug.cgi?id=1051354#c1
Andreas Stieger
http://bugzilla.opensuse.org/show_bug.cgi?id=1051354
Rebecca Cran
http://bugzilla.opensuse.org/show_bug.cgi?id=1051354
François Valenduc
http://bugzilla.opensuse.org/show_bug.cgi?id=1051354
http://bugzilla.opensuse.org/show_bug.cgi?id=1051354#c4
--- Comment #4 from François Valenduc
http://bugzilla.opensuse.org/show_bug.cgi?id=1051354
http://bugzilla.opensuse.org/show_bug.cgi?id=1051354#c5
--- Comment #5 from Andreas Stieger
http://bugzilla.opensuse.org/show_bug.cgi?id=1051354
http://bugzilla.opensuse.org/show_bug.cgi?id=1051354#c28
Richard Weinberger
http://bugzilla.opensuse.org/show_bug.cgi?id=1051354
http://bugzilla.opensuse.org/show_bug.cgi?id=1051354#c29
--- Comment #29 from Richard Weinberger
Adding these lines doesn't change anything. In fact, the disk and the partition are detected. The problem is rather that the LVM volumes are not found.
In my case the difference between working and bad initrd is: diff -Nur good/usr/lib/udev/rules.d/61-persistent-storage-compat.rules bad/usr/lib/udev/rules.d/61-persistent-storage-compat.rules --- good/usr/lib/udev/rules.d/61-persistent-storage-compat.rules 2017-08-20 20:58:53.723996905 +0200 +++ bad/usr/lib/udev/rules.d/61-persistent-storage-compat.rules 2017-08-20 20:59:04.775996863 +0200 @@ -37,10 +37,11 @@ # NVMe links were introduced first via a SUSE specific commit # (bsc#944132) and upstream gained support later but of course using a -# different scheme. -KERNEL=="nvme*", ENV{DEVTYPE}=="disk", ENV{ID_SERIAL}!="?*", IMPORT{program}="scsi_id --export --whitelisted -d $tempnode", ENV{ID_BUS}="nvme" -KERNEL=="nvme*", ENV{DEVTYPE}=="disk", ENV{ID_SERIAL}=="?*", SYMLINK+="disk/by-id/$env{ID_BUS}-$env{ID_SERIAL}" -KERNEL=="nvme*", ENV{DEVTYPE}=="partition", ENV{ID_SERIAL}=="?*", SYMLINK+="disk/by-id/$env{ID_BUS}-$env{ID_SERIAL}-part%n" +# different scheme. Also note that ID_SERIAL is already used by the +# contemporary rules, see bsc#1048679 for details. +KERNEL=="nvme*", ENV{DEVTYPE}=="disk", ENV{ID_NVME_SERIAL_COMPAT}!="?*", PROGRAM="scsi_id --whitelisted --replace-whitespace -d $devnode", RESULT=="?*", ENV{ID_NVME_SERIAL_COMPAT}="$result" +KERNEL=="nvme*", ENV{DEVTYPE}=="disk", ENV{ID_NVME_SERIAL_COMPAT}=="?*", SYMLINK+="disk/by-id/nvme-$env{ID_NVME_SERIAL_COMPAT}" +KERNEL=="nvme*", ENV{DEVTYPE}=="partition", ENV{ID_NVME_SERIAL_COMPAT}=="?*", SYMLINK+="disk/by-id/nvme-$env{ID_NVME_SERIAL_COMPAT}-part%n" # SCSI compat links for ATA devices, removed by f6ba1a468cea (boo#769002) KERNEL=="sd*[!0-9]", ENV{ID_BUS}=="ata", PROGRAM="scsi_id --whitelisted --replace-whitespace -p0x80 -d $devnode", RESULT=="?*", ENV{ID_SCSI_COMPAT}="$result", SYMLINK+="disk/by-id/scsi-$env{ID_SCSI_COMPAT}" So, Lee might be correct. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1051354
Kresten P. Vester
http://bugzilla.opensuse.org/show_bug.cgi?id=1051354
http://bugzilla.opensuse.org/show_bug.cgi?id=1051354#c38
--- Comment #38 from François Valenduc
http://bugzilla.opensuse.org/show_bug.cgi?id=1051354
http://bugzilla.opensuse.org/show_bug.cgi?id=1051354#c39
--- Comment #39 from François Valenduc
http://bugzilla.opensuse.org/show_bug.cgi?id=1051354
François Valenduc
http://bugzilla.opensuse.org/show_bug.cgi?id=1051354
http://bugzilla.opensuse.org/show_bug.cgi?id=1051354#c41
--- Comment #41 from François Valenduc
http://bugzilla.opensuse.org/show_bug.cgi?id=1051354
http://bugzilla.opensuse.org/show_bug.cgi?id=1051354#c43
--- Comment #43 from François Valenduc
http://bugzilla.opensuse.org/show_bug.cgi?id=1051354
http://bugzilla.opensuse.org/show_bug.cgi?id=1051354#c45
--- Comment #45 from François Valenduc
http://bugzilla.opensuse.org/show_bug.cgi?id=1051354
http://bugzilla.opensuse.org/show_bug.cgi?id=1051354#c47
--- Comment #47 from François Valenduc
http://bugzilla.opensuse.org/show_bug.cgi?id=1051354
http://bugzilla.opensuse.org/show_bug.cgi?id=1051354#c48
--- Comment #48 from François Valenduc
http://bugzilla.opensuse.org/show_bug.cgi?id=1051354
http://bugzilla.opensuse.org/show_bug.cgi?id=1051354#c49
--- Comment #49 from François Valenduc
http://bugzilla.opensuse.org/show_bug.cgi?id=1051354
http://bugzilla.opensuse.org/show_bug.cgi?id=1051354#c59
François Valenduc
participants (1)
-
bugzilla_noreply@novell.com