Comment 10 for bug 1981622

Hi,

This is in fact caused by the recent systemd SRU, which includes a patch to systemd-pstore.service [1]. The issue appears to be quite benign, but if anyone has experienced side effects as a result of this change (besides the dmesg error), please let us know.

In the mean time, you can work around this issue:

EDIT: This will NOT fix any system that is not booting, because the "mtd device must be supplied (device name is empty)" message is not the cause of failed boots. This work around is only for those who are annoyed by the error message, but are otherwise not experiencing any issues.

# cp /{lib,etc}/systemd/system/systemd-pstore.service
# sed -i '<email address hidden> //' /etc/systemd/system/systemd-pstore.service
# systemctl daemon-reload

[1] https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?h=ubuntu-jammy&id=d990b13612810a296246011ad66a165b30166702