[SOLVED] Reboot without reason

Ernie95 · Oct 27, 2025

Hi All,

During my absence, the proxmox server was rebooted with any reason.

I saw this in the journal :

Code:

Oct 27 18:42:54 pve smartd[2089]: Device: /dev/sdh [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 22 to 23
-- Reboot --
Oct 27 18:56:34 pve kernel: Linux version 6.14.11-4-pve (build@proxmox) (gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44) #1 SMP PREEMPT_DYNAMIC PMX 6.14.11-4 (2025-10-10T08:04Z) ()
Oct 27 18:56:34 pve kernel: Command line: initrd=\EFI\proxmox\6.14.11-4-pve\initrd.img-6.14.11-4-pve root=ZFS=rpool/ROOT/pve-1 boot=zfs intel_iommu=on iommu=pt

How can I investigate in order to identify the origin of the reboot ?

The server is on UPS and no alert (electricity was not cut).

Thanks for your help

Ernie95 · Oct 27, 2025

Hi,
I saw this in grafana for the memory used :

I am using since this weekend : Linux 6.14.11-4-pve (2025-10-10T08:04Z) as kernel (after update).

Is it a memory leak ?

thanks for your advice

UdoB · Oct 28, 2025

Ernie95 said:
Is it a memory leak ?

Probably not. (Why do you think so?)

In the old days ZFS had default ARC size of 50%, that would fit. The newer limits (auto-configured by PVE during installation) are much lower, see https://pve.proxmox.com/pve-docs/pve-admin-guide.html#sysadmin_zfs_limit_memory_usage

Ernie95 said:
How can I investigate in order to identify the origin of the reboot ?

Try harder to find hints regarding the crashes in the Journal. You only posted a single line before "Reboot" - that's not enough ;-)

If it happened during the previous boot you can look at the end of the relevant journal like this:

Code:

journalctl -b -1  -p warning  -e

For a description of "-b" etc. consult man journalctl.

Additionally you may check all cables and connectors, run memtest86++ over night, check for BIOS/Firmware updates, ...

Ernie95 · Oct 28, 2025

Thanks.
Here the results of the command :

Code:

Oct 24 09:58:06 pve usbhid-ups[2461]: ups_status_set: seems that UPS [apc] is in OL+DISCHRG state now. Is it calibrating (perhaps you want to set 'onlinedischarge_calibration>
Oct 24 10:39:51 pve pvestatd[2598]: auth key pair too old, rotating..
Oct 24 13:39:13 pve pveproxy[953079]: got inotify poll request in wrong process - disabling inotify
Oct 24 14:18:13 pve pveproxy[976995]: got inotify poll request in wrong process - disabling inotify
Oct 24 15:15:13 pve pveproxy[1011889]: got inotify poll request in wrong process - disabling inotify
Oct 24 18:10:13 pve pveproxy[1118862]: got inotify poll request in wrong process - disabling inotify
Oct 24 18:25:14 pve pveproxy[1128083]: got inotify poll request in wrong process - disabling inotify
Oct 24 22:22:13 pve pveproxy[1273806]: got inotify poll request in wrong process - disabling inotify
Oct 24 22:44:15 pve pveproxy[1287203]: got inotify poll request in wrong process - disabling inotify
Oct 24 22:54:14 pve pveproxy[1293288]: got inotify poll request in wrong process - disabling inotify
Oct 25 02:49:14 pve pveproxy[1436942]: got inotify poll request in wrong process - disabling inotify
Oct 25 02:55:14 pve pveproxy[1440604]: got inotify poll request in wrong process - disabling inotify
Oct 25 04:30:14 pve pveproxy[1498641]: got inotify poll request in wrong process - disabling inotify
Oct 25 04:38:14 pve pveproxy[1503517]: got inotify poll request in wrong process - disabling inotify
Oct 25 10:29:15 pve pveproxy[1717910]: got inotify poll request in wrong process - disabling inotify
Oct 25 10:39:54 pve pvestatd[2598]: auth key pair too old, rotating..
Oct 25 14:15:32 pve pveproxy[1856473]: got inotify poll request in wrong process - disabling inotify
Oct 25 15:24:49 pve kernel: RPC: server 192.168.150.21 requires stronger authentication.
Oct 25 15:24:49 pve kernel: RPC: server 192.168.150.21 requires stronger authentication.
Oct 25 15:24:49 pve kernel: RPC: server 192.168.150.21 requires stronger authentication.
Oct 25 15:24:49 pve kernel: RPC: server 192.168.150.21 requires stronger authentication.
Oct 25 15:24:49 pve kernel: RPC: server 192.168.150.21 requires stronger authentication.
Oct 25 15:24:49 pve kernel: RPC: server 192.168.150.21 requires stronger authentication.
Oct 25 15:24:49 pve kernel: RPC: server 192.168.150.21 requires stronger authentication.
Oct 25 15:24:49 pve kernel: RPC: server 192.168.150.21 requires stronger authentication.
Oct 25 15:24:49 pve kernel: RPC: server 192.168.150.21 requires stronger authentication.
Oct 25 15:24:49 pve kernel: RPC: server 192.168.150.21 requires stronger authentication.
Oct 25 15:24:49 pve kernel: RPC: server 192.168.150.21 requires stronger authentication.
Oct 25 15:24:49 pve kernel: RPC: server 192.168.150.21 requires stronger authentication.
Oct 25 15:42:27 pve pveproxy[1913763]: got inotify poll request in wrong process - disabling inotify
Oct 25 16:04:16 pve pvedaemon[1891468]: unable to get PID for CT 116 (not running?)
Oct 25 16:08:26 pve pveproxy[1976200]: got inotify poll request in wrong process - disabling inotify
Oct 25 16:26:44 pve pvedaemon[2002075]: unable to get PID for CT 119 (not running?)
Oct 25 16:32:29 pve pveproxy[2031895]: got inotify poll request in wrong process - disabling inotify
Oct 25 16:38:44 pve pvedaemon[2030170]: unable to get PID for CT 108 (not running?)
Oct 25 16:38:52 pve pvedaemon[1975102]: unable to get PID for CT 111 (not running?)
Oct 25 16:49:27 pve pveproxy[2067269]: got inotify poll request in wrong process - disabling inotify
Oct 25 17:00:41 pve pveproxy[2076286]: got inotify poll request in wrong process - disabling inotify
Oct 25 17:04:25 pve pveproxy[2076286]: problem with client ::ffff:192.168.150.58; Connection reset by peer
Oct 25 17:06:31 pve pveproxy[2080077]: got inotify poll request in wrong process - disabling inotify
Oct 25 17:19:58 pve pveproxy[2080077]: problem with client ::ffff:192.168.150.100; No route to host
Oct 25 21:01:26 pve pveproxy[2224882]: got inotify poll request in wrong process - disabling inotify
Oct 25 21:23:47 pve kernel: kauditd_printk_skb: 163 callbacks suppressed
Oct 25 21:23:48 pve pvedaemon[2222405]: unable to get PID for CT 111 (not running?)
Oct 25 21:24:12 pve pveproxy[2224887]: problem with client ::ffff:192.168.150.74; Connection reset by peer
Oct 25 21:29:47 pve pveproxy[2222814]: problem with client ::ffff:192.168.150.74; Connection reset by peer
Oct 25 23:36:26 pve pveproxy[2320975]: got inotify poll request in wrong process - disabling inotify
Oct 26 03:18:30 pve pveproxy[2520309]: got inotify poll request in wrong process - disabling inotify
Oct 26 03:26:31 pve pveproxy[2525176]: got inotify poll request in wrong process - disabling inotify
Oct 26 05:21:27 pve pveproxy[2595378]: got inotify poll request in wrong process - disabling inotify
Oct 26 06:11:31 pve pveproxy[2625768]: got inotify poll request in wrong process - disabling inotify
Oct 26 06:14:32 pve pveproxy[2627612]: got inotify poll request in wrong process - disabling inotify
Oct 26 07:00:27 pve pveproxy[2656042]: got inotify poll request in wrong process - disabling inotify
Oct 26 07:09:27 pve pveproxy[2661426]: got inotify poll request in wrong process - disabling inotify
Oct 26 07:55:27 pve pveproxy[2689580]: got inotify poll request in wrong process - disabling inotify
Oct 26 08:09:27 pve pveproxy[2697988]: got inotify poll request in wrong process - disabling inotify
Oct 26 09:18:18 pve pvedaemon[2699906]: authentication failure; rhost=::ffff:192.168.150.58 user=root@pam msg=Authentication failure
Oct 26 09:25:15 pve kernel: kauditd_printk_skb: 163 callbacks suppressed
Oct 26 09:39:57 pve pvestatd[2598]: auth key pair too old, rotating..
Oct 26 09:54:14 pve kernel: kauditd_printk_skb: 163 callbacks suppressed
Oct 26 09:54:14 pve pvedaemon[2733980]: unable to get PID for CT 135 (not running?)
Oct 26 10:11:32 pve pveproxy[2785134]: got inotify poll request in wrong process - disabling inotify
Oct 26 10:14:59 pve pvedaemon[2770406]: unable to get PID for CT 113 (not running?)
Oct 26 10:15:00 pve pvedaemon[2787273]: command '/usr/bin/termproxy 5900 --path /vms/113 --perm VM.Console -- /usr/bin/dtach -A /var/run/dtach/vzctlconsole113 -r winch -z lxc>
Oct 26 10:15:00 pve pvedaemon[2770406]: <root@pam> end task UPID:pve:002A87C9:03FDF612:68FDE68C:vncproxy:113:root@pam: command '/usr/bin/termproxy 5900 --path /vms/113 --perm>
Oct 26 10:22:51 pve pvedaemon[2763735]: unable to get PID for CT 135 (not running?)
Oct 26 10:31:42 pve pvedaemon[2770406]: unable to get PID for CT 113 (not running?)
Oct 26 11:59:46 pve pveproxy[2854706]: got inotify poll request in wrong process - disabling inotify
Oct 26 12:01:32 pve kernel: ata1.00: exception Emask 0x10 SAct 0x400 SErr 0x2c0100 action 0x6 frozen
Oct 26 12:01:32 pve kernel: ata1.00: irq_stat 0x08000000, interface fatal error
Oct 26 12:01:32 pve kernel: ata1: SError: { UnrecovData CommWake 10B8B BadCRC }
Oct 26 12:01:32 pve kernel: ata1.00: failed command: READ FPDMA QUEUED
Oct 26 12:01:32 pve kernel: ata1.00: cmd 60/00:50:00:00:00/01:00:00:00:00/40 tag 10 ncq dma 131072 in
Oct 25 16:26:44 pve pvedaemon[2002075]: unable to get PID for CT 119 (not running?)
Oct 25 16:32:29 pve pveproxy[2031895]: got inotify poll request in wrong process - disabling inotify
Oct 25 16:38:44 pve pvedaemon[2030170]: unable to get PID for CT 108 (not running?)
Oct 25 16:38:52 pve pvedaemon[1975102]: unable to get PID for CT 111 (not running?)
Oct 25 16:49:27 pve pveproxy[2067269]: got inotify poll request in wrong process - disabling inotify
Oct 25 17:00:41 pve pveproxy[2076286]: got inotify poll request in wrong process - disabling inotify
Oct 25 17:04:25 pve pveproxy[2076286]: problem with client ::ffff:192.168.150.58; Connection reset by peer
Oct 25 17:06:31 pve pveproxy[2080077]: got inotify poll request in wrong process - disabling inotify
Oct 25 17:19:58 pve pveproxy[2080077]: problem with client ::ffff:192.168.150.100; No route to host
Oct 25 21:01:26 pve pveproxy[2224882]: got inotify poll request in wrong process - disabling inotify
Oct 25 21:23:47 pve kernel: kauditd_printk_skb: 163 callbacks suppressed
Oct 25 21:23:48 pve pvedaemon[2222405]: unable to get PID for CT 111 (not running?)
Oct 25 21:24:12 pve pveproxy[2224887]: problem with client ::ffff:192.168.150.74; Connection reset by peer
Oct 25 21:29:47 pve pveproxy[2222814]: problem with client ::ffff:192.168.150.74; Connection reset by peer
Oct 25 23:36:26 pve pveproxy[2320975]: got inotify poll request in wrong process - disabling inotify
Oct 26 03:18:30 pve pveproxy[2520309]: got inotify poll request in wrong process - disabling inotify
Oct 26 03:26:31 pve pveproxy[2525176]: got inotify poll request in wrong process - disabling inotify
Oct 26 05:21:27 pve pveproxy[2595378]: got inotify poll request in wrong process - disabling inotify
Oct 26 06:11:31 pve pveproxy[2625768]: got inotify poll request in wrong process - disabling inotify
Oct 26 06:14:32 pve pveproxy[2627612]: got inotify poll request in wrong process - disabling inotify
Oct 26 07:00:27 pve pveproxy[2656042]: got inotify poll request in wrong process - disabling inotify
Oct 26 07:09:27 pve pveproxy[2661426]: got inotify poll request in wrong process - disabling inotify
Oct 26 07:55:27 pve pveproxy[2689580]: got inotify poll request in wrong process - disabling inotify
Oct 26 08:09:27 pve pveproxy[2697988]: got inotify poll request in wrong process - disabling inotify
Oct 26 09:18:18 pve pvedaemon[2699906]: authentication failure; rhost=::ffff:192.168.150.58 user=root@pam msg=Authentication failure
Oct 26 09:25:15 pve kernel: kauditd_printk_skb: 163 callbacks suppressed
Oct 26 09:39:57 pve pvestatd[2598]: auth key pair too old, rotating..
Oct 26 09:54:14 pve kernel: kauditd_printk_skb: 163 callbacks suppressed
Oct 26 09:54:14 pve pvedaemon[2733980]: unable to get PID for CT 135 (not running?)
Oct 26 10:11:32 pve pveproxy[2785134]: got inotify poll request in wrong process - disabling inotify
Oct 26 10:14:59 pve pvedaemon[2770406]: unable to get PID for CT 113 (not running?)
Oct 26 10:15:00 pve pvedaemon[2787273]: command '/usr/bin/termproxy 5900 --path /vms/113 --perm VM.Console -- /usr/bin/dtach -A /var/run/dtach/vzctlconsole113 -r winch -z lxc>
Oct 26 10:15:00 pve pvedaemon[2770406]: <root@pam> end task UPID:pve:002A87C9:03FDF612:68FDE68C:vncproxy:113:root@pam: command '/usr/bin/termproxy 5900 --path /vms/113 --perm>
Oct 26 10:22:51 pve pvedaemon[2763735]: unable to get PID for CT 135 (not running?)
Oct 26 10:31:42 pve pvedaemon[2770406]: unable to get PID for CT 113 (not running?)
Oct 26 11:59:46 pve pveproxy[2854706]: got inotify poll request in wrong process - disabling inotify
Oct 26 12:01:32 pve kernel: ata1.00: exception Emask 0x10 SAct 0x400 SErr 0x2c0100 action 0x6 frozen
Oct 26 12:01:32 pve kernel: ata1.00: irq_stat 0x08000000, interface fatal error
Oct 26 12:01:32 pve kernel: ata1: SError: { UnrecovData CommWake 10B8B BadCRC }
Oct 26 12:01:32 pve kernel: ata1.00: failed command: READ FPDMA QUEUED
Oct 26 12:01:32 pve kernel: ata1.00: cmd 60/00:50:00:00:00/01:00:00:00:00/40 tag 10 ncq dma 131072 in
                                     res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x10 (ATA bus error)
Oct 26 12:01:32 pve kernel: ata1.00: status: { DRDY }
Oct 26 12:03:26 pve pveproxy[2855088]: proxy detected vanished client connection
Oct 26 12:03:36 pve pvedaemon[2857254]: command '/usr/bin/termproxy 5900 --path /vms/111 --perm VM.Console -- /usr/bin/dtach -A /var/run/dtach/vzctlconsole111 -r winch -z lxc>
Oct 26 12:03:36 pve pvedaemon[2810886]: <root@pam> end task UPID:pve:002B9926:0407E68C:68FDFFFE:vncproxy:111:root@pam: command '/usr/bin/termproxy 5900 --path /vms/111 --perm>
Oct 26 12:06:29 pve pveproxy[2859307]: got inotify poll request in wrong process - disabling inotify
Oct 26 12:38:28 pve pveproxy[2879399]: got inotify poll request in wrong process - disabling inotify
Oct 26 13:41:28 pve pveproxy[2920317]: got inotify poll request in wrong process - disabling inotify
Oct 26 13:59:26 pve pveproxy[2931892]: got inotify poll request in wrong process - disabling inotify
Oct 26 14:06:32 pve pveproxy[2937240]: got inotify poll request in wrong process - disabling inotify
Oct 26 14:49:28 pve pveproxy[2965905]: got inotify poll request in wrong process - disabling inotify
Oct 26 15:55:28 pve pveproxy[3006968]: got inotify poll request in wrong process - disabling inotify
Oct 26 16:31:32 pve pveproxy[3030041]: got inotify poll request in wrong process - disabling inotify
Oct 26 17:15:27 pve pveproxy[3057247]: got inotify poll request in wrong process - disabling inotify
Oct 26 17:51:52 pve pveproxy[3081661]: got inotify poll request in wrong process - disabling inotify
Oct 26 17:59:06 pve pveproxy[3086461]: got inotify poll request in wrong process - disabling inotify
Oct 26 18:15:31 pve pveproxy[3097185]: got inotify poll request in wrong process - disabling inotify
Oct 26 18:23:27 pve pveproxy[3102155]: got inotify poll request in wrong process - disabling inotify
Oct 26 20:40:29 pve pveproxy[3190895]: got inotify poll request in wrong process - disabling inotify
Oct 26 21:45:26 pve pveproxy[3231400]: got inotify poll request in wrong process - disabling inotify
Oct 27 02:51:26 pve pveproxy[3418530]: got inotify poll request in wrong process - disabling inotify
Oct 27 02:56:32 pve pveproxy[3421608]: got inotify poll request in wrong process - disabling inotify
Oct 27 03:48:26 pve pveproxy[3453281]: got inotify poll request in wrong process - disabling inotify
Oct 27 04:01:31 pve pveproxy[3461264]: got inotify poll request in wrong process - disabling inotify
Oct 27 04:49:26 pve pveproxy[3490689]: got inotify poll request in wrong process - disabling inotify
Oct 27 05:54:26 pve pveproxy[3530481]: got inotify poll request in wrong process - disabling inotify
Oct 27 06:35:27 pve pveproxy[3555669]: got inotify poll request in wrong process - disabling inotify
Oct 27 06:49:26 pve pveproxy[3564329]: got inotify poll request in wrong process - disabling inotify
Oct 27 07:33:26 pve pveproxy[3591285]: got inotify poll request in wrong process - disabling inotify
Oct 27 08:35:26 pve pveproxy[3629245]: got inotify poll request in wrong process - disabling inotify
Oct 27 09:19:26 pve pveproxy[3656119]: got inotify poll request in wrong process - disabling inotify
Oct 27 09:32:31 pve pveproxy[3664156]: got inotify poll request in wrong process - disabling inotify
Oct 27 09:39:59 pve pvestatd[2598]: auth key pair too old, rotating..
Oct 27 11:13:26 pve pveproxy[3725897]: got inotify poll request in wrong process - disabling inotify
Oct 27 12:29:30 pve pveproxy[3772568]: got inotify poll request in wrong process - disabling inotify
Oct 27 12:32:31 pve pveproxy[3774404]: got inotify poll request in wrong process - disabling inotify
Oct 27 13:26:32 pve pveproxy[3807452]: got inotify poll request in wrong process - disabling inotify
Oct 27 14:20:31 pve pveproxy[3840625]: got inotify poll request in wrong process - disabling inotify
Oct 27 14:58:27 pve pveproxy[3863722]: got inotify poll request in wrong process - disabling inotify
Oct 27 15:55:26 pve pveproxy[3898577]: got inotify poll request in wrong process - disabling inotify
Oct 27 17:07:29 pve pveproxy[3942648]: got inotify poll request in wrong process - disabling inotify

Does # pvecm updatecerts can solve the error 'got inotify....' ?

Not sure that it is the origin of my reboot.

I am thinking to a memory leak as the grafana show a decrease of the memory.

I will investigate the error on ATA1.00

I will launch asap the memtest, look at bios also.

Onslow · Oct 28, 2025

I don't know if they are the reason of the reboot, but these "ata" entries in the log look as a disk (or a disk interface, or a controller or a cable) problem.

Do you have backups?

https://en.wikipedia.org/wiki/Rebel_Without_a_Cause
- sorry, my first association after reading the title of the thread ;-).

Ernie95 · Oct 29, 2025

Onslow said:
I don't know if they are the reason of the reboot, but these "ata" entries in the log look as a disk (or a disk interface, or a controller or a cable) problem.

Do you have backups?

https://en.wikipedia.org/wiki/Rebel_Without_a_Cause
- sorry, my first association after reading the title of the thread ;-).

