Hello all,

 

For the third night in a row my unRAID install has just completely frozen. Web GUI doesn't work, shares aren't accessible, nothing. I'm having to go press the hard reset button on my case just to get it up again. I'm still new to unRAID (still in my trial period) so maybe there's something super obvious that I'm missing. Have any of you ever experienced this before? My box had Windows on it before and I've never experienced anything like it. Are there any diagnostics steps you all would recommend? I've read a few similar(ish) posts and in one of them the OP found his memory was faulty. Maybe I should run a memtest? If so, how would I go about doing that?

 

System specs if needed:

AMD FX 8350

16GB of RAM

EVGA 500W PSU

6x 8TB HDD

1x 1TB HDD
1x 120GB SSD

1x SanDisk Ultra 32GB (boot device)

 

Currently running the following docker images:

Plex

PlexPy

Ombi

 

Thanks for your help!

Edited August 18, 20178 yr by doubley

Just now, doubley said:

Maybe I should run a memtest?

Definitely

Just now, doubley said:

My box had Windows on it before and I've never experienced anything like it

Quite common.  As most problems when Windows is involved gets dusted off as "That's just a Windows problem", even though the OS is rock solid

 

Also you need to post the exact model of the power supply.

2 minutes ago, doubley said:

Are there any diagnostics steps you all would recommend?

Since this is nice and repeatable, install the Fix Common Problems plugin and toss it into troubleshooting mode and do what it tells you to do.  May or may not help diagnosis.

6 minutes ago, Squid said:

Also you need to post the exact model of the power supply.

EVGA 500 W1. Not the best PSU, but it's what I have.

 

7 minutes ago, Squid said:

Since this is nice and repeatable, install the Fix Common Problems plugin and toss it into troubleshooting mode and do what it tells you to do.  May or may not help diagnosis.

Okay, I have it installed and now I'll just wait until it crashes again.

And when you have the next failure and report back on it, give a few details about what time of night the lockup is occurring and what periodic tasks might be running.  Have you ever had it lock up at any other time of day?   Are you using mover, does it start its task, and does it finish?  Does it run a correcting parity check and does it find and fix any errors?

4 hours ago, Frank1940 said:

And when you have the next failure and report back on it, give a few details about what time of night the lockup is occurring and what periodic tasks might be running.  Have you ever had it lock up at any other time of day?   Are you using mover, does it start its task, and does it finish?  Does it run a correcting parity check and does it find and fix any errors?

It always seems to freeze between 3-7AM. Plex does it's nightly maintenance during that time, but I can't imagine why that would cause it to shut down. It is currently running a parity check, because the server has always locked up before I can even get the initial parity check complete! (which means my data is unprotected)

 

I'm unsure has to what the "mover" is so I can't answer that question.

 

I just ran a memtest and it came back saying there were no errors.

3 minutes ago, doubley said:

Plex does it's nightly maintenance during that time, but I can't imagine why that would cause it to shut down.

One way to find out would be to stop the Plex Docker before you go to bed. 

 

4 minutes ago, doubley said:

because the server has always locked up before I can even get the initial parity check complete!

You could try stopping all of the Dockers until you get the parity check complete.

 

6 minutes ago, doubley said:

I'm unsure has to what the "mover" is so I can't answer that question.

 

Mover is the built-in process that moves files written to shares on the cache drive to the protected unRAID array.  It usually runs at night (and I can't remember whether this it is automatically scheduled to so so or not).  You can check its settings by going to    'Settings'   >>>  'Scheduler'   >>>  'Mover settings'.  (This may not show up if you aren't caching files...)

 

9 minutes ago, doubley said:

I just ran a memtest and it came back saying there were no errors.

To get a good workout of the memory, it should run for at least 24 hours without any error.  But you could delay doing this (now) until you have checked out some of the other things. 

I have exact same problem while Plex, Unbalance, and Mover running at same time.