Bug 1169927

Summary:	Boot stuck at "[ OK ] Started Create list of static device nodes for the current kernel."
Product:	[openSUSE] openSUSE Tumbleweed	Reporter:	t neo <tneo>
Component:	Bootloader	Assignee:	Jiri Srain <jsrain>
Status:	RESOLVED DUPLICATE	QA Contact:	Jiri Srain <jsrain>
Severity:	Major
Priority:	P5 - None
Version:	Current
Target Milestone:	---
Hardware:	x86-64
OS:	openSUSE Factory
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description t neo 2020-04-20 14:39:02 UTC

After ugrading my TumbleWeed installation to 20200416 snapshot I'm not able to boot my computer anymore. The boot process gets stuck at message:

"[ OK ] Started Create list of static device nodes for the current kernel."


Based upon this thread (https://forums.opensuse.org/showthread.php/539951-Boot-stuck-at-quot-OK-Started-Create-list-of-static-device-nodes-for-the-current-kernel-quot?p=2933747) I was able to work around the issue and disabling plymouth got me into my system. As Plymouth is not asking for my passprash to unlock my devices.

The file /usr/lib/systemd/system/systemd-ask-password-plymouth.service was changed during the last update so that:
ConditionPathExists=/run/plymouth/pid

changed to:
ConditionPathExists=/var/run/plymouth/pid

Whereas in /usr/lib/systemd/system/systemd-ask-password-console.service the pid file is still expected to be in /run/plymouth/pid. This led to a situation where I was asked neither on the console nor by plymouth for my password!

I could fix this by resetting the pid file path in systemd-ask-password-plymouth.service

Comment 1 Antoine Belvire 2020-04-20 18:29:27 UTC

Dupe of 1169783.

*** This bug has been marked as a duplicate of bug 1169783 ***