Thanks. Yes I have backup. I will check the cable.

Ernie95 · Nov 2, 2025

Hi All,

Here some results of my investigation :

1) ata1.00 : I changed the sata cable by a sata cable with clip. I will see if the error disappears but I am confident.

2) Memtest86+ version 7.2
- first test with 4 dimm (each 32Go and same brand, same reference) : at the beginning of the test lot of errors. I stopped the test.
- 2nd test with 3 dimm : no error (4 hours)
- 3rd test with 3 dimm : I moved one dimm on the empty position. No errors (4 hours)
- 4th test with 4 dimm (the same as test 1) : no errors (7 hours). The difference is that I unplugged network cables, and there was an unplugged of AC cable before the test
- 5th test with 4 dimm : all network cables are plugged. Test in progress, I will see tomorrow morning.

Not clear why some errors with first test. Tomorrow I will see if bad memory.

3) I saw later some errors in journal on zram. I installed Zram but I think it is a bad idea with ZFS (https://forum.proxmox.com/threads/how-to-configure-zram-on-zfs.151747/). I installed Proxmox on zraid1 (mirror).
So I will unstall zram and perhaps it could be the origin of my reboot.
I will move to swap as this explanation : https://forum.proxmox.com/threads/n...-raid1-how-to-create-swap.103157/#post-470250

I will see how to test my PSU to be sure that ATA error is not linked to bad PSU.

Any comments are welcome.

Ernie95 · Friday at 12:52

Hi
I had to change the cable with new one (I used a cable that I bought some years ago...) as the ATA error comes back.

With new cables, no error at boot. I will see with time.

Since the memtest and the suppression of zram, no reboot without reason.

BR

Edit 24 hours : no new error ATA

Ernie95 · Sunday at 12:51

Hi,
Solved and the summary

1) Error on ATA1.00

Code:

Oct 26 12:01:32 pve kernel: ata1.00: exception Emask 0x10 SAct 0x400 SErr 0x2c0100 action 0x6 frozen
Oct 26 12:01:32 pve kernel: ata1.00: irq_stat 0x08000000, interface fatal error
Oct 26 12:01:32 pve kernel: ata1: SError: { UnrecovData CommWake 10B8B BadCRC }
Oct 26 12:01:32 pve kernel: ata1.00: failed command: READ FPDMA QUEUED
Oct 26 12:01:32 pve kernel: ata1.00: cmd 60/00:50:00:00:00/01:00:00:00:00/40 tag 10 ncq dma 131072 in

For 95% of the case, it comes from bad sata cable. It is my case.

2) Reboot : I suspect the use of zram for swap, and zram is not recommanded for zfs.

BR

Search

Search

[SOLVED] Reboot without reason

Ernie95

Member

Ernie95

Member

UdoB

Distinguished Member

Ernie95

Member

Onslow

Active Member

Ernie95

Member

Ernie95

Member

Ernie95

Member

Ernie95

Member

We value your privacy