Unknown messages at shutdown after systemd 259.1 update

rosenbaum · 2025-12-19 17:59:16

Hello, I'm getting the following during shutdown.

shutdown[1]: Failed to parse /proc/self/mountinfo: Operation not supported
shutdown[1]: Unable to unmount file system: Operation not supported

They're the last thing shown before the screen goes black.
It seems harmless but it's been there ever since I updated to systemd-259-1.
Any help would be appreciated in removing just these messages either by fixing them or hiding them, thanks.

Last edited by rosenbaum (2025-12-19 18:00:21)

gromit · 2025-12-19 18:43:48

Which kernel package and version are you using?

rosenbaum · 2025-12-19 19:43:07

gromit wrote:

Which kernel package and version are you using?

linux 6.18.1-arch1-2

Last edited by rosenbaum (2025-12-19 19:43:36)

gromit · 2025-12-19 21:05:54

Hm, I don't have that in my journal ... Do you have any special mounts configured? Maybe post the output of "cat /etc/fstab" or "mount"

rosenbaum · 2025-12-19 21:17:37

Neither do I, journalctl won't save them because I reckon they come in so late in the shutdown sequence that most of the systemd journal services are already stopped.
I can only see it when I shut it down. I've enabled "quiet" in the kernel parameters so that it's the only thing printed. See the picture below.

https://i.imgur.com/Wjdh7pS.jpeg

I've been running this /etc/fstab file for at least a year without any problems.

# Static information about the filesystems.
# See fstab(5) for details.

# <file system> <dir> <type> <options> <dump> <pass>
# /dev/mapper/root
UUID=(hidden)   /                           ext4   rw,relatime                                                                                                                                            0 1 

# /dev/nvme0n1p1
UUID=(hidden)                              /boot          vfat   rw,relatime,fmask=0137,dmask=0027,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro   0 2

Last edited by rosenbaum (2025-12-19 21:22:22)

gromit · 2025-12-19 21:20:58

Is this also present with the linux-lts package?

tronie.service · 2025-12-19 22:51:47

I have 6-12-63-LTS kernel and the same issue.

I have a BIOS/MBR install using grub to boot. Kernel is 6.12.63. Intel CPU i3. DE is Plasma, no fancy customizations. Root & swap partition, only. Asigned via UUID in /etc/fstab. Fallback initramfs has been disabled (and deleted). System fully updated. systemd 259-1 been freshly installed during last update.

When I shutdown I see for very short time following messages:

... shutdown[1]: Failed to parse /proc/self/mountinfo: Operation not supported
... shutdown[1]: Unable to unmount file systems: Operation not supported
... shutdown[1]: Cannot enumerate swap partitions, no libmount support.
... shutdown[1]: Unable to deactivate swaps: Operation not supported
... shutdown[1]: Failed to parse /proc/self/mountinfo: Operation not supported
... shutdown[1]: Unable to unmount file systems: Operation not supported
... shutdown[1]: Cannot enumerate swap partitions, no libmount support.
... shutdown[1]: Unable to deactivate swaps: Operation not supported
... shutdown[1]: Unable to finalize remaining file systems, swap devices, ignoring.

It does not make a difference if I keep the legacy HOOKS with base and udev or the new default with systemd (without base).

Last edited by tronie.service (2025-12-20 10:29:06)

post-factum · 2025-12-19 23:33:31

It's a mkinitcpio issue. Since v259, systemd doesn't have a linker dependency on libmount.so, and mkinitcpio doesn't pull the library into the shutdown initramfs causing the errors you observe.

Initially, the issue was reported here: https://github.com/systemd/systemd/issues/40154

Currently, a workaround is to put

add_binary /usr/lib/libmount.so

into /usr/lib/initcpio/install/sd-shutdown.

I've discussed this with Foxboron in #archlinux, he'll probably fix this "soon". Likely, mkinitcpio should be pulling in other now-"weak" deps of systemd like libblkid etc too.

athan · 2025-12-20 00:22:47

I am experiencing the same problem after updating to systemd-259-1, regardless of the kernel (latest or LTS).

991.5718171 watchdog: watchdog: watchdog did not stop!
991.7118873 watchdog: watchdog®: watchdog did not stop!
991.7572853 991.7579493 shutdoun[1]: Failed to parse /proc/self/sountinfo: Operation not supported
991.7585443 shutdoun[1]: Unable to unmount file systems: Operation not supported
991.7598431 shutdoun[1]: Cannot enuserate swap partitions, no libaount support.
991.7596883 shutdoun[1]: Unable
991.7681263 shutdoun[1]: Failed to deactivate suaps: Operation not supported shutdoun[11: Unable to parse /proc/self/sountinfo: Operation not supported
991.7685863 to unmount file systems: Operation not supported
991.7689683 shutdount1]: Cannot enunerate suap partitions, no 1lbaount support.
991.7613223 shutdoun[1]: Unable to deactivate suaps: Operation not supported watchdog: watchdog: watchdog did not stop!
991.7617944 shutdoun[1]: Unable to finalize remaining file systems, swap devices, igouring.

zoui · 2025-12-20 08:19:44

Thanks for your answer post-factum. Can the errors be safely ignored until the fix is available ?

post-factum · 2025-12-20 10:13:27

Not sure about the errors. IMO, they shouldn't be ignored.

Reboot9012 · 2025-12-20 10:22:46

Which line should this binary should be added inside the if ?

Allan · 2025-12-20 10:25:21

Anyone want to file the mkinitcpio bug?

post-factum · 2025-12-20 10:26:36

Like this:

--- /usr/lib/initcpio/install/sd-shutdown~      2025-12-20 11:25:18.697000000 +0100
+++ /usr/lib/initcpio/install/sd-shutdown       2025-12-20 11:26:00.646095072 +0100
@@ -2,6 +2,7 @@
 # SPDX-License-Identifier: GPL-2.0-only

 build() {
+    add_binary /usr/lib/libmount.so
     add_binary /usr/lib/systemd/systemd-shutdown /shutdown

     if type -P kexec >/dev/null; then

Reboot9012 · 2025-12-20 10:32:18

That seems to work thanks

tronie.service · 2025-12-20 10:41:07

Works for me, too.

Matthl · 2025-12-20 11:08:13

If I apply the workaround and add the line above to the file /usr/lib/initcpio/install/sd-shutdown - will the file sd-shutdown be replaced with a future bugfix mkinitcpio update?
Or do I have to remember the fix and remove the line manually, then?

Last edited by Matthl (2025-12-20 11:08:43)

nowy · 2025-12-20 12:35:16

Allan wrote:

Anyone want to file the mkinitcpio bug?

I’ve been trying to file the report since yesterday, but I'm currently stuck because the one-time code for login isn't being sent to my email.

The bug details are identical to the discussions here and this GitHub issue: https://github.com/systemd/systemd/issues/40154

athan · 2025-12-20 13:53:18

Is it possible to use a local config override instead of modifying a system file?

Berni341 · 2025-12-20 14:34:53

Can confirm this bug.

Last edited by Berni341 (2025-12-21 10:18:46)

post-factum · 2025-12-20 17:22:21

Merge request with the fix pending: https://gitlab.archlinux.org/archlinux/ … quests/457

rosenbaum · 2025-12-20 19:58:42

Matthl wrote:

If I apply the workaround and add the line above to the file /usr/lib/initcpio/install/sd-shutdown - will the file sd-shutdown be replaced with a future bugfix mkinitcpio update?
Or do I have to remember the fix and remove the line manually, then?

Any update to mkinitcpio that includes the newest sd-shutdown will overwrite your fix.

Gator · 2025-12-20 20:14:07

... Same here (freshly updated sd to 259.1):

... shutdown[1]: Failed to parse /proc/self/mountinfo: Operation not supported
... shutdown[1]: Unable to unmount file systems: Operation not supported
... shutdown[1]: Cannot enumerate swap partitions, no libmount support.
... shutdown[1]: Unable to deactivate swaps: Operation not supported
... shutdown[1]: Unable to finalize remaining file systems, swap devices, ignoring.

Right now tested and for me fixed by:

https://gitlab.archlinux.org/archlinux/ … /457/diffs

[DELL Latitude7280, homebrew 6.18.2, totally up-2-date Arch from scratch]

THX @foxboron

Matthl · 2025-12-20 20:50:57

rosenbaum wrote:

Any update to mkinitcpio that includes the newest sd-shutdown will overwrite your fix.

Thank you. Just saw the merge request with the changes in 'sd-shutdown'. Now I'm sure the file will get overridden.
Fix applied and no more error messages.

vbezhenar · Yesterday 11:05:43

What's the consequence of this issue? Can it cause data loss on shutdown/reboot? Should I patch sd-shutdown or install mkinitcpio from testing ASAP? I'm using NVME->LUKS->EXT4 for my root partition and NVME->FAT32 for by EFI partition.

Arch Linux

#1 2025-12-19 17:59:16

Unknown messages at shutdown after systemd 259.1 update

#2 2025-12-19 18:43:48

Re: Unknown messages at shutdown after systemd 259.1 update

#3 2025-12-19 19:43:07

Re: Unknown messages at shutdown after systemd 259.1 update

#4 2025-12-19 21:05:54

Re: Unknown messages at shutdown after systemd 259.1 update

#5 2025-12-19 21:17:37

Re: Unknown messages at shutdown after systemd 259.1 update

#6 2025-12-19 21:20:58

Re: Unknown messages at shutdown after systemd 259.1 update

#7 2025-12-19 22:51:47

Re: Unknown messages at shutdown after systemd 259.1 update

#8 2025-12-19 23:33:31

Re: Unknown messages at shutdown after systemd 259.1 update

#9 2025-12-20 00:22:47

Re: Unknown messages at shutdown after systemd 259.1 update

#10 2025-12-20 08:19:44

Re: Unknown messages at shutdown after systemd 259.1 update

#11 2025-12-20 10:13:27

Re: Unknown messages at shutdown after systemd 259.1 update

#12 2025-12-20 10:22:46

Re: Unknown messages at shutdown after systemd 259.1 update

#13 2025-12-20 10:25:21

Re: Unknown messages at shutdown after systemd 259.1 update

#14 2025-12-20 10:26:36

Re: Unknown messages at shutdown after systemd 259.1 update

#15 2025-12-20 10:32:18

Re: Unknown messages at shutdown after systemd 259.1 update

#16 2025-12-20 10:41:07

Re: Unknown messages at shutdown after systemd 259.1 update

#17 2025-12-20 11:08:13

Re: Unknown messages at shutdown after systemd 259.1 update

#18 2025-12-20 12:35:16

Re: Unknown messages at shutdown after systemd 259.1 update

#19 2025-12-20 13:53:18

Re: Unknown messages at shutdown after systemd 259.1 update

#20 2025-12-20 14:34:53

Re: Unknown messages at shutdown after systemd 259.1 update

#21 2025-12-20 17:22:21

Re: Unknown messages at shutdown after systemd 259.1 update

#22 2025-12-20 19:58:42

Re: Unknown messages at shutdown after systemd 259.1 update

#23 2025-12-20 20:14:07

Re: Unknown messages at shutdown after systemd 259.1 update

#24 2025-12-20 20:50:57

Re: Unknown messages at shutdown after systemd 259.1 update

#25 Yesterday 11:05:43

Re: Unknown messages at shutdown after systemd 259.1 update

Board footer