FS#79187 - [systemd] Unable to mount root device on boot with systemd 253.7

Attached to Project: Arch Linux
Opened by Aaron Barany (akb825) - Monday, 24 July 2023, 06:54 GMT
Last edited by Christian Hesse (eworm) - Sunday, 30 July 2023, 22:00 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Christian Hesse (eworm)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

Description:
After updating to systemd 253.7, booting the system dropped to the emergency shell with a message of "device UUID=XXX not found", where XXX was the UUID of my root device.

Looking at the upstream systemd-stable github project, there is one commit (https://github.com/systemd/systemd-stable/commit/ca7787a9f29ff836a300b782a73f9c5926ee0d14) immediately after the 253.7 release. After building systemd 253.7 locally with this commit, I was able to boot as normal. This commit appears to fix an issue with non-btrfs disks, where my various partitions are ext4.

Additional info:
* package version 253.7
* link to upstream fix: https://github.com/systemd/systemd-stable/commit/ca7787a9f29ff836a300b782a73f9c5926ee0d14

Steps to reproduce:
1. Update to systemd 253.7 with an ext4 root disk
2. Reboot system
This task depends upon

Closed by  Christian Hesse (eworm)
Sunday, 30 July 2023, 22:00 GMT
Reason for closing:  Fixed
Additional comments about closing:  systemd 254-1
Comment by Aaron Barany (akb825) - Monday, 24 July 2023, 07:10 GMT
See also forum thread at https://bbs.archlinux.org/viewtopic.php?pid=2111416
Comment by Toolybird (Toolybird) - Monday, 24 July 2023, 20:38 GMT
Clearly, only a very small minority are affected by this...there must be more to it than just simply having an ext4 root disk i.e. a specific configuration, an initrd screw up, etc.
Comment by Christian Hesse (eworm) - Monday, 24 July 2023, 21:22 GMT
Uh, bad timing... Just pushed another pre-release to core-testing. 🥴 I would like to wait for feedback on that in case of issues.

Looks like this is indeed a very specific issue and limited to a small number of systems. For now you are welcome to test the pre-release. It looks really stable for now, and already contains your fix.
Comment by Eli T. Drumm (etdr) - Tuesday, 25 July 2023, 14:02 GMT
Odd, I had this happen to me yesterday but my root partition *is* btrfs. Didn't happen to me with systemd 253.7 and Linux 6.4.4 but instead it happened when I upgraded to 6.4.5. Downgrading back to 6.4.4 let me boot normally again.

EDIT: should I be posting this on that forum thread instead?
Comment by Jaakko Hintsala (Hina) - Friday, 28 July 2023, 05:53 GMT
I think that would help.

Loading...