boot hangs on Scientific Linux 7 with a message "a start job is running for Wait for Plymouth..."
by edorig from LinuxQuestions.org on (#517CR)
I have asked this question first in the scientific linux forum, but since CentOS7 and Scientific Linux 7 are rather similar this could be of interest to CentOS7 users.
I have a HP ZBook 14, with ATI Radeon graphics card and LUKS encrypted hard drive. This computer in under Scientific Linux with GNOME 3 and has worked without issue since January. This morning, after asking for the decryption password of the drive, the computer froze to a black screen, showing only a mouse pointer instead of the banner.
Switching to a console, a message 'A start job is running for Wait for Plymouth Boot screen to quit (13min/no limit)' showed up.
I was able to reboot the computer in rescue mode, and change the target from graphical to multi-user for systemd. The computer boots in text mode (runlevel 3 in System V terminology) and X can be started with startx.
If possible, I would like to restore full graphical login.
What is the role of pymouthd ? Does it simply show a banner ? Can it be eliminated from the boot sequence without trouble ? Or do I need to use an alternative login manager to gdm ?
I have found links reporting similar issues in Oracle Linux and CentOS but no solution.
https://unix.stackexchange.com/quest...-plymouth-boot
https://unix.stackexchange.com/quest...-gnome-upgrade
https://bugzilla.redhat.com/show_bug.cgi?id=1205610
https://support.oracle.com/knowledge...2433775_1.html
I have a HP ZBook 14, with ATI Radeon graphics card and LUKS encrypted hard drive. This computer in under Scientific Linux with GNOME 3 and has worked without issue since January. This morning, after asking for the decryption password of the drive, the computer froze to a black screen, showing only a mouse pointer instead of the banner.
Switching to a console, a message 'A start job is running for Wait for Plymouth Boot screen to quit (13min/no limit)' showed up.
I was able to reboot the computer in rescue mode, and change the target from graphical to multi-user for systemd. The computer boots in text mode (runlevel 3 in System V terminology) and X can be started with startx.
If possible, I would like to restore full graphical login.
What is the role of pymouthd ? Does it simply show a banner ? Can it be eliminated from the boot sequence without trouble ? Or do I need to use an alternative login manager to gdm ?
I have found links reporting similar issues in Oracle Linux and CentOS but no solution.
https://unix.stackexchange.com/quest...-plymouth-boot
https://unix.stackexchange.com/quest...-gnome-upgrade
https://bugzilla.redhat.com/show_bug.cgi?id=1205610
https://support.oracle.com/knowledge...2433775_1.html