Richard - I edited my above comment to clarify. That workaround is not an attempt to fix boot on any systems.
To anyone that is experiencing boot issues, please open a separate bug with your journal logs and dmesg logs. The "mtd device must be supplied (device name is empty)" error is not the cause of your boot issues, and should be ignored. The reason you all are seeing this error message is that `systemd-pstore.service` is trying to recover kernel crash data from `/sys/fs/pstore` *after* a kernel crash. It happens that the mtdpstore module cannot be loaded, but systemd-pstore.service (and the rest of the system) will happily move along without it. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1981622 Title: mtd device must be supplied (device name is empty) Status in systemd package in Ubuntu: Confirmed Bug description: After updating my 22.04 system (possibly caused by Systemd update). And now booting, dmesg has two errors: 'mtd device must be supplied (device name is empty)'. See line 8 and 134 in the included logfile. The system are booting as it should though, and the system are working like it should no errors at all. Is this maybe caused by 'efi-pstore-not-cleared-on-boot.patch' in systemd? I have an EFI mounted at boot but it isn't used because I have installed my system in legacy BIOS mode. Is this maybe the culprit? I could ignore the message but it isn't nice though. Regards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1981622/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
