https://bugzilla.suse.com/show_bug.cgi?id=1181242 https://bugzilla.suse.com/show_bug.cgi?id=1181242#c35 --- Comment #35 from heming zhao <heming.zhao@suse.com> --- (In reply to Suse User from comment #34)

...

Do you see any other issues?

Recently I have reported a few other bugs. No idea if any and which of them may be related.

Please show me these bug url.

...

1. open & edit /etc/lvm/lvm.conf change cfg item external_device_info_source from "udev" to "none" [...] the last grep cmd should show: external_device_info_source = "udev"

It shows:

external_device_info_source = "none"

which meaning did you say: in rootfs /etc/lvm/lvm.conf has "none" or in initrd the value is "none" or both is "none"? in your machine, the new cfg value may be saved in /etc/lvm/lvm.conf.rpmsave (please check it), so the dracut will generate initrd with old value ("none"). if the value is "none" in both initrd & rootfs, you may have a different issue (not bsc#1181432).

After applying this workaround and rebooting, I did not get the errors reported initially, but now I got:

[ 43.766472] lvm[635]: WARNING: Device /dev/sda not initialized in udev database even after waiting 10000000 microseconds.

Please let me know if I should undo the workaround (e.g. if a bugfix would make it irrelevant or conflicting).

keep or revert is safe for your machine. change to "none" value which is just revert one of recent lvm2 change. you can get the lvm2 changelog by cmd: ``` rpm -qi lvm2-2.03.<your-current-version>.x86_64 --changelog | head -n 40 ``` the "udev" value response to the change commit: ``` - lvm2 should use 'external_device_info_source="udev"' by default (bsc#1179691) - change external_device_info_source from none to udev ``` so I have another question: which tumbleweed version did you use before updating to 20210118 (c#0 mentioned). what's lvm2 version do you use? (by: rpm -qa | grep lvm2) ----- from c#8 comment ``` [ 25.926875] systemd[1]: Detected architecture x86. ``` It shows your arch is x86, not x86-64. what's your arch? Would you provide us a reproduced method for your issue? Do you familiar with qemu-kvm? do you have time to set up a env under qemu-kvm, reproduce the issue, and tell us the steps. if you want to help us to remove the issue, please send us full boot log(from first line output to login prompt). Or send mail directly to us. -- You are receiving this mail because: You are on the CC list for the bug.