systemd-shutdown[1]: Failed to finalize DM devices, ignoring

B

Blacktime2

New Member
Oct 30, 2022
4
0
1
Hello,

Since installing and configuring my Proxmox server, I can't restart it without pressing the stop button because I get this message :
systemd-shutdown[1]: Failed to finalize DM devices, ignoring

Version info :

Code: 
root@serveur1:/etc/apt# pveversion --verbose
proxmox-ve: 7.2-1 (running kernel: 5.15.64-1-pve)
pve-manager: 7.2-11 (running version: 7.2-11/b76d3178)
pve-kernel-5.15: 7.2-13
pve-kernel-helper: 7.2-13
pve-kernel-5.15.64-1-pve: 5.15.64-1
pve-kernel-5.15.60-2-pve: 5.15.60-2
pve-kernel-5.15.60-1-pve: 5.15.60-1
pve-kernel-5.15.53-1-pve: 5.15.53-1
pve-kernel-5.15.30-2-pve: 5.15.30-3
ceph-fuse: 16.2.9-pve1
corosync: 3.1.5-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.24-pve1
libproxmox-acme-perl: 1.4.2
libproxmox-backup-qemu0: 1.3.1-1
libpve-access-control: 7.2-4
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.2-3
libpve-guest-common-perl: 4.1-4
libpve-http-server-perl: 4.1-4
libpve-storage-perl: 7.2-10
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 5.0.0-3
lxcfs: 4.0.12-pve1
novnc-pve: 1.3.0-3
proxmox-backup-client: 2.2.7-1
proxmox-backup-file-restore: 2.2.7-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.5.1
pve-cluster: 7.2-2
pve-container: 4.2-3
pve-docs: 7.2-2
pve-edk2-firmware: 3.20220526-1
pve-firewall: 4.2-6
pve-firmware: 3.5-6
pve-ha-manager: 3.4.0
pve-i18n: 2.7-2
pve-qemu-kvm: 7.0.0-4
pve-xtermjs: 4.16.0-1
qemu-server: 7.2-4
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.7.1~bpo11+1
vncterm: 1.7-1
zfsutils-linux: 2.1.6-pve1

Thanks a lot to those who will take the time to read this topic !
 
Same here, kernel Linux pve 5.15.74-1-pve #1 SMP PVE 5.15.74-1 (Mon, 14 Nov 2022 20:17:15 +0100) x86_64 GNU/Linux
 
I'm having the same issue, but within PBS. i've spun up a PBS instance on my PVE machine to do some initial testing before installing on bare metal. If I am in the VM console or sshed to the VM and intiate a reboot or poweroff command, the OS properly shutsdown completely or reboots normally. However if i use the PVE webUI shutdown button or reboot button, I get the same error message where the system shuts down but does not power off and I need to kill the shutdown command in the tasks at the bottom of the page, then initiate a stop to completely stop the VM. the PBS 2.3.1 is using kernel version 5.15.83. I also tried with the 5.15.74 version and the same issue happens on both. I also tried manually installing the qemu-guest-agent and making sure the qemu agent flag is checked in the VM settings but that doesn't seem to have helped. Not sure what is causing this hang
 
rchamp26 said:
I'm having the same issue, but within PBS. i've spun up a PBS instance on my PVE machine to do some initial testing before installing on bare metal. If I am in the VM console or sshed to the VM and intiate a reboot or poweroff command, the OS properly shutsdown completely or reboots normally. However if i use the PVE webUI shutdown button or reboot button, I get the same error message where the system shuts down but does not power off and I need to kill the shutdown command in the tasks at the bottom of the page, then initiate a stop to completely stop the VM. the PBS 2.3.1 is using kernel version 5.15.83. I also tried with the 5.15.74 version and the same issue happens on both. I also tried manually installing the qemu-guest-agent and making sure the qemu agent flag is checked in the VM settings but that doesn't seem to have helped. Not sure what is causing this hang
Click to expand...
just noticed today the the non subscription system updates resolved my vm shutdown issue. now the vms properly shutdown
 
