[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 <astieger@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |astieger@suse.com, | |daniel.molkentin@suse.com, | |systemd-maintainers@suse.de Assignee|bnc-team-screening@forge.pr |daniel.molkentin@suse.com |ovo.novell.com | --- Comment #1 from Andreas Stieger <astieger@suse.com> --- Trying dracut maintainers, cc'ing systemd maintainers. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1051354 Rebecca Cran <rebecca@bluestop.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rebecca@bluestop.org -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1051354 François Valenduc <francoisvalenduc@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |francoisvalenduc@gmail.com -- 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#c4 --- Comment #4 from François Valenduc <francoisvalenduc@gmail.com> --- I have also the same problem. Applying the 2 patches from bug 1051465 doesn't solve the problem, so my system is still unbootable. For me this is the perfect definition of a blocking problem. -- 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#c5 --- Comment #5 from Andreas Stieger <astieger@suse.com> --- just documenting the work-around / downgrade: zypper in --oldpackage ` \ zypper info -t patch --conflicts openSUSE-2017-847 | \ grep " < " | while read NAME C VERSION; do \ rpm --quiet -q --queryformat "%{name}\n" $NAME && echo "${NAME}<${VERSION}"; \ done` zypper al -t patch openSUSE-2017-847 -- 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#c28 Richard Weinberger <richard@nod.at> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |richard@nod.at --- Comment #28 from Richard Weinberger <richard@nod.at> --- I suffer from the same problem. :( -- 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#c29 --- Comment #29 from Richard Weinberger <richard@nod.at> --- (In reply to François Valenduc from comment #27)
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 <kresten@vester.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kresten@vester.org -- 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#c38 --- Comment #38 from François Valenduc <francois.valenduc@tvcablenet.be> --- So, I don't need to indicate the root device ? And resume is not more allowed ? -- 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#c39 --- Comment #39 from François Valenduc <francois.valenduc@tvcablenet.be> --- The system still doesn't boot whitout root and resume parameters. What I also find strange is that if I run lvm vgchange -a y in the shell I get with rd.break=initqueue, all the LVM volumes are found. So why aren't they detected in a normal boot ? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1051354 François Valenduc <francois.valenduc@tvcablenet.be> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(francoisvalenduc@ | |gmail.com) | -- 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#c41 --- Comment #41 from François Valenduc <francois.valenduc@tvcablenet.be> --- Maybe it was a bad copy paste from me, but the resume and root parameters where given only once. And the problem continues. -- 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#c43 --- Comment #43 from François Valenduc <francois.valenduc@tvcablenet.be> --- unfortunately, there is a no shell with rd.break=pre-mount -- 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#c45 --- Comment #45 from François Valenduc <francois.valenduc@tvcablenet.be> --- How can I use a serial console ? My computer is way to recent to have a serial port... With rd.debug, I can see that it repeatedly tries to find the root partition in the initqueue, without finding it. Is there a git tree of udev of systemd in opensuse ? Then I could use git bisect to try to find the problematic change. -- 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#c47 --- Comment #47 from François Valenduc <francois.valenduc@tvcablenet.be> --- the lvm volumes is on sda3 which is detected. It repeatedly tries to find /dev/mapper/system-opensuse, but in the end, it complains that it doesn't find /dev/system/opensuse -- 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#c48 --- Comment #48 from François Valenduc <francois.valenduc@tvcablenet.be> --- The problem is indeed dracut and not udev or systemd. If I revert to the older packages like explained in comment #5 and if I the update everythinhg (thus systemd and udev) except dracut, it works without problem. -- 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#c49 --- Comment #49 from François Valenduc <francois.valenduc@tvcablenet.be> --- I was a bit too fast. If I lock dracut, udev stays at the older version too. -- 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#c59 François Valenduc <francois.valenduc@tvcablenet.be> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|DUPLICATE |--- --- Comment #59 from François Valenduc <francois.valenduc@tvcablenet.be> --- In my case, this problem has nothing to do with rules for NVMe devices, I have a SATA disk. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com