I have been running unraid on an old pc for about a year and its always had problems but they were liveable, like not being able to access plex remotely or having to run new safe permissions if i wanted to move a downloaded file manually, docker.img filling up, error 403. 

The biggest issue is that it randomly becomes completely unresponsive, the web gui and docker containers are inaccessible, my router isn't showing it on the network and even not even the caps lock works but the led's and fans are still running. a hard power off and restart seems to solve the problem in the short term, be it months or days as has been the case in the last few weeks.

I have lurked on this forum and reddit whenever i get time and tried to fix things but at this point I just got to ask for help. i have tried completely deleting my dockers and installed different repositories three or four times, reformatted my cache drive and dismantled and re-seated all my drives and components. some of them seem to help for a while.

I have discovered that hitting the cpu at 100% all cores even for a single moment will cause it to crash but given that it still happens after trying to use docker pining to reserve a core just for unraid, it cant be the only thing

 

Specs:

i7-7500

MSI Z270 SLI PLUS

32GB DDR4

4x WD 18tb (1 as a parity)

1tb Kingston NV2 as cache

Corsair RM750

 

Any help would be greatly appreciated

Thanks

tower-diagnostics-20230820-1322.zip

Enable the syslog server and post that after a crash.

 

I did a few days ago, to flash, does the diagnostic file thing not inculde it? either way I can see the last crash in the system log (evening of the 18th)

syslog

1 hour ago, KaosWalker said:

does the diagnostic file thing not inculde it?

Diagnostics includes the current syslog. The current syslog is in RAM like the rest of the OS, so doesn't survive reboot.

1 hour ago, KaosWalker said:

I can see the last crash in the system log

Aug 17 22:51:03 Tower root: Fix Common Problems: Warning: Syslog mirrored to flash
Aug 18 17:03:28 Tower kernel: microcode: microcode updated early to revision 0xf0, date = 2021-11-12

Nothing logged between these timestamps.

 

1 hour ago, KaosWalker said:

(evening of the 18th)

Are you sure it hadn't already crashed hours earlier?

unfortunately I don't have an exact time, I was out most of the day, first I knew was my brother complaining plex was down down. for all I know it could have crashed the night before. guess I got to wait till it crashes again.

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.

Have you done memtest?

I haven't done a memtest, couldn't hurt to give it a go. I was recently given an old HP prolient ML350p gen 8, would there be any stability benefit to swapping to it?

14 hours ago, KaosWalker said:

would there be any stability benefit to swapping to it?

It's worth a try.

So it finally crashed again some point last night (between midnight and now) , probably the longest its been running continuously for a long while. I've grabbed the diagnostics and log file, let me know if anything else would help. I'm going to set it to run a mem test, didn't want to ruin a streak.

syslog (3) tower-diagnostics-20230828-1116.zip

Still nothing relevant logged.

are there any other log files or something that might be helpfull?

I think the memtest i was running has just crashed, after running for about 3 hours. does this mean that the ram is most likely whats causing the crashes?

 

 

Not necessarily, but basically it confirms a hardware issue, if you have multiple sticks of RAM try with just one, if it still crashes try a different one, that would basically rule out a RAM problem.