Proxmox freezes on an Intel NUC

steuerlexi

New Member
Jan 26, 2023
8
1
3
Hi community,

I have the problem that my Intel NUC is constantly freezing after a couple of hours without any reason. I thought it could be an hardware issue so I checked the memory with memtest86 and it did not show any errors. Then I checked the Crucial MX300 750gb SSD and updated it to the latest FW. But all of that did not help.

When it freezes only a hard reset will help. It won´t connect to the webservice, neither i can ping it or access via SSH. The entire system freezes completely.

Code:
Jan 26 14:52:45 pve pvedaemon[999]: <root@pam> end task UPID:pve:000051BB:0008E056:63D285AD:vncshell::root@pam: OK
Jan 26 14:52:45 pve systemd[20934]: Queued start job for default target Main User Target.
Jan 26 14:52:45 pve systemd[20934]: Created slice User Application Slice.
Jan 26 14:52:45 pve systemd[20934]: Reached target Paths.
Jan 26 14:52:45 pve systemd[20934]: Reached target Timers.
Jan 26 14:52:45 pve systemd[20934]: Listening on GnuPG network certificate management daemon.
Jan 26 14:52:45 pve systemd[20934]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).
Jan 26 14:52:45 pve systemd[20934]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
Jan 26 14:52:45 pve systemd[20934]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
Jan 26 14:52:45 pve systemd[20934]: Listening on GnuPG cryptographic agent and passphrase cache.
Jan 26 14:52:45 pve systemd[20934]: Reached target Sockets.
Jan 26 14:52:45 pve systemd[20934]: Reached target Basic System.
Jan 26 14:52:45 pve systemd[20934]: Reached target Main User Target.
Jan 26 14:52:45 pve systemd[20934]: Startup finished in 141ms.
Jan 26 14:52:45 pve systemd[1]: Started User Manager for UID 0.
Jan 26 14:52:45 pve systemd[1]: Started Session 27 of user root.
Jan 26 14:52:45 pve systemd-logind[672]: Session 27 logged out. Waiting for processes to exit.
Jan 26 14:59:58 pve pveproxy[1009]: worker exit
Jan 26 14:59:58 pve pveproxy[1007]: worker 1009 finished
Jan 26 14:59:58 pve pveproxy[1007]: starting 1 worker(s)
Jan 26 14:59:58 pve pveproxy[1007]: worker 22396 started
Jan 26 15:04:51 pve pvedaemon[999]: <root@pam> successful auth for user 'root@pam'
Jan 26 15:07:14 pve pveproxy[1008]: worker exit
Jan 26 15:07:14 pve pveproxy[1007]: worker 1008 finished
Jan 26 15:07:14 pve pveproxy[1007]: starting 1 worker(s)
Jan 26 15:07:14 pve pveproxy[1007]: worker 23775 started
Jan 26 15:17:01 pve CRON[25677]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Jan 26 15:17:01 pve CRON[25678]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Jan 26 15:17:01 pve CRON[25677]: pam_unix(cron:session): session closed for user root
Jan 26 15:53:44 pve pvedaemon[1001]: <root@pam> successful auth for user 'root@pam'
Jan 26 16:08:40 pve pvedaemon[1000]: <root@pam> successful auth for user 'root@pam'
-- Reboot --


I hope someone could help here.

Cheers
Alex
 
Hi,
did you try booting with a different kernel version? What is your pveversion -v?
 
No, how do I do it?

Code:
proxmox-ve: 7.3-1 (running kernel: 5.15.83-1-pve)
pve-manager: 7.3-4 (running version: 7.3-4/d69b70d4)
pve-kernel-helper: 7.3-2
pve-kernel-5.15: 7.3-1
pve-kernel-5.15.83-1-pve: 5.15.83-1
pve-kernel-5.15.74-1-pve: 5.15.74-1
ceph-fuse: 15.2.17-pve1
corosync: 3.1.7-pve1
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-pve2
libproxmox-acme-perl: 1.4.3
libproxmox-backup-qemu0: 1.3.1-1
libpve-access-control: 7.3-1
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.3-1
libpve-guest-common-perl: 4.2-3
libpve-http-server-perl: 4.1-5
libpve-storage-perl: 7.3-1
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.3.2-1
proxmox-backup-file-restore: 2.3.2-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.5.3
pve-cluster: 7.3-2
pve-container: 4.4-2
pve-docs: 7.3-1
pve-edk2-firmware: 3.20220526-1
pve-firewall: 4.2-7
pve-firmware: 3.6-2
pve-ha-manager: 3.5.1
pve-i18n: 2.8-1
pve-qemu-kvm: 7.1.0-4
pve-xtermjs: 4.16.0-1
qemu-server: 7.3-2
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.8.0~bpo11+2
vncterm: 1.7-1
zfsutils-linux: 2.1.7-pve3
 
ahh ok, I will connect a monitor to it and try that. Thank you
You might also leave the monitor connected while the system freezes, maybe you get some more information.
 
  • Like
Reactions: steuerlexi
I wasn´t at home yesterday and the system ran through since yesterday 4pm without any problems. It looks like it freezes when i use Home Assistant VM via Webservice. But when it run in idle everything seems to be fine.
 
ok, it freezed again. Now i am trying with a different kernel instead of kernel: 5.15.83-1-pve i will use 5.15.74
 
With the other Kernel it runs stable since yesterday. Could you please elaborate why this is?
could be a number of reasons. The kernel provides all the device drivers. The newer kernel might have a different driver or could have resolved a conflict of some sort or even be written to use less CPU cycles. I am still not convince your NUC wasn't over heating. Locking up while under load (while home assistant was running) vs not locking up at idle could be all about the processor load and heat build up.
 
Ok, now it died last night out of nowhere. There was no load on the system at all. I will exchange the RAM and harddrive and try to set it up fresh.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!