You are not logged in.

#1 2024-11-16 02:36:25

OIhfes
Member
Registered: 2024-01-17
Posts: 14

[SOLVED]Encounter "Could not detach DM ..." in shutdown after systemd

My computer has two partitions, one is the ESP partition for storaging EFI files, and another is the LUKS2 partition (Btrfs on LUKS).
I use UKI as the EFI file (with the kernel parameter "rd.luks.name=luksuuid=root root=/dev/mapper/root" to let the systemd based initramfs decrypt the LUKS2 partition and mount it as rootfs)
These works as expected.
However, after I upgrade the systemd from 256.7-1 to 256.8-1, there are some error messages when shutdown:

shutdown[1]: Could not detach DM /dev/dm-0: Device or resource busy
shutdown[1]: Unable to finalize remaining DM devices, ignoring.

(These error messages only come out with systemd 256.8-1, 256.7-1 doesn't come out these error messages)
Do you have the same issue after upgrading systemd to 256.8-1 so I can confirm that this is might due to the systemd's initial error rather than my own config's error before I reporting to the upstreaming.

Last edited by OIhfes (2024-11-16 08:20:08)

Offline

#2 2024-11-16 08:19:29

OIhfes
Member
Registered: 2024-01-17
Posts: 14

Re: [SOLVED]Encounter "Could not detach DM ..." in shutdown after systemd

After some debug between 256.7-1 and 256.8-1 with this way https://freedesktop.org/wiki/Software/s … wnproblems
I just found that actually they have no difference but the 256.8-1 just output the message, they all unable to detach DM /dev/dm-0 beacuse of "that backs the OS itself, skipping." which means this is working as expected not a real error.

And this is part of the shutdown log looks like:

[   53.884700] systemd-shutdown[1]: All filesystems unmounted.
[   53.884704] systemd-shutdown[1]: Deactivating swaps.
[   53.884717] systemd-shutdown[1]: All swaps deactivated.
[   53.884719] systemd-shutdown[1]: Detaching loop devices.
[   53.885781] systemd-shutdown[1]: All loop devices detached.
[   53.885783] systemd-shutdown[1]: Stopping MD devices.
[   53.885835] systemd-shutdown[1]: All MD devices stopped.
[   53.885836] systemd-shutdown[1]: Detaching DM devices.
[   53.885964] systemd-shutdown[1]: Not detaching DM /dev/dm-0 that backs the OS itself, skipping.
[   53.885966] systemd-shutdown[1]: Not all DM devices detached, 1 left.
[   53.885968] systemd-shutdown[1]: Couldn't finalize remaining  DM devices, trying again.
[   53.885975] systemd-shutdown[1]: Failed to open watchdog device auto.
[   53.886011] systemd-shutdown[1]: Detaching DM devices.
[   53.886140] systemd-shutdown[1]: Not detaching DM /dev/dm-0 that backs the OS itself, skipping.
[   53.886142] systemd-shutdown[1]: Not all DM devices detached, 1 left.
[   53.886143] systemd-shutdown[1]: Cannot finalize remaining DM devices, continuing.
[   53.886373] systemd-shutdown[1]: Successfully forked off '(sd-exec-strv)' as PID 1922.
[   53.886513] (sd-exec-strv)[1922]: About to execute /usr/lib/systemd/system-shutdown/debug.sh (null)
[   53.886644] (sd-exec-strv)[1922]: Successfully forked off '(direxec)' as PID 1923.
[   53.886655] (sd-exec-strv)[1922]: About to execute /usr/lib/systemd/system-shutdown/fwupd.shutdown (null)
[   53.886804] (sd-exec-strv)[1922]: Successfully forked off '(direxec)' as PID 1924.
[   53.886812] (sd-exec-strv)[1922]: About to execute /usr/lib/systemd/system-shutdown/mdadm.shutdown (null)
[   53.886951] (sd-exec-strv)[1922]: Successfully forked off '(direxec)' as PID 1925.

Offline

Board footer

Powered by FluxBB