[Bug 1981622] Re: mtd device must be supplied (device name is empty)

Thu Sep 22 09:08:57 UTC 2022

This bug was fixed in the package systemd - 249.11-0ubuntu3.6

---------------
systemd (249.11-0ubuntu3.6) jammy; urgency=medium

  * Deny-list TEST-58-REPART on ppc64el (LP: #1988994)
    File: debian/patches/lp1988994-Deny-list-TEST-58-REPART-on-ppc64el.patch
    https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=d2ed3cc1d223bf35015b15ff83b50156b58f0f38

systemd (249.11-0ubuntu3.5) jammy; urgency=medium

  [ Nick Rosbrook ]
  * Ensure dns_search_domain_unlink_marked removes all marked domains (LP: #1975667)
    File: debian/patches/lp1975667-Ensure-dns_search_domain_unlink_marked-removes-all-marked.patch
    https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=919d5ddedd5bb8b45ab9437bf42d66c2821bb074
  * core,firstboot: workaround timezone issues on Ubuntu Core (LP: #1981042)
    Thanks to Robert Ancell for preparing the patch.
    File: debian/patches/lp1981042-core-firstboot-workaround-timezone-issues-caused-by-Ubunt.patch
    https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=b15546361b549217908fb6ca5d473be23d7fa757
  * network: do not remove localhost address (LP: #1979951)
    File: debian/patches/lp1979951-network-do-not-remove-localhost-address.patch
    https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=2cd88391cce9fe95a486ae6dd214c12f236f3881
  * units: remove the restart limit on the modprobe at .service (LP: #1982462)
    File: debian/patches/lp1982462-units-remove-the-restart-limit-on-the-modprobe-.service.patch
    https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=8f0acd1b2fbb8eed1259c34963e5e9b201bef900
  * pstore: do not try to load mtdpstore (LP: #1981622)
    File: debian/patches/lp1978079-efi-pstore-not-cleared-on-boot.patch
    https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=15225032c3657f5906ee49d48929f9295a8664a0
  * core/mount: downgrade log level about several mkdir failures (LP: #1979952)
    Files:
    - debian/patches/lp1979952-Revert-core-mount-fail-early-if-directory-cannot-be-creat.patch
    - debian/patches/lp1979952-core-mount-downgrade-log-level-about-several-mkdir-failur.patch
    https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=ee8cfcf500698fab2e990de291ecf4c3ab87a4ae
  * debian/control: add Recommends: systemd-hwe-hwdb to udev.
    The systemd-hwe-hwdb brings in additional hwdb rules for HWE, so we want
    those installed with udev by default.
    File: debian/control
    https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=4a7a3258c33201cca305956820fcc6bcd6052d76
  * hwdb: implement --root option for systemd-hwdb query (LP: #1988078)
    Files:
    - debian/libsystemd0.symbols
    - debian/patches/lp1988078-hwdb-implement-root-option-for-systemd-hwdb-query.patch
    - debian/patches/lp1988078-sd-hwdb-add-sd_hwdb_new_from_path.patch
    - debian/patches/lp1988078-sd-hwdb-include-sys-stat.h-in-hwdb-internal.h.patch
    https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=937fef96c858f2f2042bf71032f315647c14add0

  [ Luca Boccassi ]
  * Enable systemd-repart and ship it in a new systemd-repart package.
    (LP: #1897932)
    Add fdisk as test dependency, needed by test-repart which calls sfdisk.
    Add libfdisk-dev/libssl-dev as dependencies, needed for systemd-repart.
    Author: Luca Boccassi
    Files:
    - debian/control
    - debian/rules
    - debian/systemd-repart.install
    https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=debbc5e9362522210096ae5fa9da48378791e381

  [ Lukas Märdian ]
  * Add sd-repart as test depend, to avoid skipping TEST-58-REPART
    File: debian/tests/control
    https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=669190653f06a6554ddf9725cbeccac65149df23

 -- Nick Rosbrook <nick.rosbrook at canonical.com>  Fri, 09 Sep 2022
14:47:16 -0400

** Changed in: systemd (Ubuntu Jammy)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to the bug report.
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 at 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