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

English Install/Boot/Login
#1

Hello everyone,

after doing an update from openSUSE Tumbleweed 20200413-0 -> 20200415-0 my system gets stuck during boot at

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

After doing a

snapper rollback

to the previous snapshot everything worked fine again, so this is definitely a software issue.
Can you help me, figure this out, please?

Regards,
🂩

#2

Try booting without “quiet” and with “plymouth.enable=0” on kernel command line, it may give some hints. Otherwise you can enable early debug shell in systemd, this may allow looking at system state when it “hangs”: https://freedesktop.org/wiki/Software/systemd/Debugging/

#3

Hi @arvidjaar](https://forums.opensuse.org/member.php/69818-arvidjaar),

thank you for your advise. I disabled plymouth while booting and it worked. I was asked for the passphrase for my encrypted hard drive, which did not happen when I booted with plymouth and hit [Esc].

However I figured out, that the file /usr/lib/systemd/system/systemd-ask-password-plymouth.service had changed during the last update so that


ConditionPathExists=/run/plymouth/pid
[/CODE/

became

ConditionPathExists=/var/run/plymouth/pid


whereas in [u]/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 in *plymouth* for my password!

I could fix this by resetting the pid file path in systemd-ask-password-plymouth.service, but this is clearly a bug. Where can I report this?

Thank you for your help.

Regards,
🂩
#4

Hi @arvidjaar,

thank you for your advise. I disabled plymouth while booting and it worked. I was asked for the passphrase for my encrypted hard drive, which did not happen when I booted with plymouth and hit [Esc].

However I figured out, that the file /usr/lib/systemd/system/systemd-ask-password-plymouth.service had changed during the last update so that

 
ConditionPathExists=/run/plymouth/pid

became


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, but this is clearly a bug. Where can I report this?

Thank you for your help.

Regards,
🂩

#5

I doubt it is the reason for the problem, but if you verified that after changing service definition problem is fixed report bug at https://bugzilla.opensuse.org/

#6

It may be the same issue mentioned in the release notes:

#7

Today I had the same issue when switching to the 2020-04-16 TW release. I was not able to execute anything on the terminal and could not rollback to previous snapshot. As whatever I was doing threw a “failed dbus error” message.

I tried clean installing TW, but same result, now I’m going back to 15.1 and wait until TW releases new snapshot that works.

#8

During the last few weeks I installed every snapshot up to 20200416 and never experienced problems. I have:

erlangen:~ # ll /var/run/plymouth/pid
-rw-r--r-- 1 root root 4 Apr 20 05:56 /var/run/plymouth/pid
erlangen:~ # ll /run/plymouth/pid
-rw-r--r-- 1 root root 4 Apr 20 05:56 /run/plymouth/pid
erlangen:~ #

Provide further detail. I think waiting only won’t change anything.

#9

Installation is an issue at the moment. TW is currently working to get installed. It has been a while that I had so much trouble to boot my system after TW upgrade broke my system.

#10

Thanks for the debugging steps and fix for me!

I created a bug report: https://bugzilla.opensuse.org/show_bug.cgi?id=1169927