Hi folks,
Usually I try to solve my own issues, but I've been having quite a bit of trouble with this particular problem and I am looking for some assistance.
I've been using Proxmox for a while now and quite like it. As I've started to upgrade my hardware, I decided to integrate my VE with Network UPS Tools (NUT). I have a UPS, went through some tutorials on YouTube to shutdown Proxmox after it is on battery for too long. The shutdown script worked too well and turned the system off even if there was a little brown out, so that was resolved. Now, and I am not sure when the issue first started happening - potentially when I went from VE 7 to 8, Proxmox performs the NUT shutdown as expected, but the system hangs on a black screen with some text and does not shut the system down as it continues to draw power.
Some troubleshooting I've tried (not in any particular order):
- Changed the NUT shutdown script to different options (shutdown -h, shutdown now)
- Updated the BIOS
- Changed ACPI Sleep States in the BIOS
- Completely re-installed Proxmox with newest version on different storage
- Probably some more things that I have since forgotten
Despite the above, I am still unable to have the system fully shutdown as it usually turns up the message which I have attached to this post.
Some other information relating this issue:
- Virtual machines are using guest agent
- In order to shutdown the system, I must press and hold the power button on the case of the unit to fully have it power off
- This has nothing to do with NUT specifically. The system has this hanging problem if I put in the shutdown command in the CLI or use the GUI
- I do not believe this relates to the Virtual Machines shutting down. I turned off all virtual machines as a test one day before I shutdown the system and the system was still hanging on the message attached to this post
- When the system fails to power off and displays the message attached to this post, the Q-Code LED usually comes up as 05 which corresponds to the motherboard user manual which says 'System is entering S5 sleep state'
- Probably the weirdest part is if I attempt to do a shutdown and it fails to the point where I have to push the power button on the case like described above, turn on the machine and immediately shut it down again, it shuts down without any issue. Virtual Machines are running as per the automatic power on settings within the GUI and they are powered off by the OS before it shuts down itself. There are also no Q-Codes on the motherboard LED either.
The last part is why it has taken me so long to troubleshoot the issue. I usually go through this exercise of thinking there was an issue, "fix" the issue by making some configuration changes, testing by a reboot which would work. It seems that a reboot of the system followed by another shutdown (either by NUT or by CLI / GUI) works fine, so I thought that the issue was fixed, when in theory, it's not. Rinse and repeat until I figured out that I need to wait a day before I test as that's usually when the issue presents itself again.
It's almost like something is preventing it from shutting down and I am not sure where to even look anymore to resolve this issue.
I am currently running Proxmox with an ASUS WS X299 SAGE/10G motherboard with an Intel Core i9-7980XE CPU, not sure if that's relevant, but thought I would add it.
As such, if there's anything anyone can think of, I would be extremely grateful as I have been at this for a while and I am running out of ideas of what the issue could be.
Thanks!
Usually I try to solve my own issues, but I've been having quite a bit of trouble with this particular problem and I am looking for some assistance.
I've been using Proxmox for a while now and quite like it. As I've started to upgrade my hardware, I decided to integrate my VE with Network UPS Tools (NUT). I have a UPS, went through some tutorials on YouTube to shutdown Proxmox after it is on battery for too long. The shutdown script worked too well and turned the system off even if there was a little brown out, so that was resolved. Now, and I am not sure when the issue first started happening - potentially when I went from VE 7 to 8, Proxmox performs the NUT shutdown as expected, but the system hangs on a black screen with some text and does not shut the system down as it continues to draw power.
Some troubleshooting I've tried (not in any particular order):
- Changed the NUT shutdown script to different options (shutdown -h, shutdown now)
- Updated the BIOS
- Changed ACPI Sleep States in the BIOS
- Completely re-installed Proxmox with newest version on different storage
- Probably some more things that I have since forgotten
Despite the above, I am still unable to have the system fully shutdown as it usually turns up the message which I have attached to this post.
Some other information relating this issue:
- Virtual machines are using guest agent
- In order to shutdown the system, I must press and hold the power button on the case of the unit to fully have it power off
- This has nothing to do with NUT specifically. The system has this hanging problem if I put in the shutdown command in the CLI or use the GUI
- I do not believe this relates to the Virtual Machines shutting down. I turned off all virtual machines as a test one day before I shutdown the system and the system was still hanging on the message attached to this post
- When the system fails to power off and displays the message attached to this post, the Q-Code LED usually comes up as 05 which corresponds to the motherboard user manual which says 'System is entering S5 sleep state'
- Probably the weirdest part is if I attempt to do a shutdown and it fails to the point where I have to push the power button on the case like described above, turn on the machine and immediately shut it down again, it shuts down without any issue. Virtual Machines are running as per the automatic power on settings within the GUI and they are powered off by the OS before it shuts down itself. There are also no Q-Codes on the motherboard LED either.
The last part is why it has taken me so long to troubleshoot the issue. I usually go through this exercise of thinking there was an issue, "fix" the issue by making some configuration changes, testing by a reboot which would work. It seems that a reboot of the system followed by another shutdown (either by NUT or by CLI / GUI) works fine, so I thought that the issue was fixed, when in theory, it's not. Rinse and repeat until I figured out that I need to wait a day before I test as that's usually when the issue presents itself again.
It's almost like something is preventing it from shutting down and I am not sure where to even look anymore to resolve this issue.
I am currently running Proxmox with an ASUS WS X299 SAGE/10G motherboard with an Intel Core i9-7980XE CPU, not sure if that's relevant, but thought I would add it.
As such, if there's anything anyone can think of, I would be extremely grateful as I have been at this for a while and I am running out of ideas of what the issue could be.
Thanks!
