Proxmox 7.1 immediately reboots after shutdown -h now

[idh2021]

I have successfully installed Proxmox on various hardware (Dell T110ii, Fujitsu TX100, HP N36L, Dell T20) to replace VMWare ESXi.

Usually the system turns off after "shutdown -h now".

The Dell T20 was an anomaly and rebooted instead. This was eventually solved by disabling USB3 ports, but why was this necessary? The other hardware has no USB3 and hence probably the lack of a problem.

I now have a HP T630 thin client with the same rebooting problem but no option to disable the USB3 ports. I have just installed Debian 11.3 and shutdown works as expected.

So why does Proxmox not behave like its Debian base? "Proxmox VE is based on Debian."

I am reluctant to try to install Proxmox on top of the working Debian 11, since a previous attempt on other hardware did not succeed.

I would prefer to stick with Proxmox so can anyone suggest what is needed to fix the problem?

I can reinstall Proxmox to provide logs, etc

 

[shrdlicka]

Hi,
have you tried to disable "Wake on LAN" or other "Wake on X" settings in bios?

Can you show us the boot log maybe?

sudo journalctl  -b -1 -e

 

[MightySlaytanic]

Hi,
have you tried to disable "Wake on LAN" or other "Wake on X" settings in bios?

Can you show us the boot log maybe?

sudo journalctl  -b -1 -e

I'm having the same problem on Proxmox VE 7.2 on Intel NUC 10th Gen. I need Wake on Line to wakeup my lab remotely, is there anything else I can try to do a power down without automatic restart? I know that in the bios you can setup the wake on lan from different states, should I try to change that parameter? If I remove the power and re-connect the Intel NUC is not powered on by anything on the net (I can see the ethernet card alive but the NUC is not woken up), so there must be something related to how the system is powered down. Right after a fresh installation of PVE 7.2 I've powered down the NUC at least twice without problems to try waking up remotely, so maybe is something introduced by some update I did after the installation? Any suggestion?

Here it says powered off but it automatically restart immediately after.
$ sudo journalctl -b -1 -e Nov 09 00:14:12 pve systemd[1]: systemd-fsck@dev-disk-by\x2duuid-A8FC\x2d3C79.service: Succeeded. Nov 09 00:14:12 pve systemd[1]: Stopped File System Check on /dev/disk/by-uuid/A8FC-3C79. Nov 09 00:14:12 pve systemd[1]: Removed slice system-systemd\x2dfsck.slice. Nov 09 00:14:12 pve systemd[1]: Stopped target Local File Systems (Pre). Nov 09 00:14:12 pve systemd[1]: Stopping Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling... Nov 09 00:14:12 pve systemd[1]: systemd-tmpfiles-setup-dev.service: Succeeded. Nov 09 00:14:12 pve systemd[1]: Stopped Create Static Device Nodes in /dev. Nov 09 00:14:12 pve systemd[1]: systemd-sysusers.service: Succeeded. Nov 09 00:14:12 pve systemd[1]: Stopped Create System Users. Nov 09 00:14:12 pve systemd[1]: systemd-remount-fs.service: Succeeded. Nov 09 00:14:12 pve systemd[1]: Stopped Remount Root and Kernel File Systems. Nov 09 00:14:12 pve dmeventd[510]: No longer monitoring thin pool pve-data-tpool. Nov 09 00:14:12 pve lvm[1650]: 13 logical volume(s) in volume group "pve" unmonitored Nov 09 00:14:12 pve systemd[1]: lvm2-monitor.service: Succeeded. Nov 09 00:14:12 pve systemd[1]: Stopped Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling. Nov 09 00:14:12 pve systemd[1]: Stopping Device-mapper event daemon... Nov 09 00:14:12 pve dmeventd[510]: dmeventd detected break while being idle for 0 second(s), exiting. Nov 09 00:14:12 pve dmeventd[510]: dmeventd shutting down. Nov 09 00:14:12 pve systemd[1]: dm-event.service: Succeeded. Nov 09 00:14:12 pve systemd[1]: Stopped Device-mapper event daemon. Nov 09 00:14:12 pve systemd[1]: Reached target Shutdown. Nov 09 00:14:12 pve systemd[1]: Reached target Final Step. Nov 09 00:14:12 pve systemd[1]: systemd-poweroff.service: Succeeded. Nov 09 00:14:12 pve systemd[1]: Finished Power-Off. Nov 09 00:14:12 pve systemd[1]: Reached target Power-Off. Nov 09 00:14:12 pve systemd[1]: Shutting down. Nov 09 00:14:12 pve systemd-shutdown[1]: Syncing filesystems and block devices. Nov 09 00:14:12 pve systemd-shutdown[1]: Sending SIGTERM to remaining processes... Nov 09 00:14:12 pve systemd-journald[495]: Journal stopped

Update: problem disappeared after adding the following in /etc/network/interfaces, maybe WOL parameters where reset to something different than g (wake only with Magic Packet) and they were set to wake up even with ARP/Ping requests:

iface eno1 inet manual
    ethernet-wol g

 

[ukro]

+1 Same here, and ethernet-wol g didn't help.

Jan 16 12:02:23 node systemd[1]: Stopping iSCSI initiator daemon (iscsid)...
Jan 16 12:02:23 node iscsid[1736]: iscsid shutting down.
Jan 16 12:02:23 node systemd[1]: iscsid.service: Succeeded.
Jan 16 12:02:23 node systemd[1]: Stopped iSCSI initiator daemon (iscsid).
Jan 16 12:02:23 node systemd[1]: Stopped target Network is Online.
Jan 16 12:02:23 node systemd[1]: Stopped target Network.
Jan 16 12:02:23 node systemd[1]: Stopping Network initialization...
Jan 16 12:02:23 node networking[6517]: networking: Skipping deconfiguring network interfaces
Jan 16 12:02:23 node systemd[1]: networking.service: Succeeded.
Jan 16 12:02:23 node systemd[1]: Stopped Network initialization.
Jan 16 12:02:23 node systemd[1]: Stopped target Local File Systems.
Jan 16 12:02:23 node systemd[1]: Unmounting /dsbackup...
Jan 16 12:02:23 node systemd[1]: systemd-sysctl.service: Succeeded.
Jan 16 12:02:23 node systemd[1]: Stopped Apply Kernel Variables.
Jan 16 12:02:23 node systemd[1]: systemd-modules-load.service: Succeeded.
Jan 16 12:02:23 node systemd[1]: Stopped Load Kernel Modules.
Jan 16 12:02:23 node systemd[1]: dsbackup.mount: Succeeded.
Jan 16 12:02:23 node systemd[1]: Unmounted /dsbackup.
Jan 16 12:02:23 node systemd[1]: Stopped target Local File Systems (Pre).
Jan 16 12:02:23 node systemd[1]: Reached target Unmount All Filesystems.
Jan 16 12:02:23 node systemd[1]: Stopping Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling...
Jan 16 12:02:23 node systemd[1]: systemd-tmpfiles-setup-dev.service: Succeeded.
Jan 16 12:02:23 node systemd[1]: Stopped Create Static Device Nodes in /dev.
Jan 16 12:02:23 node systemd[1]: systemd-sysusers.service: Succeeded.
Jan 16 12:02:23 node systemd[1]: Stopped Create System Users.
Jan 16 12:02:23 node systemd[1]: systemd-remount-fs.service: Succeeded.
Jan 16 12:02:23 node systemd[1]: Stopped Remount Root and Kernel File Systems.
Jan 16 12:02:23 node lvm[6521]:   7 logical volume(s) in volume group "pve" unmonitored
Jan 16 12:02:23 node dmeventd[554]: No longer monitoring thin pool pve-data-tpool.
Jan 16 12:02:23 node systemd[1]: lvm2-monitor.service: Succeeded.
Jan 16 12:02:23 node systemd[1]: Stopped Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling.
Jan 16 12:02:23 node systemd[1]: Stopping Device-mapper event daemon...
Jan 16 12:02:23 node dmeventd[554]: dmeventd detected break while being idle for 0 second(s), exiting.
Jan 16 12:02:23 node dmeventd[554]: dmeventd shutting down.
Jan 16 12:02:23 node systemd[1]: dm-event.service: Succeeded.
Jan 16 12:02:23 node systemd[1]: Stopped Device-mapper event daemon.
Jan 16 12:02:23 node systemd[1]: Reached target Shutdown.
Jan 16 12:02:23 node systemd[1]: Reached target Final Step.
Jan 16 12:02:23 node systemd[1]: systemd-poweroff.service: Succeeded.
Jan 16 12:02:23 node systemd[1]: Finished Power-Off.
Jan 16 12:02:23 node systemd[1]: Reached target Power-Off.
Jan 16 12:02:23 node systemd[1]: Shutting down.
Jan 16 12:02:23 node systemd-shutdown[1]: Syncing filesystems and block devices.
Jan 16 12:02:23 node systemd-shutdown[1]: Sending SIGTERM to remaining processes...
Jan 16 12:02:23 node systemd-journald[539]: Journal stopped

When shutting down with -h it is saying
Failed to finalize DM devices, ignoring.
And then just rebooting after 1 minute
Wake on lan in BIOS disabled.
Host: HP ML110 Gen9

 

[ukro]

i dont know what i did, but now its shutting down even without -h
I was playing with gpu passthrough editing grub rebooting all the time, settings some blacklist, a realy dont know what i did to make it work LOL huraaaaay

 

[proxmix]

Same here. Local scenario/solution: My pve has an Eaton UPS attached via USB, which causes the reboot, that in fact is a "wakeup". After disabling "USB S5 Wakeup Support" in the mainboard's BIOS shutdown -h works fine again.