ProxMox Virtual Environment 8.4.0 Device Randomly Shutsdown without reason

W

Wusaru

New Member
Jun 10, 2025
5
1
3
Hello,

I run ProxMox Virtual Environment 8.4.0 on a TRIGKEY Key-N150 Mini PC, Intel Twin Lake N150 (4C/4T, bis zu 3,60 GHz) Mini Computer, 16 GB DDR4, 500 GB SSD M.2 PCIe x4, Dual HDMI/Zwei LAN 1000M,WiFi5,Bluetooth5.0 Device

It worked like a charm for 10 days, but now suddenly I wake up and try to reach the service proxmox or the running vm both offline. I walk to the server and check and it is shutdown for some reason. 2 days later it happened again. I have no clue why this happens.

In these logs you can see the server last writing a log at 4:31 then I turned it back on at 15:37:20 by hitting the power button manually. The proxmox server and the vm both shut down.
journalctl:

Jun 10 01:17:01 mov CRON[285373]: pam_unix(cron:session): session closed for user root
Jun 10 01:28:15 mov systemd[1]: Starting pve-daily-update.service - Daily PVE download activities...
Jun 10 01:28:19 mov pveupdate[287140]: <root@pam> starting task UPID:mov:000461A9:00B240CD:68476E12:aptupdate::root@pam:
Jun 10 01:28:21 mov pveupdate[287145]: command 'apt-get update' failed: exit code 100
Jun 10 01:28:21 mov pveupdate[287140]: command 'apt-get update' failed: exit code 100
Jun 10 01:28:21 mov pveupdate[287140]: <root@pam> end task UPID:mov:000461A9:00B240CD:68476E12:aptupdate::root@pam: command 'apt-get update' failed: exit code 100
Jun 10 01:28:21 mov systemd[1]: pve-daily-update.service: Deactivated successfully.
Jun 10 01:28:21 mov systemd[1]: Finished pve-daily-update.service - Daily PVE download activities.
Jun 10 01:28:21 mov systemd[1]: pve-daily-update.service: Consumed 1.755s CPU time.
Jun 10 01:31:23 mov smartd[550]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 40 to 46
Jun 10 02:01:23 mov smartd[550]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 46 to 41
Jun 10 02:17:01 mov CRON[294568]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Jun 10 02:17:01 mov CRON[294569]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Jun 10 02:17:01 mov CRON[294568]: pam_unix(cron:session): session closed for user root
Jun 10 02:31:23 mov smartd[550]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 41 to 43
Jun 10 03:01:23 mov smartd[550]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 43 to 41
Jun 10 03:10:01 mov CRON[302383]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Jun 10 03:10:01 mov CRON[302384]: (root) CMD (test -e /run/systemd/system || SERVICE_MODE=1 /sbin/e2scrub_all -A -r)
Jun 10 03:10:01 mov CRON[302383]: pam_unix(cron:session): session closed for user root
Jun 10 03:17:01 mov CRON[303410]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Jun 10 03:17:01 mov CRON[303411]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Jun 10 03:17:01 mov CRON[303410]: pam_unix(cron:session): session closed for user root
Jun 10 03:31:23 mov smartd[550]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 41 to 42
Jun 10 04:01:23 mov smartd[550]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 42 to 48
Jun 10 04:17:01 mov CRON[312274]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Jun 10 04:17:01 mov CRON[312275]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Jun 10 04:17:01 mov CRON[312274]: pam_unix(cron:session): session closed for user root
Jun 10 04:31:23 mov smartd[550]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 48 to 47
-- Boot 00b494ec022543f6979628b9032da935 --
Jun 10 15:37:20 mov kernel: Linux version 6.8.12-9-pve (build@proxmox) (gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP PREEMPT_DYNAMIC PMX 6.8.12-9 (2025-03-16T19:18Z) ()
Jun 10 15:37:20 mov kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-6.8.12-9-pve root=/dev/mapper/pve-root ro quiet
Jun 10 15:37:20 mov kernel: KERNEL supported cpus:
Jun 10 15:37:20 mov kernel: Intel GenuineIntel
Jun 10 15:37:20 mov kernel: AMD AuthenticAMD
Jun 10 15:37:20 mov kernel: Hygon HygonGenuine
Jun 10 15:37:20 mov kernel: Centaur CentaurHauls
Jun 10 15:37:20 mov kernel: zhaoxin Shanghai
Jun 10 15:37:20 mov kernel: x86/split lock detection: #AC: crashing the kernel on kernel split_locks and warning on user-space split_locks
Jun 10 15:37:20 mov kernel: BIOS-provided physical RAM map:
Jun 10 15:37:20 mov kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009dfff] usable
Jun 10 15:37:20 mov kernel: BIOS-e820: [mem 0x000000000009e000-0x000000000009efff] reserved
Jun 10 15:37:20 mov kernel: BIOS-e820: [mem 0x000000000009f000-0x000000000009ffff] usable
Jun 10 15:37:20 mov kernel: BIOS-e820: [mem 0x00000000000a0000-0x00000000000fffff] reserved
Jun 10 15:37:20 mov kernel: BIOS-e820: [mem 0x0000000000100000-0x0000000040d5bfff] usable
Jun 10 15:37:20 mov kernel: BIOS-e820: [mem 0x0000000040d5c000-0x0000000040d5cfff] reserved
Jun 10 15:37:20 mov kernel: BIOS-e820: [mem 0x0000000040d5d000-0x0000000040d92fff] usable
Jun 10 15:37:20 mov kernel: BIOS-e820: [mem 0x0000000040d93000-0x0000000040d93fff] reserved
Jun 10 15:37:20 mov kernel: BIOS-e820: [mem 0x0000000040d94000-0x00000000720edfff] usable
Jun 10 15:37:20 mov kernel: BIOS-e820: [mem 0x00000000720ee000-0x00000000751edfff] reserved


