I've recently updated my UnRaid to 5.0.5 and it has been working ok.  I have some fine tuning to do, but the basics are all good.

 

Last night I was unable to access the array through either my browser, my network shares or telnet.  The issue was discovered when I went to transfer a 4GB ISO file over from my local machine to the array.  I wasn't watching the transfer to see if anything moved before the server became inaccessible.  I had no option but to hold the power button in and shut it down.  I knew this would force a parity check once I booted it back up, but that wasn't a major issue as I was going to bed anyways.

 

This morning, after the parity check finished, I see this in the summary:

Last checked on Sun Apr 27 04:45:37 2014 EDT, finding 556 errors.

 

There are no corresponding errors listed in the device status screen, yet the syslog does show the corrections.  I'm not seeing in the syslog if the errors are specific to one drive or error of little to no concern that are somewhat common when a sudden reboot occurs.

 

One side question:  I found it somewhat odd that of my 12 drives (11 Data, 1 parity), that only 4 drives ever spun down during the partiy check.  My parity drive is 2TB.  I only have one 2TB data drive.  Would you not have figured that if some of my 1.5TB drives spun down, they all would have spun down, as the parity check process would have been finished with all of them at the same time.

 

Thanks for the help.  Syslog attached.

 

syslog-Apr.27-2014.txt

Run a another parity check. There should be zero errors.