I'm running Proxmox VE on a new Protecli VP4650 with:
Memory:
Kingston Impact DDR4-3200 SO-DIMM Memory Module - 32GB
Storage (M.2 NVMe or SATA SSD):
4TB Kingston NVMe NV2-4000G
BIOS:
coreboot (Open Source) BIOS
I installed Proxmox VE 8.1.3 with zfs. I then updated it with the no subscription updates. I would then get random reboots every few hours. It once lasted all night. Since I was just starting, I reinstalled Proxmox with the defaults, booted it, logged in, and made no changes. A little over an hour later, it rebooted. This is the last of the log:
Jan 04 15:17:01 pve1 CRON[4844]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Jan 04 15:17:01 pve1 CRON[4845]: (root) CMD (cd / && run-parts –report /etc/cron.hourly)
Jan 04 15:17:01 pve1 CRON[4844]: pam_unix(cron:session): session closed for user root
Jan 04 15:35:05 pve1 pvedaemon[938]: <root@pam> successful auth for user ‘root@pam’
Jan 04 15:39:44 pve1 kernel: i915 0000:00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun
Jan 04 15:45:54 pve1 pveproxy[967]: worker exit
Jan 04 15:45:54 pve1 pveproxy[964]: worker 967 finished
Jan 04 15:45:54 pve1 pveproxy[964]: starting 1 worker(s)
Jan 04 15:45:54 pve1 pveproxy[964]: worker 8708 started
Jan 04 15:52:17 pve1 pveproxy[966]: worker exit
Jan 04 15:52:17 pve1 pveproxy[964]: worker 966 finished
Jan 04 15:52:17 pve1 pveproxy[964]: starting 1 worker(s)
Jan 04 15:52:17 pve1 pveproxy[964]: worker 9552 started
Jan 04 15:55:05 pve1 pvedaemon[937]: <root@pam> successful auth for user ‘root@pam’
Jan 04 16:10:08 pve1 pveproxy[965]: worker exit
Jan 04 16:10:08 pve1 pveproxy[964]: worker 965 finished
Jan 04 16:10:08 pve1 pveproxy[964]: starting 1 worker(s)
Jan 04 16:10:08 pve1 pveproxy[964]: worker 11928 started
Jan 04 16:15:05 pve1 pvedaemon[938]: <root@pam> successful auth for user ‘root@pam’
Jan 04 16:17:01 pve1 CRON[12841]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Jan 04 16:17:01 pve1 CRON[12843]: (root) CMD (cd / && run-parts –report /etc/cron.hourly)
Jan 04 16:17:01 pve1 CRON[12841]: pam_unix(cron:session): session closed for user root
— Reboot —
Protecli ran a bunch of tests on the unit prior to shipping. Prior to the last install, I ran one cycle of memtest without errors.
Update: it rebooted again:
Jan 04 16:45:05 pve1 pvedaemon[945]: <root@pam> successful auth for user ‘root@pam’
Jan 04 16:59:24 pve1 pveproxy[954]: worker exit
Jan 04 16:59:24 pve1 pveproxy[953]: worker 954 finished
Jan 04 16:59:24 pve1 pveproxy[953]: starting 1 worker(s)
Jan 04 16:59:25 pve1 pveproxy[953]: worker 14823 started
Jan 04 17:00:05 pve1 pvedaemon[946]: <root@pam> successful auth for user ‘root@pam’
— Reboot —
Update: It's the next day. It rebooted at 22:53, 01:01, and 03:45. It's now 08:33. One other piece of information: I'm using a DHCP assigned IP address.
Memory:
Kingston Impact DDR4-3200 SO-DIMM Memory Module - 32GB
Storage (M.2 NVMe or SATA SSD):
4TB Kingston NVMe NV2-4000G
BIOS:
coreboot (Open Source) BIOS
I installed Proxmox VE 8.1.3 with zfs. I then updated it with the no subscription updates. I would then get random reboots every few hours. It once lasted all night. Since I was just starting, I reinstalled Proxmox with the defaults, booted it, logged in, and made no changes. A little over an hour later, it rebooted. This is the last of the log:
Jan 04 15:17:01 pve1 CRON[4844]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Jan 04 15:17:01 pve1 CRON[4845]: (root) CMD (cd / && run-parts –report /etc/cron.hourly)
Jan 04 15:17:01 pve1 CRON[4844]: pam_unix(cron:session): session closed for user root
Jan 04 15:35:05 pve1 pvedaemon[938]: <root@pam> successful auth for user ‘root@pam’
Jan 04 15:39:44 pve1 kernel: i915 0000:00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun
Jan 04 15:45:54 pve1 pveproxy[967]: worker exit
Jan 04 15:45:54 pve1 pveproxy[964]: worker 967 finished
Jan 04 15:45:54 pve1 pveproxy[964]: starting 1 worker(s)
Jan 04 15:45:54 pve1 pveproxy[964]: worker 8708 started
Jan 04 15:52:17 pve1 pveproxy[966]: worker exit
Jan 04 15:52:17 pve1 pveproxy[964]: worker 966 finished
Jan 04 15:52:17 pve1 pveproxy[964]: starting 1 worker(s)
Jan 04 15:52:17 pve1 pveproxy[964]: worker 9552 started
Jan 04 15:55:05 pve1 pvedaemon[937]: <root@pam> successful auth for user ‘root@pam’
Jan 04 16:10:08 pve1 pveproxy[965]: worker exit
Jan 04 16:10:08 pve1 pveproxy[964]: worker 965 finished
Jan 04 16:10:08 pve1 pveproxy[964]: starting 1 worker(s)
Jan 04 16:10:08 pve1 pveproxy[964]: worker 11928 started
Jan 04 16:15:05 pve1 pvedaemon[938]: <root@pam> successful auth for user ‘root@pam’
Jan 04 16:17:01 pve1 CRON[12841]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Jan 04 16:17:01 pve1 CRON[12843]: (root) CMD (cd / && run-parts –report /etc/cron.hourly)
Jan 04 16:17:01 pve1 CRON[12841]: pam_unix(cron:session): session closed for user root
— Reboot —
Protecli ran a bunch of tests on the unit prior to shipping. Prior to the last install, I ran one cycle of memtest without errors.
Update: it rebooted again:
Jan 04 16:45:05 pve1 pvedaemon[945]: <root@pam> successful auth for user ‘root@pam’
Jan 04 16:59:24 pve1 pveproxy[954]: worker exit
Jan 04 16:59:24 pve1 pveproxy[953]: worker 954 finished
Jan 04 16:59:24 pve1 pveproxy[953]: starting 1 worker(s)
Jan 04 16:59:25 pve1 pveproxy[953]: worker 14823 started
Jan 04 17:00:05 pve1 pvedaemon[946]: <root@pam> successful auth for user ‘root@pam’
— Reboot —
Update: It's the next day. It rebooted at 22:53, 01:01, and 03:45. It's now 08:33. One other piece of information: I'm using a DHCP assigned IP address.
Last edited: