A couple of nights ago unRAID crashed while was watching a video streaming from it.  I could ping it, but the webgui was unresponsive, I was unable to ssh to it, and the direct console was frozen.  I hard powered it off and started a parity check after reboot.

 

The next day, the webgui had the red X on drive 2, and it said it was 67% done rebuilding the drive.  Shortly after that it crashed with the same symptoms.  When I rebooted I looked at drive's 2 smart status.  It all looked good, no bad sectors.  I ran a short smart test, and it completed with no errors.

 

Last night I started a parity check again, and it was 37% done when I went to bed.  It was unresponsive again this morning.

 

I don't have any syslogs because I've had to reboot unRAID each time to get it working.  I've got syslog on screen and to a text file with "tail -f" now.

 

Should I try doing another parity check to capture the syslog?  These crashes can't be good for the system.  I have 2 new drives for the system, but both are bigger than the current parity, and they are not precleared.  I was thinking my other option would be to do a parity swap with one of the new drives.  If it rebuilds the drive fine and completes a parity check, I can preclear the second new drive.  I can swap the 2 new disks so I  run a proper preclear test on the first one.

 

Is there anything else I should try first?

diagnostics-20160416-0738.zip

I'm sorry you seemed to have been ignored, but I suspect others found what I found, no issues at all in syslog or Disk 2.  There are no apparent clues why it would crash.

 

One thing that runs at night, and would add extra load when running the parity check, is the Mover.  Try running it manually and watch for errors.

 

* Your system was somewhat in awe of the 8TB drive!  First time I've seen a USB driver reporting "Very big device"!  But then again, I doubt there are very many 8TB drives on USB 2.0 ports!

I ended up getting it all working.  I hooked up a monitor to the server and ran another parity check.  It crashed, but there was a message on the monitor that was not in the syslog.  It was something about running out of memory and directory caching.  I rebooted, disabled the folder caching plugin and ran another parity check.  It completed without problem.  I ran another parity check with folder caching enabled and it completed normally.  I  haven't had any problems with it since.

 

My computer did seem shocked at the 8TB drive on USB!  I used an external enclosure to preclear the new drives and it didn't occur to me at the time that I don't have USB 3.0 on the front panel.  But the preclears ran without problem and completed in a normal amount of time.