| Summary: | Upgrade to systemd-44 renders the system unbootable | ||
|---|---|---|---|
| Product: | systemd | Reporter: | Bworthalex |
| Component: | general | Assignee: | Lennart Poettering <lennart> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | medium | ||
| Version: | unspecified | ||
| Hardware: | x86-64 (AMD64) | ||
| OS: | Linux (All) | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
| Attachments: | Screenshot showing systemd failing to boot | ||
I've verified this by starting off with a new exherbo installation with systemd-44 and it results in the same unbootable system. Installing systemd version 37 gets things working magically. Version 37 is the version I had working before it was upgraded to 44. I can reproduce this by upgrading systemd to version 44 which renders the system unbootable and downgrading back to version 37 makes things work again ! Could you retest with current systemd please? This should all work now as -.mount doesn't pull in systemd-journald.socket anymore! I switched over to funtoo as I was facing to many woes with exherbo. I have systemd version 185 installed on funtoo and it is working great. Thanks for getting back to me. I took the liberty to mark this bug as resolved. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.
Created attachment 59698 [details] Screenshot showing systemd failing to boot I upgraded systemd to version 44 on my exherbo system and ever since Systemd fails at boot time. I've upgraded/reinstalled all the packages that install files to /etc/system/systemd and /lib/systemd and the directory /lib/systemd doesn't exist anymore. I've also checked for links under /etc/systemd and everything is in order. (udev has been upgraded to 182.) When system boots the root file system gets mounted successfully and systemd is started but freezes with the message "failed to fully start up daemon: operation not permitted". The only option at this time is to hard reset my computer. Systemd even fails to launch rescue and emergency shells with the same message. Any pointers as to how I can debug this ? I've tried to edit the source files inserting log_error statements to help diagnose the problem. It apparently continues to execute despite the above mentioned error message. I'm having hard time to figure out exactly at which point it bails out. Any help in this direction will be highly appreciated. Thanks Alex