I read somewhere on reddit that I should deactivate c-states in the bios, but I have no clue what that even is.
I only read it can increase heating in the device ?

Please help me.
Thanks for your time.
 
Update: today it went out like 5 times always changing heat and then dead.

Jun 10 19:33:53 mov smartd[555]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 48 to 47
Jun 10 20:03:53 mov smartd[555]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 47 to 44
Jun 10 20:17:01 mov CRON[25026]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Jun 10 20:17:01 mov CRON[25027]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Jun 10 20:17:01 mov CRON[25026]: pam_unix(cron:session): session closed for user root
Jun 10 20:33:53 mov smartd[555]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 44 to 46
-- Reboot --
Jun 10 21:10:15 mov kernel: Linux version 6.8.12-9-pve (build@proxmox) (gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP PREEMPT_DYNAMIC PMX 6.8.12-9 (2025-03-16T19:18Z) ()
Jun 10 21:10:15 mov kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-6.8.12-9-pve root=/dev/mapper/pve-root ro quiet
Jun 10 21:10:15 mov kernel: KERNEL supported cpus:
Jun 10 21:10:15 mov kernel: Intel GenuineIntel
Jun 10 21:10:15 mov kernel: AMD AuthenticAMD
Jun 10 21:10:15 mov kernel: Hygon HygonGenuine
Jun 10 21:10:15 mov kernel: Centaur CentaurHauls
Jun 10 21:10:15 mov kernel: zhaoxin Shanghai
Jun 10 21:10:15 mov kernel: x86/split lock detection: #AC: crashing the kernel on kernel split_locks and warning on user-space split_locks
Jun 10 21:10:15 mov kernel: BIOS-provided physical RAM map:
Jun 10 21:10:15 mov kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009dfff] usable
Jun 10 21:10:15 mov kernel: BIOS-e820: [mem 0x000000000009e000-0x000000000009efff] reserved
 
The logs are indistinguishable from a reset button press or a temporary power outage. There is nothing to go on, sorry. This is usually a hardware problem but can sometimes be fixes by a BIOS/firmware update. "mini-pcs" don't have the best reputation on stability and suitability for a clustered enterprise hypervisor. Check for a BIOS update or try replacing hardware parts to isolate the problem.
 
leesteken said:
The logs are indistinguishable from a reset button press or a temporary power outage. There is nothing to go on, sorry. This is usually a hardware problem but can sometimes be fixes by a BIOS/firmware update. "mini-pcs" don't have the best reputation on stability and suitability for a clustered enterprise hypervisor. Check for a BIOS update or try replacing hardware parts to isolate the problem.
Click to expand...
first thanks for your answer , you are correct, I found this out and switched to a beelink mini pc with also around the same specs, then on this device proxmox was stable but my ubuntu vms crashed for no apparent reason, now I found the true problem, it was having 4x SSD USB3.2 external Harddrives connected, the power wasnt enought to keep it stable so the vm crashed, so if anyone encounters the same problem you need to get a powered USB hub

Update:
now the beelink proxmox vm crashed even with no external harddrive connected. Even with C-States in the optimal config, I guess these mini pcs are really unstable, I now switched to an GMKtec , will updated if it runs there without problem.
 
Last edited:
  • Like
Reactions: leesteken
Multiple VMs shutdown unexpectedly every hour, exactly!
I am running PMX 6.8.12-11 and I have multiple vms installed on my server

every one hour 2 VMs shutdown and do not restart after shutdown
so I have to start them manually

I have checked timers, I couldn't find anything relevant,

to put you to perspective

here is the log upon crash
Bash: 
Jun 16 10:44:38 host-92-204-255-114 kernel: tap106i0: left allmulticast mode
Jun 16 10:44:38 host-92-204-255-114 kernel: fwbr106i0: port 2(tap106i0) entered disabled state
Jun 16 10:44:38 host-92-204-255-114 kernel: fwbr106i0: port 1(fwln106i0) entered disabled state
Jun 16 10:44:38 host-92-204-255-114 kernel: vmbr0: port 3(fwpr106p0) entered disabled state
Jun 16 10:44:38 host-92-204-255-114 kernel: fwln106i0 (unregistering): left allmulticast mode
Jun 16 10:44:38 host-92-204-255-114 kernel: fwln106i0 (unregistering): left promiscuous mode
Jun 16 10:44:38 host-92-204-255-114 kernel: fwbr106i0: port 1(fwln106i0) entered disabled state
Jun 16 10:44:38 host-92-204-255-114 kernel: fwpr106p0 (unregistering): left allmulticast mode
Jun 16 10:44:38 host-92-204-255-114 kernel: fwpr106p0 (unregistering): left promiscuous mode
Jun 16 10:44:38 host-92-204-255-114 kernel: vmbr0: port 3(fwpr106p0) entered disabled state
Jun 16 10:44:38 host-92-204-255-114 qmeventd[1455]: read: Connection reset by peer
Jun 16 10:44:38 host-92-204-255-114 pvedaemon[1816]: VM 106 qmp command failed - VM 106 qmp command 'guest-ping' failed - client closed connection
Jun 16 10:44:39 host-92-204-255-114 systemd[1]: 106.scope: Deactivated successfully.
Jun 16 10:44:39 host-92-204-255-114 systemd[1]: 106.scope: Consumed 26min 47.574s CPU time.
Jun 16 10:44:39 host-92-204-255-114 qmeventd[56788]: Starting cleanup for 106
Jun 16 10:44:39 host-92-204-255-114 qmeventd[56788]: Finished cleanup for 106
 
aa0774197 said:
Multiple VMs shutdown unexpectedly every hour, exactly!
I am running PMX 6.8.12-11 and I have multiple vms installed on my server

every one hour 2 VMs shutdown and do not restart after shutdown
so I have to start them manually

I have checked timers, I couldn't find anything relevant,

to put you to perspective

here is the log upon crash
Bash: 
Jun 16 10:44:38 host-92-204-255-114 kernel: tap106i0: left allmulticast mode
Jun 16 10:44:38 host-92-204-255-114 kernel: fwbr106i0: port 2(tap106i0) entered disabled state
Jun 16 10:44:38 host-92-204-255-114 kernel: fwbr106i0: port 1(fwln106i0) entered disabled state
Jun 16 10:44:38 host-92-204-255-114 kernel: vmbr0: port 3(fwpr106p0) entered disabled state
Jun 16 10:44:38 host-92-204-255-114 kernel: fwln106i0 (unregistering): left allmulticast mode
Jun 16 10:44:38 host-92-204-255-114 kernel: fwln106i0 (unregistering): left promiscuous mode
Jun 16 10:44:38 host-92-204-255-114 kernel: fwbr106i0: port 1(fwln106i0) entered disabled state
Jun 16 10:44:38 host-92-204-255-114 kernel: fwpr106p0 (unregistering): left allmulticast mode
Jun 16 10:44:38 host-92-204-255-114 kernel: fwpr106p0 (unregistering): left promiscuous mode
Jun 16 10:44:38 host-92-204-255-114 kernel: vmbr0: port 3(fwpr106p0) entered disabled state
Jun 16 10:44:38 host-92-204-255-114 qmeventd[1455]: read: Connection reset by peer
Jun 16 10:44:38 host-92-204-255-114 pvedaemon[1816]: VM 106 qmp command failed - VM 106 qmp command 'guest-ping' failed - client closed connection
Jun 16 10:44:39 host-92-204-255-114 systemd[1]: 106.scope: Deactivated successfully.
Jun 16 10:44:39 host-92-204-255-114 systemd[1]: 106.scope: Consumed 26min 47.574s CPU time.
Jun 16 10:44:39 host-92-204-255-114 qmeventd[56788]: Starting cleanup for 106
Jun 16 10:44:39 host-92-204-255-114 qmeventd[56788]: Finished cleanup for 106
Click to expand...

