[SOLVED] Random reboots

[romish]

Hi,
I am having trouble with random reboots with Proxmox VE.
I have one node (PVE) and two active VMs (home assistant and open media vault). One inactive of ubuntu 22.04, only active when needed.
Setup:
NUC7i5DNB
Memory: 2400 Mhz 16 GiB.
CPU Intel(R) Core(TM) i5-7300U CPU @ 2.60GHz
Software: Proxmox Virtual Environment 8.1.4

Syslog info below. At around 01.34 it rebooted. This is the same kind of log I find on every reboot (multiple times a day.
Mar 08 01:04:19 pve postfix/qmgr[921]: 16B01340CB1: from=<root@pve.home>, size=1142, nrcpt=1 (queue active)
Mar 08 01:04:19 pve postfix/qmgr[921]: 31F64340D2C: from=<root@pve.home>, size=1142, nrcpt=1 (queue active)
Mar 08 01:04:19 pve postfix/smtp[4642]: connect to gmail-smtp-in.l.google.com[2a00:1450:4025:401::1a]:25: Network is unreachable
Mar 08 01:04:19 pve postfix/smtp[4643]: connect to gmail-smtp-in.l.google.com[2a00:1450:4025:401::1a]:25: Network is unreachable
Mar 08 01:04:19 pve postfix/smtp[4643]: connect to gmail-smtp-in.l.google.com[142.250.27.27]:25: No route to host
Mar 08 01:04:20 pve postfix/smtp[4642]: connect to gmail-smtp-in.l.google.com[142.250.27.27]:25: No route to host
Mar 08 01:04:21 pve postfix/smtp[4642]: connect to alt1.gmail-smtp-in.l.google.com[142.251.9.26]:25: No route to host
Mar 08 01:04:21 pve postfix/smtp[4642]: connect to alt1.gmail-smtp-in.l.google.com[2a00:1450:4025:c03::1b]:25: Network is unreachable
Mar 08 01:04:21 pve postfix/smtp[4642]: connect to alt2.gmail-smtp-in.l.google.com[2a00:1450:4010:c1c::1b]:25: Network is unreachable
Mar 08 01:04:21 pve postfix/smtp[4642]: 16B01340CB1: to=<XXX@gmail.com>, relay=none, delay=107011, delays=107009/0.01/2.2/0, dsn=4.4.1, status=deferred (connect to alt2.gmail-smtp-in.l.google.com[2a00:1450:4010:c1c::1b]:25: Network is unreachable)
Mar 08 01:04:22 pve postfix/smtp[4643]: connect to alt1.gmail-smtp-in.l.google.com[142.251.9.26]:25: No route to host
Mar 08 01:04:22 pve postfix/smtp[4643]: connect to alt1.gmail-smtp-in.l.google.com[2a00:1450:4025:c03::1b]:25: Network is unreachable
Mar 08 01:04:22 pve postfix/smtp[4643]: connect to alt2.gmail-smtp-in.l.google.com[2a00:1450:4010:c1c::1b]:25: Network is unreachable
Mar 08 01:04:22 pve postfix/smtp[4643]: 31F64340D2C: to=<XXX@gmail.com>, relay=none, delay=1502, delays=1499/0.01/3.2/0, dsn=4.4.1, status=deferred (connect to alt2.gmail-smtp-in.l.google.com[2a00:1450:4010:c1c::1b]:25: Network is unreachable)
Mar 08 01:09:18 pve smartd[598]: Device: /dev/sda [SAT], removed ATA device: No such device
Mar 08 01:09:18 pve smartd[598]: Device: /dev/sdb [SAT], removed ATA device: No such device
Mar 08 01:17:01 pve CRON[6384]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Mar 08 01:17:01 pve CRON[6385]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Mar 08 01:17:01 pve CRON[6384]: pam_unix(cron:session): session closed for user root
Mar 08 01:19:19 pve postfix/qmgr[921]: DE471340ABC: from=<root@pve.home>, size=7523, nrcpt=1 (queue active)
Mar 08 01:19:19 pve postfix/smtp[6710]: connect to gmail-smtp-in.l.google.com[142.250.27.27]:25: No route to host
Mar 08 01:19:19 pve postfix/smtp[6710]: connect to gmail-smtp-in.l.google.com[2a00:1450:4025:401::1a]:25: Network is unreachable
Mar 08 01:19:20 pve postfix/smtp[6710]: connect to alt1.gmail-smtp-in.l.google.com[142.251.9.27]:25: No route to host
Mar 08 01:19:20 pve postfix/smtp[6710]: connect to alt1.gmail-smtp-in.l.google.com[2a00:1450:4025:c03::1b]:25: Network is unreachable
Mar 08 01:19:21 pve postfix/smtp[6710]: connect to alt2.gmail-smtp-in.l.google.com[142.250.150.26]:25: No route to host
Mar 08 01:19:21 pve postfix/smtp[6710]: DE471340ABC: to=<XXX@gmail.com>, relay=none, delay=180458, delays=180456/0.01/2.1/0, dsn=4.4.1, status=deferred (connect to alt2.gmail-smtp-in.l.google.com[142.250.150.26]:25: No route to host)
Mar 08 01:24:19 pve postfix/qmgr[921]: 0C870340BC8: from=<root@pve.home>, size=5796, nrcpt=1 (queue active)
Mar 08 01:24:19 pve postfix/smtp[7394]: connect to gmail-smtp-in.l.google.com[142.250.102.26]:25: No route to host
Mar 08 01:24:19 pve postfix/smtp[7394]: connect to gmail-smtp-in.l.google.com[2a00:1450:4025:401::1a]:25: Network is unreachable
Mar 08 01:24:20 pve postfix/smtp[7394]: connect to alt1.gmail-smtp-in.l.google.com[142.251.9.27]:25: No route to host
Mar 08 01:24:20 pve postfix/smtp[7394]: connect to alt1.gmail-smtp-in.l.google.com[2a00:1450:4025:c03::1b]:25: Network is unreachable
Mar 08 01:24:21 pve postfix/smtp[7394]: connect to alt2.gmail-smtp-in.l.google.com[142.250.150.26]:25: No route to host
Mar 08 01:24:21 pve postfix/smtp[7394]: 0C870340BC8: to=<XXX@gmail.com>, relay=none, delay=180599, delays=180597/0.01/2.2/0, dsn=4.4.1, status=deferred (connect to alt2.gmail-smtp-in.l.google.com[142.250.150.26]:25: No route to host)
Mar 08 01:34:19 pve postfix/qmgr[921]: 13A04340C71: from=<root@pve.home>, size=10722, nrcpt=1 (queue active)
Mar 08 01:34:19 pve postfix/qmgr[921]: 31F64340D2C: from=<root@pve.home>, size=1142, nrcpt=1 (queue active)
Mar 08 01:34:19 pve postfix/smtp[8767]: connect to gmail-smtp-in.l.google.com[2a00:1450:4025:402::1a]:25: Network is unreachable
Mar 08 01:34:19 pve postfix/smtp[8768]: connect to gmail-smtp-in.l.google.com[142.250.102.26]:25: No route to host
Mar 08 01:34:19 pve postfix/smtp[8768]: connect to gmail-smtp-in.l.google.com[2a00:1450:4025:402::1a]:25: Network is unreachable
Mar 08 01:34:19 pve postfix/smtp[8768]: connect to alt1.gmail-smtp-in.l.google.com[2a00:1450:4025:c03::1a]:25: Network is unreachable
Mar 08 01:34:20 pve postfix/smtp[8767]: connect to gmail-smtp-in.l.google.com[142.250.102.26]:25: No route to host
Mar 08 01:34:22 pve postfix/smtp[8768]: connect to alt1.gmail-smtp-in.l.google.com[142.251.9.27]:25: No route to host
Mar 08 01:34:23 pve postfix/smtp[8767]: connect to alt1.gmail-smtp-in.l.google.com[142.251.9.27]:25: No route to host
Mar 08 01:34:23 pve postfix/smtp[8767]: connect to alt1.gmail-smtp-in.l.google.com[2a00:1450:4025:c03::1a]:25: Network is unreachable
Mar 08 01:34:23 pve postfix/smtp[8767]: connect to alt2.gmail-smtp-in.l.google.com[2a00:1450:4010:c1c::1a]:25: Network is unreachable
Mar 08 01:34:23 pve postfix/smtp[8767]: 13A04340C71: to=<XXX@gmail.com>, relay=none, delay=176580, delays=176577/0.01/3.2/0, dsn=4.4.1, status=deferred (connect to alt2.gmail-smtp-in.l.google.com[2a00:1450:4010:c1c::1a]:25: Network is unreachable)
Mar 08 01:34:24 pve postfix/smtp[8768]: connect to alt2.gmail-smtp-in.l.google.com[142.250.150.26]:25: No route to host
Mar 08 01:34:24 pve postfix/smtp[8768]: 31F64340D2C: to=<XXX@gmail.com>, relay=none, delay=3304, delays=3300/0.01/4.2/0, dsn=4.4.1, status=deferred (connect to alt2.gmail-smtp-in.l.google.com[142.250.150.26]:25: No route to host)
-- Reboot --
Mar 08 01:55:53 pve kernel: Linux version 6.5.13-1-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.5.13-1 (2024-02-05T13:50Z) ()
Mar 08 01:55:53 pve kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-6.5.13-1-pve root=/dev/mapper/pve-root ro quiet
Mar 08 01:55:53 pve kernel: KERNEL supported cpus:
Mar 08 01:55:53 pve kernel: Intel GenuineIntel
Mar 08 01:55:53 pve kernel: AMD AuthenticAMD
Mar 08 01:55:53 pve kernel: Hygon HygonGenuine
Mar 08 01:55:53 pve kernel: Centaur CentaurHauls
Mar 08 01:55:53 pve kernel: zhaoxin Shanghai

I allready reinstalled proxmox multiple times but it keeps happening.
The reboot also occurs on times when there is not mutch in use (in the middle of the night for example).
I cant find what is causing it, mallfuntioning hardware or some other fault.

I do not now what other info might help you, help me , so please tell me what you need.

 

[gfngfn256]

Maybe try running HA & OMV on it bare metal, and see the results, this way you'd know if its Proxmox related at all.
How long have you been running PVE on it?

 

[romish]

This specific setup for a few weeks. I just switcht to a different NUC (newer), the old one did not have these reboots. It only happens with the new NUC. So I hope it is not a hardware issue.
But i cant find any error messages or the reason why the system is rebooting at random times.

 

[gfngfn256]

So since changing to this "new" NUC (2017 release?) you're getting these reboots. It smells like HW related, where no logs appear. Go through the usual (if possible!; swap out power supply, RAM etc. Check the temps etc. Purchased recently? Second-hand?
Anyway I would still try a bare metal test install.

 

[romish]

Yes a second hand unit.
I was afraid for possible hardware issues. Think ill try this setup with another pc to verify it has to do with the current one.
Thx. for your fast replies.

 

[romish]

It was an hardware issue.
Just bought a New mini pc, installed proxmox VE, did a backups return from the VMs and everything is sollid now.
Still doet now precisie WhatsApp caused it, but it is hardware relaxed.

 

[romish]

It was an hardware issue.
Just bought a New mini pc, installed proxmox VE, did a backups return from the VMs and everything is sollid now.
Still doet now precise whats caused it, but it is hardware relaxed.

 

[gfngfn256]

It was an hardware issue.

This "happens" with second-hand stuff.
Try and get a refund.