FS#34345 - systemd won't boot; tries to run not-configured plymouth
Attached to Project:
Arch Linux
Opened by kei (kei) - Sunday, 17 March 2013, 14:46 GMT
Last edited by Dave Reisner (falconindy) - Wednesday, 20 March 2013, 17:40 GMT
Opened by kei (kei) - Sunday, 17 March 2013, 14:46 GMT
Last edited by Dave Reisner (falconindy) - Wednesday, 20 March 2013, 17:40 GMT
|
Details
Description:
After yesterday's update (Mar 16) my system won't boot anymore. The red error message from "journalctl -xb" is "Failed at step EXEC spawning /bin/plymouth: No such file or directory". The strange thing: I've never used plymouth---at least not on purpose. Plymouth is not installed according to "pacman -Qs plymouth" and "grep -r 'plymouth' /etc" does not yield any result. I'm cautious about altering stuff myself as I don't know much about systemd, but since this is the computer I use for work, I'd appreciate to hear of any quick workarounds. Additional info: * package version(s) systemd 198-1 filesystem 2013.03-2 * config and/or log files etc. I will try to extract them from the rescue shell if needed! Steps to reproduce: Boot the system. I'd be glad to supply additional information; just let me know! |
This task depends upon
Closed by Dave Reisner (falconindy)
Wednesday, 20 March 2013, 17:40 GMT
Reason for closing: Not a bug
Additional comments about closing: User configuration error.
Wednesday, 20 March 2013, 17:40 GMT
Reason for closing: Not a bug
Additional comments about closing: User configuration error.
# journalctl -xb -p err
... systemd[1]: Failed to load default target: No such file or directory
... kernel: microcode: failed to load file amd-ucode/microcode_amd.bin
... kernel: sp5100_tco: mmio address 0xb8fe00 already in use
... systemd[280]: Failed at step EXEC spawning /bin/plymouth: No such file or directory
I'm pretty sure that the second error has been there before (I think I forgot to install the amd ucode package), but I don't know about the others. How can I identify what's keeping the default target from loading? I didn't change anything in the unit files.
If I jump out of rescue mode with C-d, system boots normally to my awesomewm desktop (I have autologin configured with SLiM). Here I observe second weird thing, if I logout of my awesomewm session, SLiM suddenly hangs. Or when I try to poweroff instead of logout, systemd-198-1 has trouble to shut down SLiM service, as it takes extra time.
Solution for me: downgrade back to systemd-197-4 lib32-systemd-197-1 systemd-sysvcompat-197-4 and lurk in this bug thread :(
-- Unit sysinit.target has finished starting up.
--
-- The start-up result is done.
Mar 18 12:31:18 vali-notebook mtp-probe[1892]: checking bus 2, device 2: "/sys/devices/pci0000:00/0000:00:1d.7/usb2/2-2"
Mar 18 12:31:18 vali-notebook mtp-probe[1893]: checking bus 2, device 3: "/sys/devices/pci0000:00/0000:00:1d.7/usb2/2-6"
Mar 18 12:31:18 vali-notebook mtp-probe[1893]: bus: 2, device: 3 was not an MTP device
Mar 18 12:31:18 vali-notebook mtp-probe[1892]: bus: 2, device: 2 was not an MTP device
Mar 18 12:31:21 vali-notebook kernel: bio: create slab <bio-1> at 1
Mar 18 12:31:21 vali-notebook mkswap[1937]: Setting up swapspace version 1, size = 2000056 KiB
Mar 18 12:31:21 vali-notebook mkswap[1937]: no label, UUID=97890cc8-fe0f-4505-88a9-0df49b699e68
Mar 18 12:31:25 vali-notebook systemd[1946]: Failed at step EXEC spawning /bin/plymouth: No such file or directory
-- Subject: Process /bin/plymouth could not be executed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: http://www.freedesktop.org/wiki/Software/systemd/catalog/641257651c1b4ec9a8624d7a40a9e1e7
--
-- The process /bin/plymouth could not be executed and failed.
--
-- The error number returned while executing this process is 2.
A little research showed me that this is nota bug.
From systemd(1):
KERNEL COMMAND LINE
2, 3, 4, 5
Boot into the specified legacy SysV runlevel. These are equivalent to systemd.unit=runlevel2.target, ...
In systemd-198-1 the symlinks runleveln.target are removed.
See commit 245d345f7539983c08fd8dbc0c51079422ca096a, build-sys: link runlevel targets on install only if sysv compat is enabled, http://cgit.freedesktop.org/systemd/systemd/commit/?id=245d345f7539983c08fd8dbc0c51079422ca096a