just like this and this happens exactly one hour after restart
other VMs work fine
only two VMs crash
 
aa0774197 said:
just like this and this happens exactly one hour after restart
other VMs work fine
only two VMs crash
Click to expand...
I am now on the third Mini pc, it really seems the intel n150 cpu has problem with proxmox, the c-states could be the culprit, I luckily could use amazon to get a refund, I even checked without the external harddrives so this was not the problem
 
aa0774197 said:
just like this and this happens exactly one hour after restart
other VMs work fine
only two VMs crash
Click to expand...
I am now on the third Mini pc, it really seems the intel n150 cpu has problem with proxmox, the c-states could be the culprit, I luckily could use amazon to get a refund, I even checked without the external harddrives so this was not the problem

Update:
Ok the new mini pc VM also crashed, but it seems it has a legit error code now with a segfault


Code: 
Jun 16 19:40:55 proxmox systemd[1]: Started 100.scope.
Jun 16 19:40:55 proxmox kernel: tap100i0: entered promiscuous mode
Jun 16 19:40:55 proxmox kernel: vmbr0: port 2(fwpr100p0) entered blocking state
Jun 16 19:40:55 proxmox kernel: vmbr0: port 2(fwpr100p0) entered disabled state
Jun 16 19:40:55 proxmox kernel: fwpr100p0: entered allmulticast mode
Jun 16 19:40:55 proxmox kernel: fwpr100p0: entered promiscuous mode
Jun 16 19:40:55 proxmox kernel: vmbr0: port 2(fwpr100p0) entered blocking state
Jun 16 19:40:55 proxmox kernel: vmbr0: port 2(fwpr100p0) entered forwarding state
Jun 16 19:40:55 proxmox kernel: fwbr100i0: port 1(fwln100i0) entered blocking state
Jun 16 19:40:55 proxmox kernel: fwbr100i0: port 1(fwln100i0) entered disabled state
Jun 16 19:40:55 proxmox kernel: fwln100i0: entered allmulticast mode
Jun 16 19:40:55 proxmox kernel: fwln100i0: entered promiscuous mode
Jun 16 19:40:55 proxmox kernel: fwbr100i0: port 1(fwln100i0) entered blocking state
Jun 16 19:40:55 proxmox kernel: fwbr100i0: port 1(fwln100i0) entered forwarding state
Jun 16 19:40:55 proxmox kernel: fwbr100i0: port 2(tap100i0) entered blocking state
Jun 16 19:40:55 proxmox kernel: fwbr100i0: port 2(tap100i0) entered disabled state
Jun 16 19:40:55 proxmox kernel: tap100i0: entered allmulticast mode
Jun 16 19:40:55 proxmox kernel: fwbr100i0: port 2(tap100i0) entered blocking state
Jun 16 19:40:55 proxmox kernel: fwbr100i0: port 2(tap100i0) entered forwarding state
Jun 16 19:40:56 proxmox kernel: sd 5:0:0:0: [sdd] Synchronizing SCSI cache
Jun 16 19:40:56 proxmox kernel: sd 5:0:0:0: [sdd] Synchronize Cache(10) failed: Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
Jun 16 19:40:56 proxmox kernel: sd 4:0:0:0: [sdc] Synchronizing SCSI cache
Jun 16 19:40:56 proxmox kernel: sd 4:0:0:0: [sdc] Synchronize Cache(10) failed: Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
Jun 16 19:40:56 proxmox kernel: sd 3:0:0:0: [sdb] Synchronizing SCSI cache
Jun 16 19:40:56 proxmox kernel: sd 3:0:0:0: [sdb] Synchronize Cache(10) failed: Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
Jun 16 19:40:56 proxmox kernel: sd 2:0:0:0: [sda] Synchronizing SCSI cache
Jun 16 19:40:56 proxmox kernel: sd 2:0:0:0: [sda] Synchronize Cache(10) failed: Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
Jun 16 19:40:56 proxmox pvedaemon[14614]: VM 100 started with PID 14625.
Jun 16 19:40:56 proxmox pvedaemon[864]: <root@pam> end task UPID:proxmox:00003916:0008064F:68505727:qmstart:100:root@pam: OK
Jun 16 19:40:56 proxmox pvedaemon[14695]: starting vnc proxy UPID:proxmox:00003967:000806EB:68505728:vncproxy:100:root@pam:
Jun 16 19:40:56 proxmox pvedaemon[863]: <root@pam> starting task UPID:proxmox:00003967:000806EB:68505728:vncproxy:100:root@pam:
Jun 16 19:41:02 proxmox kernel: usb 2-1.4: reset SuperSpeed USB device number 6 using xhci_hcd
Jun 16 19:41:02 proxmox kernel: usb 2-1.3: reset SuperSpeed USB device number 5 using xhci_hcd
Jun 16 19:41:02 proxmox kernel: usb 2-1.2: reset SuperSpeed USB device number 4 using xhci_hcd
Jun 16 19:41:02 proxmox kernel: usb 2-1.1: reset SuperSpeed USB device number 3 using xhci_hcd
Jun 16 19:46:03 proxmox kernel: usb 2-1.4: reset SuperSpeed USB device number 6 using xhci_hcd
Jun 16 19:46:03 proxmox kernel: kvm[14625]: segfault at 31 ip 0000569cbf809080 sp 00007ffd628f8bb0 error 4 in qemu-system-x86_64[569cbf521000+6ba000] likely on CPU 0 (core 4, socket 0)
Jun 16 19:46:03 proxmox kernel: Code: f6 ba 50 00 8b 04 81 89 42 54 80 7b 10 00 0f 85 d6 00 00 00 8b 05 68 e6 46 01 4c 8b 6b 08 85 c0 0f 85 74 01 00 00 49 8b 45 10 <80> 78 0c 00 74 0a 80 78 01 69 0f 84 10 01 00 00 48 8d 35 f4 ea 4b
Jun 16 19:46:03 proxmox pvedaemon[863]: <root@pam> end task UPID:proxmox:00003967:000806EB:68505728:vncproxy:100:root@pam: OK
Jun 16 19:46:03 proxmox kernel: fwbr100i0: port 2(tap100i0) entered disabled state
Jun 16 19:46:03 proxmox kernel: tap100i0 (unregistering): left allmulticast mode
Jun 16 19:46:03 proxmox kernel: fwbr100i0: port 2(tap100i0) entered disabled state
Jun 16 19:46:03 proxmox systemd[1]: 100.scope: Deactivated successfully.
Jun 16 19:46:03 proxmox systemd[1]: 100.scope: Consumed 5min 32.274s CPU time.
Jun 16 19:46:04 proxmox qmeventd[15476]: Starting cleanup for 100
Jun 16 19:46:04 proxmox kernel: fwbr100i0: port 1(fwln100i0) entered disabled state
Jun 16 19:46:04 proxmox kernel: vmbr0: port 2(fwpr100p0) entered disabled state
Jun 16 19:46:04 proxmox kernel: fwln100i0 (unregistering): left allmulticast mode
Jun 16 19:46:04 proxmox kernel: fwln100i0 (unregistering): left promiscuous mode
Jun 16 19:46:04 proxmox kernel: fwbr100i0: port 1(fwln100i0) entered disabled state
Jun 16 19:46:04 proxmox kernel: fwpr100p0 (unregistering): left allmulticast mode
Jun 16 19:46:04 proxmox kernel: fwpr100p0 (unregistering): left promiscuous mode
Jun 16 19:46:04 proxmox kernel: vmbr0: port 2(fwpr100p0) entered disabled state
Jun 16 19:46:04 proxmox qmeventd[15476]: Finished cleanup for 100
Jun 16 19:47:16 proxmox pvedaemon[15675]: starting termproxy UPID:proxmox:00003D3B:00089B3C:685058A4:vncshell::root@pam:
Jun 16 19:47:16 proxmox pvedaemon[863]: <root@pam> starting task UPID:proxmox:00003D3B:00089B3C:685058A4:vncshell::root@pam:
Jun 16 19:47:16 proxmox pvedaemon[864]: <root@pam> successful auth for user 'root@pam
 
You must log in or register to reply here.
Top Bottom