Bug 2039888 - systemd-249.8-1.fc35 fails to boot completely, drops me into an emergency shell
Summary: systemd-249.8-1.fc35 fails to boot completely, drops me into an emergency shell
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: systemd
Version: 35
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: systemd-maint
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 2039900 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-01-12 16:37 UTC by Nils Philippsen
Modified: 2022-01-18 11:54 UTC (History)
14 users (show)

Fixed In Version: systemd-249.9-1.fc35
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-01-18 11:54:48 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Logs of a failed boot. Contain artifacts of an attempt to reboot hard (SysRq+S,U,B) towards the end. (167.82 KB, text/plain)
2022-01-12 16:37 UTC, Nils Philippsen
no flags Details
journalctl -xb output (819.12 KB, text/plain)
2022-01-12 17:15 UTC, The Source
no flags Details

Description Nils Philippsen 2022-01-12 16:37:13 UTC
Created attachment 1850413 [details]
Logs of a failed boot. Contain artifacts of an attempt to reboot hard (SysRq+S,U,B) towards the end.

Description of problem:

After updating to the systemd-249.8-1.fc35 testing update, booting didn't complete but dropped me into an emergency shell.

Version-Release number of selected component (if applicable):
systemd-249.8-1.fc35

How reproducible:
Reproducible

Steps to Reproduce:
0. Install that version of systemd.
1. Reboot

Actual results:
I got dropped into an emergency shell. In this shell, attempting to start units with systemctl blocked completely (couldn't Ctrl+C out of it), the dbus system bus would sometimes become unavailable making even an orderly reboot impossible.

Expected results:
Booting works. 😃

Additional info:
Downgrading to systemd-249.7-2.fc35.x86_64 made my system bootable again.

Comment 1 The Source 2022-01-12 17:14:55 UTC
I can confirm the issue. For me pressing Ctrl+D while in emergency mode allows me to continue booting. In my journalctl -xb output I noticed that some systemd services failed to start (start-limit-hit)

Comment 2 The Source 2022-01-12 17:15:32 UTC
Created attachment 1850425 [details]
journalctl -xb output

Comment 3 Zbigniew Jędrzejewski-Szmek 2022-01-12 17:15:42 UTC
*** Bug 2039900 has been marked as a duplicate of this bug. ***

Comment 4 Zbigniew Jędrzejewski-Szmek 2022-01-12 17:17:10 UTC
It looks like the patches for #1956022 were the problem. I'll rebuild with them reverted.

Comment 5 Sammy 2022-01-12 18:53:35 UTC
I can also confirm this on two of my DELL Precision machines....

Comment 6 Sammy 2022-01-12 22:56:42 UTC
Versions 249.9 solved the issue it looks like.

Comment 7 Christian Labisch 2022-01-13 11:50:50 UTC
With version 249.9 the system boots as expected.


Note You need to log in before you can comment on or make changes to this bug.