Hi, on 21.09.2022 updating ubuntu broke it with this bug. Running on i386, dell latitude e7450 with ssd and ubuntu22.04.1, kernel 5.15.0-48 generic, x86.
After booting, I get the mtd device must be supplied etc etc error, and I am left with a terminal only version. I have an important hint: as suggested above, it's a problem with some authentication stuff. Yesterday after the bad upgrade, I put the pc in suspend mode. When I re opened it, I failed to log in into my account (the graphical session was otherwise normal) in a funny way: when propmted the password, it was as if the Enter key was continuosly being pressedm and I could at most enter one single word. I have seen from a link provided above that the i386 version has not been tested, which is indeed my version. Running apt-cache policy systemd returns (roughly, cannot copy and past as I'm from another machine): Installed 249.11-0ubuntu3.4 Candidate same version tables has entries: 249.11-ubuntu3.4 500 249.11-ubuntu3 I have tried the other suggested actions but none worked. I have failed in installing the proposed ubuntu3.6 version of systemd, goes beyond my skills, I would need more detailed instructions. Otherwise is it possible to undo the update of 21.09.22? I may try this path or just switch to something Fedora, it is not accetaple that a daily update breaks down an LTS, it's the first time it happens to me in 8 years of ubuntu, please provide a fix on the main brench. -- 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: Fix Released Status in systemd source package in Focal: Invalid Status in systemd source package in Jammy: Fix Released Bug description: [WORKAROUND] This will NOT fix a 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. If you are not able to boot your system, but you see this error message, please open a separate bug with your journalctl and dmesg logs. # cp /{lib,etc}/systemd/system/systemd-pstore.service # sed -i 's/modprobe@mtdpstore.service //' /etc/systemd/system/systemd-pstore.service # systemctl daemon-reload [Impact] Due to mtdpstore not being properly configured as a pstore backend, when systemd-pstore.service tries to load the module, users get the following error in dmesg: [ 18.453473] systemd[1]: Starting Load Kernel Module mtdpstore... [ 18.462685] mtd device must be supplied (device name is empty) This is a distracting error for users trying to diagnose other system issues, especially if their system does not boot after a kernel crash and this is the only message displayed on the console. [Test Plan] * Force a kernel crash to populate /sys/fs/pstore, thus causing systemd-pstore.service to start on the subsequent boot: # echo 1 > /proc/sys/kernel/sysrq # echo 1 > /proc/sys/kernel/panic # echo c > /proc/sysrq-trigger * When the system reboots, observe the error in dmesg: # dmesg | grep mtd [Where problems could occur] If a system was relying on this pstore backend, and mtdpstore is built as a module, it is possible for systemd-pstore.service to trigger before mtdpstore is loaded, causing systemd-pstore to not copy the contents of /sys/fs/pstore. Note however that before the patched introduced as a result of bug 1978079, systemd-pstore.service would not attempt to load *any* kernel modules. [Original 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
