Ever since I started my server (about 9 months ago) I have been having intermittent crashes. I can no longer access my SMB shares through Windows or Android and my Plex server says my files are unavailable. I also check the router and my IP address no longer shows in the router as a connected device. In this time I have moved house and tried multiple ethernet cables thinking it was a networking issue. Recently it crashed twice in the one night so I followed the instructions to write my syslog to the boot USB. A week or two later brings it up to last night and it crashed whilst I was asleep. Once I realised it crashed I held in the power button and pulled the USB and have attached the syslog file below. I am a little confused looking at the time stamps as I received a notification in Discord from Sonarr at 4:57am but the last log is around 4:50am. As I am unable to access the network I have uploaded a diagnostics dump I made after the last crash and a reboot. Please let me know if anything further is required or if you have any recommendations as I am at a bit of a loss at the cause of the crashes. 

 

Edit:

I assumed my system information would be in the diagnostics but re-reading the help post I saw that I was supposed to include it separately in the post

- UNRAID 6.11.5 (not sure how to check this without booting to NAS but this is the name of the text file in the diagnostics)

- ASUSTeK COMPUTER INC. - ROG STRIX Z590-A GAMING WIFI II

- Intel Core i5-11400
- Corsair Vengeance LPX 16GB DDR4 3200MHz CL16 Dual Channel Kit (2x 8GB), White

- LSI 9211-8i P20 IT Mode for ZFS FreeNAS unRAID Dell H310 6Gbps SAS HBA

- 4x WD40003FFBX

- 3x ST400VN008

- 1x Seagate_BarraCuda_Q1_SSD

 

Running (from memory):

- Sonarr*

- Bazarr*

- Radarr*

- Plex

- 1x Windows 10 VM

- RStudio Docker

- R Shiny Server*

- DuckDNS

- Wireguard
* Installed in the last month; ie crashes happening from day one when everything else was installed

syslog unraid-nas-diagnostics-20230609-0429.zip

Edited June 18, 20233 yr by AngryPig
Tried to make title more unique and accurate for problem

Unfortunately there's nothing relevant logged, this usually points to a hardware issue, one thing you can try is to boot the server in safe mode with all docker/VMs disabled, 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.

11 minutes ago, JorgeB said:

Unfortunately there's nothing relevant logged, this usually points to a hardware issue, one thing you can try is to boot the server in safe mode with all docker/VMs disabled, 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.

 

I was hoping that wouldn't be the case as it can take weeks to occur, which is a long time on reduced access, but if there is nothing obvious I guess I will have to

11 hours ago, JorgeB said:

Unfortunately there's nothing relevant logged, this usually points to a hardware issue, one thing you can try is to boot the server in safe mode with all docker/VMs disabled, 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.

 

I went into my settings and disabled docker and then went to my flash settings and enabled safe mode no plugins (then rebooted) and it crashed today. Do you have any suggestions on what I should look into for hardware issues?

 

Edit: I have attached the updated syslog file if that helps

syslog

Edited June 18, 20233 yr by AngryPig
Added syslog file

10 hours ago, AngryPig said:

Do you have any suggestions on what I should look into for hardware issues?

Crashing in safe mode to me suggests some hardware issue.