Proxmox Rebooting constantly on BOXNUC7I5BNK i5 NUC

Payee6908

New Member
Jan 14, 2024
8
0
1
Hi There,
I instal proxmox on an Intel NUC BOXNUC7I5BNK i5.
After running a few VMS i find the NUC get hot and reboots.

I assume this may be a driver issue?
Anyone been able to fix this?
 
Hello

Can you send me your journalctl -b please?

Regards
Philipp
 
programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Wed Sep 20 22:36:03 AEST 2023 on pts/0
root@proxmox:~# journalctl -b
Sep 20 22:15:14 proxmox kernel: Linux version 6.5.11-4-pve (fgruenbichler@yuna) (gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Bi>
Sep 20 22:15:14 proxmox kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-6.5.11-4-pve root=/dev/mapper/pve-root ro quiet
Sep 20 22:15:14 proxmox kernel: KERNEL supported cpus:
Sep 20 22:15:14 proxmox kernel: Intel GenuineIntel
Sep 20 22:15:14 proxmox kernel: AMD AuthenticAMD
Sep 20 22:15:14 proxmox kernel: Hygon HygonGenuine
Sep 20 22:15:14 proxmox kernel: Centaur CentaurHauls
Sep 20 22:15:14 proxmox kernel: zhaoxin Shanghai
Sep 20 22:15:14 proxmox kernel: BIOS-provided physical RAM map:
Sep 20 22:15:14 proxmox kernel: BIOS-e820: [mem 0x0000000000000000-0x0000000000057fff] usable
Sep 20 22:15:14 proxmox kernel: BIOS-e820: [mem 0x0000000000058000-0x0000000000058fff] reserved
Sep 20 22:15:14 proxmox kernel: BIOS-e820: [mem 0x0000000000059000-0x000000000009efff] usable
Sep 20 22:15:14 proxmox kernel: BIOS-e820: [mem 0x000000000009f000-0x00000000000fffff] reserved
Sep 20 22:15:14 proxmox kernel: BIOS-e820: [mem 0x0000000000100000-0x000000006e9a6fff] usable
Sep 20 22:15:14 proxmox kernel: BIOS-e820: [mem 0x000000006e9a7000-0x000000006e9a7fff] ACPI NVS
Sep 20 22:15:14 proxmox kernel: BIOS-e820: [mem 0x000000006e9a8000-0x000000006e9a8fff] reserved
Sep 20 22:15:14 proxmox kernel: BIOS-e820: [mem 0x000000006e9a9000-0x000000007a481fff] usable
Sep 20 22:15:14 proxmox kernel: BIOS-e820: [mem 0x000000007a482000-0x000000007a7c0fff] reserved
Sep 20 22:15:14 proxmox kernel: BIOS-e820: [mem 0x000000007a7c1000-0x000000007a7fefff] ACPI data
Sep 20 22:15:14 proxmox kernel: BIOS-e820: [mem 0x000000007a7ff000-0x000000007afd6fff] ACPI NVS
Sep 20 22:15:14 proxmox kernel: BIOS-e820: [mem 0x000000007afd7000-0x000000007b399fff] reserved
Sep 20 22:15:14 proxmox kernel: BIOS-e820: [mem 0x000000007b39a000-0x000000007b3fdfff] type 20
Sep 20 22:15:14 proxmox kernel: BIOS-e820: [mem 0x000000007b3fe000-0x000000007b3fefff] usable
Sep 20 22:15:14 proxmox kernel: BIOS-e820: [mem 0x000000007b400000-0x000000007fffffff] reserved
Sep 20 22:15:14 proxmox kernel: BIOS-e820: [mem 0x00000000e0000000-0x00000000efffffff] reserved
Sep 20 22:15:14 proxmox kernel: BIOS-e820: [mem 0x00000000fe000000-0x00000000fe010fff] reserved
Sep 20 22:15:14 proxmox kernel: BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
Sep 20 22:15:14 proxmox kernel: BIOS-e820: [mem 0x00000000fed00000-0x00000000fed00fff] reserved
Sep 20 22:15:14 proxmox kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
Sep 20 22:15:14 proxmox kernel: BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Sep 20 22:15:14 proxmox kernel: BIOS-e820: [mem 0x0000000100000000-0x000000107effffff] usable
lines 1-31
 
Hi There,
I instal proxmox on an Intel NUC BOXNUC7I5BNK i5.
After running a few VMS i find the NUC get hot and reboots.

I assume this may be a driver issue?
Anyone been able to fix this?

Do you happen to have IRQ .... nobody cared in dmesg output?
 
Hey, sorry, my bad. I mend journalctl -b -1 to show the last boot (where it crashed)
 
I'm not sure whether there will be a follow-up here, but just in case someone finds this later. On some of the NUCs there were issues with cstates on some kernels, it was however mostly resulting in freezes and there was nothing telling prior to it in the logs. Quick blind check was to have intel_idle.max_cstate=1 and then try different kernels, possibly disable hyperthreading for testing.

The other thing that I have had happen was the onboard audio card sit on IRQ that was shared with SSD. Also nothing telling in the log except that soon after boot one would see irq XX: nobody cared (try booting with the "irqpoll" option) in the journalctl -k even on currently still running system. A quick look at lspci -vv would show which is which and one gets the idea. Disabling onboard devices would help.

The OP, however, had an RTC issue (separate post) yesterday, so would not be surprised if that was related to that as well.
 
Last edited:
  • Like
Reactions: helplessbadger
Hey, sorry, my bad. I mend journalctl -b -1 to show the last boot (where it crashed)
Still getting crashes, this is the output of the new command.




Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Wed Sep 27 21:03:07 AEST 2023 on pts/0
root@proxmox:~# journalctl -b -1
Sep 20 22:15:14 proxmox kernel: Linux version 6.5.11-4-pve (fgruenbichler@yuna) (gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Bi>
Sep 20 22:15:14 proxmox kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-6.5.11-4-pve root=/dev/mapper/pve-root ro quiet
Sep 20 22:15:14 proxmox kernel: KERNEL supported cpus:
Sep 20 22:15:14 proxmox kernel: Intel GenuineIntel
Sep 20 22:15:14 proxmox kernel: AMD AuthenticAMD
Sep 20 22:15:14 proxmox kernel: Hygon HygonGenuine
Sep 20 22:15:14 proxmox kernel: Centaur CentaurHauls
Sep 20 22:15:14 proxmox kernel: zhaoxin Shanghai
Sep 20 22:15:14 proxmox kernel: BIOS-provided physical RAM map:
Sep 20 22:15:14 proxmox kernel: BIOS-e820: [mem 0x0000000000000000-0x0000000000057fff] usable
Sep 20 22:15:14 proxmox kernel: BIOS-e820: [mem 0x0000000000058000-0x0000000000058fff] reserved
Sep 20 22:15:14 proxmox kernel: BIOS-e820: [mem 0x0000000000059000-0x000000000009efff] usable
Sep 20 22:15:14 proxmox kernel: BIOS-e820: [mem 0x000000000009f000-0x00000000000fffff] reserved
Sep 20 22:15:14 proxmox kernel: BIOS-e820: [mem 0x0000000000100000-0x000000006e9a6fff] usable
Sep 20 22:15:14 proxmox kernel: BIOS-e820: [mem 0x000000006e9a7000-0x000000006e9a7fff] ACPI NVS
Sep 20 22:15:14 proxmox kernel: BIOS-e820: [mem 0x000000006e9a8000-0x000000006e9a8fff] reserved
Sep 20 22:15:14 proxmox kernel: BIOS-e820: [mem 0x000000006e9a9000-0x000000007a481fff] usable
Sep 20 22:15:14 proxmox kernel: BIOS-e820: [mem 0x000000007a482000-0x000000007a7c0fff] reserved
Sep 20 22:15:14 proxmox kernel: BIOS-e820: [mem 0x000000007a7c1000-0x000000007a7fefff] ACPI data
Sep 20 22:15:14 proxmox kernel: BIOS-e820: [mem 0x000000007a7ff000-0x000000007afd6fff] ACPI NVS
Sep 20 22:15:14 proxmox kernel: BIOS-e820: [mem 0x000000007afd7000-0x000000007b399fff] reserved
Sep 20 22:15:14 proxmox kernel: BIOS-e820: [mem 0x000000007b39a000-0x000000007b3fdfff] type 20
Sep 20 22:15:14 proxmox kernel: BIOS-e820: [mem 0x000000007b3fe000-0x000000007b3fefff] usable
Sep 20 22:15:14 proxmox kernel: BIOS-e820: [mem 0x000000007b400000-0x000000007fffffff] reserved
Sep 20 22:15:14 proxmox kernel: BIOS-e820: [mem 0x00000000e0000000-0x00000000efffffff] reserved
Sep 20 22:15:14 proxmox kernel: BIOS-e820: [mem 0x00000000fe000000-0x00000000fe010fff] reserved
Sep 20 22:15:14 proxmox kernel: BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
Sep 20 22:15:14 proxmox kernel: BIOS-e820: [mem 0x00000000fed00000-0x00000000fed00fff] reserved
Sep 20 22:15:14 proxmox kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
Sep 20 22:15:14 proxmox kernel: BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Sep 20 22:15:14 proxmox kernel: BIOS-e820: [mem 0x0000000100000000-0x000000107effffff] usable
Sep 20 22:15:14 proxmox kernel: NX (Execute Disable) protection: active
Sep 20 22:15:14 proxmox kernel: efi: EFI v2.5 by American Megatrends
Sep 20 22:15:14 proxmox kernel: efi: ACPI 2.0=0x7a7cd000 ACPI=0x7a7cd000 SMBIOS=0x7b30b000 SMBIOS 3.0=0x7b30a000 ESRT=0x7b3056>

root@proxmox:~#
 
Hello

You actually did only provide the first view lines of the log. However, since this states that the log starts at Sept 2023, we may, can skip some of it.

Can you issue journalctl --since '2024-03-11' > $(hostname)-journal.txt? This will generate a text file containing the logs. Can you attach this here?

Regards
Philipp
 
My server did the same ( or at least I think so ). I use Corsair Commander Pro to control the speed of ventilators. After speeding it up CPU is not getting hot and do not do auto system reboot by hardware.

Try to limit CPU speed if you cannot cool your NUC.
 

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!