I also have this problem, mine is version 7.4.3
watchdog: watchdog0: watchdog did not stop! systemd-shutdown[1]: failed to finalize DM devices, ignoring.
 
rchamp26 thank you!!! It's realy work. Manual:
1. Open nano /etc/apt/sources.list.d/pve-enterprise.list and comment #deb https://enterprise.proxmox.com stretch pve-enterprise like this.
2. Open nano /etc/apt/sources.list add ProxmoxVE 7: deb http://download.proxmox.com/debian/pve bullseye pve-no-subscription or ProxmoxVE 8: deb http://download.proxmox.com/debian/pve bookworm pve-no-subscription and deb http://security.debian.org/debian-security bookworm-security main contrib.
3. apt update && apt upgrade -y
 
Hello, this apt update && grade doesn't work for me.
I tried to update grub like this
Code: 
GRUB_CMDLINE_LINUX="quiet splash reboot=acpi"
and also reboot=bios, but either didn't help.
Shutdown works, reboot doesn't from GUI or CLI.

proxmox-ve: 8.1.0 (running kernel: 6.5.11-7-pve)
pve-manager: 8.1.3 (running version: 8.1.3/b46aac3b42da5d15)
proxmox-kernel-helper: 8.1.0
proxmox-kernel-6.5: 6.5.11-7
proxmox-kernel-6.5.11-7-pve-signed: 6.5.11-7
proxmox-kernel-6.5.11-4-pve-signed: 6.5.11-4
Click to expand...
....
 
For me this was sorted when I changed to UEFI, reboot works just like that. Machine is Dell T7920.
 
Last edited:
I also get the message: "systemd-shutdown[1]: Failed to finalize DM devices, ignoring", although it reboots normally.
I'm running a fresh install of proxmox-ve: 8.2.0 (running kernel: 6.8.12-1-pve)
 
Keek1981, is there a solution to fix these issues? I've just installed a fresh copy of PVE version 8.2.7 and still have the same problem. Many thanks

Watchdog: watchdog0: watchdog did not stop!
Proxmox system-shutdown [1]: failed to finalize dm devices, ignoring
 
Fresh install of PVE 8.3.0 and I still have this problem. I now have 2x Lenovo laptops, both on PVE 8.3.0 with this same issue. :(

Edit:
I followed this and it solved the problem for me on both laptops/PVE installs.
E

Post in thread '[SOLVED] Proxmox 8 - systemd-shutdown[1] - Failed to get MD_LEVEL property'

https://bugzilla.redhat.com/show_bug.cgi?id=1970610
https://bugs.gentoo.org/395203

Code: 
Edit the following files,
> /usr/lib/systemd/system-shutdown/mdadm.shutdown
> /lib/systemd/system-shutdown/mdadm.shutdown

Add the following:
/sbin/mdadm --wait-clean --scan
/sbin/mdadm -S -s
  • Like
 
Last edited:
Still running into this issue, none of the above worked for me. For me, I found that the issue may be related to GPU passthrough, as adding intel_iommu=on is what caused this issue to occur (confirmed with a fresh install). IOMMU is essential for this server though, and I've already tried blacklisting the GPUs, etc.
 
Hello,
I am having this issue. I started this thread https://forum.proxmox.com/threads/proxmox-ve-shutdown-does-not-poweroff-machine.160147/ but nobody answered.

Now I got access to the display, and it displayed this message:
"Failed to finalize DM devices, ignoring"
Next the screen goes dark and the PVE never shuts down, only by pressing the button.

I don't have GPU passthrough but I have HDD passthrough via virtio, but I always shut the VM first, that has the HDD, before issueing the shutdown command.

usuing init 0 or shutdown via gui gives the same results, doesn't shut down.
The "watchdog: watchdog0: watchdog did not stop!" message DOES NOT appear.

My proxmox version is updated, always updated to the last version.

What should I do?
Which solutions should I try? Are they effective?

Thank you.
 
You must log in or register to reply here.
Top Bottom