https://bugzilla.suse.com/show_bug.cgi?id=1208161 https://bugzilla.suse.com/show_bug.cgi?id=1208161#c2 --- Comment #2 from Michael Hirmke --- Does not happen with kernel 6.1.8-1. -- You are receiving this mail because: You are the assignee for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1208161 https://bugzilla.suse.com/show_bug.cgi?id=1208161#c4 --- Comment #4 from Michael Hirmke --- With kernel 6.1.12-1-default and openSUSE Tumbleweed 20230217 the problem still exists, but does not occur on every boot. -- You are receiving this mail because: You are the assignee for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1208161 https://bugzilla.suse.com/show_bug.cgi?id=1208161#c6 --- Comment #6 from Michael Hirmke --- I found out, that if I wait for about 30 seconds before entering the LUKS passphrase for the root partition in the plymouth dialog, I don't get the additional boot time and the "timeout". Instead I get systemd[1]: Unnecessary job was removed for /dev/disk/by-uuid/47c6783a-2b0$740*bd3$f0f43f63d8c. as in kernel 6.8.1. This does neither explain to me, why this crippled device name exists, nor why waiting 30 seconds will help, but perhaps someone else can see whats going on here. -- You are receiving this mail because: You are the assignee for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1208161 https://bugzilla.suse.com/show_bug.cgi?id=1208161#c8 Michael Hirmke changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Kernel |Basesystem Assignee|kernel-bugs@opensuse.org |screening-team-bugs@suse.de --- Comment #8 from Michael Hirmke --- Still exists with kernel 6.2.0-1-default and openSUSE Tumbleweed 20230228. So probably not a kernel, but a systemd problem? ... M�r 01 22:30:18 transformer systemd[1]: dev-disk-by\x2duuid-47c6783a\x2d2b0\x24740\x2abd3\x24f0f43f63d8c.device: Job dev-disk-by\x2duuid-47c6783a\x2d2b0\x24740\x2abd3\x24f0f43f63d8c.device/start timed out. M�r 01 22:30:18 transformer systemd[1]: Timed out waiting for device /dev/disk/by-uuid/47c6783a-2b0$740*bd3$f0f43f63d8c. M�r 01 22:30:18 transformer systemd[1]: Dependency failed for Cryptography Setup for root. M�r 01 22:30:18 transformer systemd[1]: Dependency failed for Local Encrypted Volumes. M�r 01 22:30:18 transformer systemd[1]: cryptsetup.target: Job cryptsetup.target/start failed with result 'dependency'. M�r 01 22:30:18 transformer systemd[1]: systemd-cryptsetup@root.service: Job systemd-cryptsetup@root.service/start failed with result 'dependency'. M�r 01 22:30:18 transformer systemd[1]: dev-disk-by\x2duuid-47c6783a\x2d2b0\x24740\x2abd3\x24f0f43f63d8c.device: Job dev-disk-by\x2duuid-47c6783a\x2d2b0\x24740\x2abd3\x24f0f43f63d8c.device/start failed with result 'timeout'. ... -- You are receiving this mail because: You are the assignee for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1208161 https://bugzilla.suse.com/show_bug.cgi?id=1208161#c10 --- Comment #10 from Michael Hirmke --- Still exists with kernel-6.2.2-1. -- You are receiving this mail because: You are the assignee for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1208161 https://bugzilla.suse.com/show_bug.cgi?id=1208161#c12 Michael Hirmke changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|WORKSFORME |--- --- Comment #12 from Michael Hirmke --- Damn, problem is back 8-< -- You are receiving this mail because: You are the assignee for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1208161 http://bugzilla.suse.com/show_bug.cgi?id=1208161#c14 Michael Hirmke changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |WORKSFORME Status|REOPENED |RESOLVED --- Comment #14 from Michael Hirmke --- I found the reason: Besides /run/systemd/generator/systemd-cryptsetup@root.service there was another systemd-cryptsetup@root.service file in /etc/systemd/system. The difference was /run/systemd/generator/systemd-cryptsetup@root.service: BindsTo=dev-disk-by\x2duuid-47c6783a\x2dd2b0\x2d4740\x2dabd3\x2d4f0f43f63d8c.device After=dev-disk-by\x2duuid-47c6783a\x2dd2b0\x2d4740\x2dabd3\x2d4f0f43f63d8c.device /etc/systemd/system/systemd-cryptsetup@root.service: BindsTo=dev-disk-by\x2duuid-47c6783a\x2d2b0\x24740\x2abd3\x24f0f43f63d8c.device After=dev-disk-by\x2duuid-47c6783a\x2d2b0\x24740\x2abd3\x24f0f43f63d8c.device i.e. the latter contained a wrong escaped guid for the encrypted partition. I have no idea, what created such an escape sequence and why this file existed at all. After removing /etc/systemd/system/systemd-cryptsetup@root.service, the problem vanished. -- You are receiving this mail because: You are the assignee for the bug.