FS#78090 - [systemd] nvme root fails to mount at boot after upgrade to 253.2
Attached to Project:
Arch Linux
Opened by Mikael Malmström (micke1m) - Saturday, 01 April 2023, 15:15 GMT
Last edited by Toolybird (Toolybird) - Sunday, 02 April 2023, 22:20 GMT
Opened by Mikael Malmström (micke1m) - Saturday, 01 April 2023, 15:15 GMT
Last edited by Toolybird (Toolybird) - Sunday, 02 April 2023, 22:20 GMT
|
Details
Upgrading systemd from 253.1 to 253.2 makes my system
unbootable.
The root nvme partition fails to mount at boot. (Kingston Fury Renegade M.2 2GB) I am using systemd boot, if that matters. Downgrading to 253.1 fixes the problem. See attached image. |
This task depends upon
Closed by Toolybird (Toolybird)
Sunday, 02 April 2023, 22:20 GMT
Reason for closing: None
Additional comments about closing: Reporter says "Probably related to the previous UUID report"
Sunday, 02 April 2023, 22:20 GMT
Reason for closing: None
Additional comments about closing: Reporter says "Probably related to the previous UUID report"
There is not enough info provided here to identify an Arch packaging bug. Please read about submitting good bug reports [1]. There are no other reports about the 253.1 to 253.2 upgrade causing similar boot failure. Although, there were some earlier reports that involved mismatched UUID entries e.g [2].
[1] https://wiki.archlinux.org/title/Bug_reporting_guidelines
[2] https://bugs.archlinux.org/task/77780#comment216060