Sudden random reboots

[kaiserfranzjosef]

Hello community,

 

Unraid is running on a Qnap TVS-872XT, not connected to the internet. All of a sudden (yesterday, 27-09-2022 at around 17:30 and today 28-09-2022 at around 04:00) the server just restarts. There is an unclen shutdown as the parity check is kicked on everytime.

 

The syslog is already writing to the flashdrive (better be safe) but I haven´t put much statpoints in my syslog-reading-skill.

 

Your help is very much appreciated und thanks in advance!! Unraidversion is 6.10.3.

 

Find attached the diagnostic files.

 

Greetings from sunny Vienna.

Christian

stammhirn-diagnostics-20220928-0820.zip

Edited September 28, 2022 by kaiserfranzjosef

[JorgeB]

Also post the permanent syslog, it's not included in the diagnostics. 

[kaiserfranzjosef]

There you go.

syslog.txt

[JorgeB]

Nothing relevant logged that I can see, could be this issue:

 

 

[kaiserfranzjosef]

Thank you.

 

The threead you linked contains a lot of transcoding talk, plex, etc. I dont use my server for this at all. Its basically just a huge fileserver (the docker containers are just testprojects and will be removed in the future).

 

I run the server headless, only webgui login and sometimes I use the terminal.

 

Are you suggesting an upgrade to 6.11?

[JorgeB]

45 minutes ago, kaiserfranzjosef said:

I dont use my server for this at all.

Yes, but just having the i915 driver loaded can cause issues for some, if you don't use the better, since you won't miss it after it's been blacklisted to prevent the driver from loading.

[kaiserfranzjosef]

Well, the blacklisting of the i915 driver didnt work. (Assuming I did it the correct way: open terminal and type "touch /boot/config/modprobe.d/i915.conf". I then checked the "System Devices" and under the vidoe controlller there was no mentioning of a i915 kernel driver in use.)

 

The server just rebootet again.

 

Find attatched the diagnostics and the syslog file from the usb flash drive.

 

All input is much appreciated!

Greetings from Vienna

Christian

stammhirn-diagnostics-20221003-1832.zip syslog-192.168.0.200.log

[JorgeB]

When nothing is logged it points to a hardware problem, and hence very difficult to diagnose remotely, one thing you can try is to boot the server in safe mode with all docker/VMs disable, let it run as a basic NAS for a few days, if it still crashes it's likely a hardware problem, if it doesn't start turning on the other services one by one.