FS#61324 - [systemd] Systemd v240 may report mount units as failed which leads to boot into emergency console

Attached to Project: Arch Linux
Opened by Michel Koss (MichelKoss1) - Wednesday, 09 January 2019, 13:44 GMT
Last edited by Dave Reisner (falconindy) - Sunday, 13 January 2019, 16:13 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Dave Reisner (falconindy)
Architecture All
Severity Critical
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 17
Private No

Details

Description:

Systemd v240 may mistakenly report mount units as failed which leads to boot into emergency console. This issue was already reported and fixed upstream. There is one commit to backport for Arch.

Upstream issue: https://github.com/systemd/systemd/issues/11362

Upstream pr: https://github.com/systemd/systemd/pull/11364

Upstream commit: https://github.com/systemd/systemd/commit/d253a45e1c147f5174265d71d7419da7bd52a88b

Additional info:
* systemd 240.0-3
This task depends upon

Closed by  Dave Reisner (falconindy)
Sunday, 13 January 2019, 16:13 GMT
Reason for closing:  Fixed
Additional comments about closing:  core/systemd-240.34-2
Comment by Anton (sci-pirate) - Wednesday, 09 January 2019, 17:02 GMT
Leads to https://bbs.archlinux.org/viewtopic.php?id=167109

All possible fixes found in the topic and here: https://superuser.com/questions/769047/unable-to-find-root-device-on-a-fresh-archlinux-install aren't working. Suggest to downgrade to 239 till the patch not get upstream.
Comment by Dave Reisner (falconindy) - Thursday, 10 January 2019, 15:31 GMT Comment by Oleg Nagornij (corner) - Thursday, 10 January 2019, 17:46 GMT
Unfortunately does not work

desktop|~# inxi -CIM
Machine: Type: Desktop Mobo: MSI model: X99A RAIDER (MS-7885) v: 5.0 serial: N/A UEFI: American Megatrends v: P.50
date: 07/19/2016
CPU: Topology: 8-Core model: Intel Xeon E5-2620 v4 bits: 64 type: MT MCP L2 cache: 20.0 MiB
Speed: 1322 MHz min/max: 2100/3000 MHz Core speeds (MHz): 1: 1268 2: 1753 3: 2064 4: 1938 5: 1968 6: 1941 7: 1911
8: 1911 9: 1700 10: 1637 11: 1937 12: 2083 13: 1940 14: 1940 15: 1901 16: 1903
Info: Processes: 336 Uptime: 2m Memory: 62.81 GiB used: 11.49 GiB (18.3%) Init: systemd Shell: bash inxi: 3.0.30
Comment by Michel Koss (MichelKoss1) - Thursday, 10 January 2019, 18:02 GMT
@falconindy those packages fix this bug on my system

@corner perhaps you issue is something different?
Comment by Oleg Nagornij (corner) - Thursday, 10 January 2019, 18:24 GMT Comment by Michel Koss (MichelKoss1) - Thursday, 10 January 2019, 18:47 GMT
@corner that seems related to  FS#61334  which is different than this one.

Loading...