Proxmox is inaccessible in 1h

C

Cyrille276

New Member
Apr 18, 2025
4
0
1
Hello,
I have installed Proxmox VE, with a single virtual machine (OMV).
However, after about an hour of use, the system becomes inaccessible. It doesn't shut down and stays on displaying “pve login:”.
I then have to restart the server, which restores the situation... for about an hour.
Do you have a solution to this problem?
Thanks
 
A little difficult to be able to help you without details.
Have you tried logging into the proxmox node console and see if there were any errors of some sort or a crash ?
Usually it could be hardware problems on the node. Maybe some faulty ram or storage problems ?
 
I reinstalled Proxmox. It’s a bit better—it now runs for about 10 hours, but the issue still persists.
I ran a MemTest86 for 3 hours without any errors.
My hard drives are in good health, as they work fine on another operating system.
I just reinstalled Proxmox using a different USB stick, created with another tool and a fresh ISO.
Now I’m waiting to see if this resolves the issue.

In any case, being able to restore the VM in under a minute is truly amazing.

thanks
 
Last edited:
It just crashed again, I think I’m going to give up.
Is there any incompatibility between Proxmox and my NUC NUC8i5BEK – Intel® NUC Mini PC i5-8259U?
Are there any BIOS settings I should configure?
Just to clarify: it doesn’t reboot, it completely freezes.
 
Last edited:
Cyrille276 said:
Is there any incompatibility between Proxmox and my NUC NUC8i5BEK – Intel® NUC Mini PC i5-8259U?
Click to expand...
There is/was crash in headless.
Buy and plug a HDMI Dummy should fix it.

J

Thread 'Intel NUC kit NUC7i7DNHE freezes after update to Proxmox 8.0.3'

Updated my cluster (3 Nodes) to Proxmox 8.0.3.

One of the Nodes is an Intel NUC kit NUC7i7DNHE. This Node dies within a couple of minutes. Than it will restart a number of times and in then it is fully dead.

I updated the BIOS to the latest version but the behavior did not change.

When I pin the kernel to 5.15.107-2-pve the system functions properly.

How can I solve this issue.

And what is the impact of running the 5.15.x kernel on one (1) Node while the other Nodes are on 6.2.16-3.

Will I still receive kernel updates?

---
John
 
  • Make sure, the bios/UEFI and all other firmwares (e.g.: SSD(s)) is/are up-to-date.
    • First of all, sorry for my English — I'm French.
      I just updated my BIOS from version v89 to v95.
  • Install the corresponding microcode package: [1].
    • As for the microcode, it wasn’t installed before, but after updating the BIOS, I now get: Mitigation; Microcode.
  • Check the syslog.
    • I don’t know how to inspect the syslog.
  • Monitor temperatures.
    • Temperatures are fine.
  • Try the opt-in kernel: [2].
    • I don’t understand what you mean by "Try the opt-in kernel: [2]".
  • See, if the same happens with another Linux distribution and maybe even Windows.
    • I had OMV running for a month without any issues on this system.
  • There is/was crash in headless.
    • I also don’t understand what you mean by "crash in headless".
  • Buy and plug a HDMI Dummy should fix it.
    • Are you suggesting I use a dummy display emulator?
      For now, I’ve kept my monitor connected to see what happens.
 
You must log in or register to reply here.
Top Bottom