systemd-shutdown cannot detach DM

Status changed to 'Confirmed' because the bug affects multiple users.

please reboot with this kernel boot parameter added:

systemd.log_level=debug

Then let the system boot up, and then perform a shutdown, to reproduce the problem. Then start the system back up (you can remove the kernel boot parameter) and capture the previous boot's journal, which should include the problem reproduction while debug is enabled; you can use the command:

$ journalctl -k -b -1 > /tmp/lp1905166.log

which will capture the log output from the previous boot.

Have the same problem, here is the log:

> Have the same problem, here is the log:

that log doesn't show the reported problematic log messages

Same issue here.
5.8.0-36-generic #40~20.04.1-Ubuntu SMP Wed Jan 6 10:15:55 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

I had issue with glxgears and some other apps that failed to start. When restarting then the computer(Lenovo P73) hanged. I think the same hanging behaviour has happened before.

Not sure if this OpenGL issue is somehow related.
pi-imager.desktop[624532]: Failed to create OpenGL context for format QSurfaceFormat(version 2.0, options QFlags<QSurfaceFormat::FormatOption>(), depthBufferSize 24, redBufferSize -1, greenBufferSize -1, blueBufferSize -1, alphaBufferSize -1, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 1, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::NoProfile)

The message:
systemd-shutdown[1]: Could not detach DM /dev/dm-0: Device or resource busy
systemd-shutdown[1]: Failed to finalize DM devices, ignoring

is not in the logs, idk why, here are some more logs, the image shows the message and the time before. I attached also a longer log file and kern log, if it helps..?

for those affected, does this happen every boot/shutdown?

is this a 'standard' installation, using the standard iso?

what do you have mounted? what's the output of 'mount' and the output of 'lsblk'?

> for those affected, does this happen every boot/shutdown?

Yes, I'm getting the following messages on Hirsute at the end of every shut down (or reboot):

[ OK ] Reached target Reboot.
[ timestamp] XFS: attr2 mount option is deprecated.
[ timestamp] sd-umoun[2337]: Failed to unmount /oldroot: Device or resource busy
[ timestamp] sd-umoun[2337]: Failed to unmount /oldroot/sys: Device or resource busy
[ timestamp] shutdown[1]: Could not detach DM /dev/dm-1: Device or resource busy
[ timestamp] shutdown[1]: Could not detach DM /dev/dm-0: Device or resource busy
[ timestamp] shutdown[1]: Failed to finalize file systems, DM devices, ignoring.

> is this a 'standard' installation, using the standard iso?

Yes, this was installed using a nightly hirsute-live-server-amd64.iso, with disk encryption enabled during installation.

> what do you have mounted? what's the output of 'mount' and the output of 'lsblk'?

# mount
...
/dev/mapper/ubuntu--vg-ubuntu--lv on / type xfs (rw,noatime,attr2,inode64,logbufs=8,logbsize=32k,noquota)
/dev/nvme0n1p2 on /boot type ext4 (rw,relatime)
/dev/nvme0n1p1 on /boot/efi type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
...

Full mount output at https://gist.githubusercontent.com/joliss/c13e728ee039a2440e98f7ba6dd7ecd8/raw/25678bdaa17707a41b81b61c0fc648e01968ca90/mount

# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
loop0 7:0 0 99.2M 1 loop /snap/core/10908
loop1 7:1 0 25.9M 1 loop /snap/heroku/4037
loop2 7:2 0 72M 1 loop /snap/lxd/19766
loop3 7:3 0 55.5M 1 loop /snap/core18/1988
loop4 7:4 0 32.3M 1 loop /snap/snapd/11107
loop5 7:5 0 32.3M 1 loop /snap/snapd/11402
loop6 7:6 0 68.7M 1 loop /snap/lxd/19823
nvme0n1 259:0 0 1.8T 0 disk
├─nvme0n1p1 259:1 0 512M 0 part /boot/efi
├─nvme0n1p2 259:2 0 1G 0 part /boot
└─nvme0n1p3 259:3 0 1.8T 0 part
  └─dm_crypt-0 253:0 0 1.8T 0 crypt
    └─ubuntu--vg-ubuntu--lv 253:1 0 1.8T 0 lvm /

> [ timestamp] sd-umoun[2337]: Failed to unmount /oldroot: Device or resource busy
> [ timestamp] sd-umoun[2337]: Failed to unmount /oldroot/sys: Device or resource busy

um, your mount output doesn't show any mounts at those dirs...you sure you're getting those messages at shutdown? ;-)

Status changed to 'Confirmed' because the bug affects multiple users.

This actually appears to be bug(s) in the 'finalrd', not systemd; probably bug 1920107 is a dup of this one

Status changed to 'Confirmed' because the bug affects multiple users.

I am having this issue too. With failing to finalize file systems.

I can see these messages that I think could be releated:

May 02 07:25:59 server lvm[556]: 1 logical volume(s) in volume group "vg" unmonitored
May 02 07:25:59 server systemd[1]: lvm2-monitor.service: Succeeded.

Perhaps my volume group is "unmonitored" means that it will not be included in the shutdown process?

I did have the same issue with lvm2:

systemd-shutdown[1]: Could not detach DM /dm/dm-2: Device or resource busy
systemd-shutdown[1]: Could not detach DM /dm/dm-1: Device or resource busy
systemd-shutdown[1]: Could not detach DM /dm/dm-0: Device or resource busy
systemd-shutdown[1]: Failed ot finalize DM devices, ignoring.

Solved it by installing dracut-core (sudo apt install dracut-core) which provides the dracut-shutdown service for systemd: https://manpages.debian.org/stretch/dracut-core/dracut-shutdown.service.8.en.html

Same issue:

Linux kythera-Precision-5570 6.2.0-31-generic #31~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Wed Aug 16 13:45:26 UTC 2 x86_64 x86_64 x86_64 GNU/Linux