https://bugzilla.suse.com/show_bug.cgi?id=1181242 https://bugzilla.suse.com/show_bug.cgi?id=1181242#c34 Suse User <suseino@riseup.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(suseino@riseup.ne | |t) | --- Comment #34 from Suse User <suseino@riseup.net> ---

Suse User, can you please check if comment 25 fixes the issue for you?

I appended 'systemd-udev-settle.service' to the 'After=' line in the .service file and rebooted. It does not not fix the issue, so I have undone it.

Can you share your block device setup after boot (lsblk)?

https://susepaste.org/1c4e2f1d

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.

Are the block devices and in particular LVM PVs/LVs correctly set up after boot?

I don't know. How do I check to confirm? Generally everything disk/partition related seems to work as expected.

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" 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). -- You are receiving this mail because: You are on the CC list for the bug.