Hi,

 

As the title says, I'm new to unRAID and am having an issue with my array. Am running the beta versison (6.2.0-beta21 as a trial).

 

Followed the getting started guide and wiped all 4 drives with PreClear (Beta) and then created array with 1 parity 3 data. Setup a samba share called 'Media' and started copying all my videos to it. Left it running later found it had crashed at ~427GB into the transfer. WebGUI and samba share unresponsive, but could SSH in. Checked and load average in the 60s with very little showing in top, but SHFS using 100% of IO on IOTOP. Unable to shutdown via command line so had to hard reset the server.

Rebooted and everything ok, array stopped obviously so started it up and resumed the transfer. Got approx 3-4Gb in and same thing - it's transferring nice and quickly and then suddenly grinds to a halt.

 

Here are some screenshots of IOTOP:

- When the copy is OK: https://dl.dropboxusercontent.com/u/29878244/unraid_iotop_copy-ok_20160609.png

- When the copy locks up: https://dl.dropboxusercontent.com/u/29878244/unraid_top_lockup_20160609.PNG

 

Nothing appears in syslog or any logs in /var/log/* at all when this happens and the only way I can seemingly recover from it is with a hard-reset.

 

My setup is as follows:

 

HP N54L

4 x 4TB WD Red

16Gb ECC Ram

 

Configuration Screenshots:

Main - https://dl.dropboxusercontent.com/u/29878244/unraid_main_20160609.PNG

Share - https://dl.dropboxusercontent.com/u/29878244/unraid_share-media_20160609.PNG

Disk Settings - https://dl.dropboxusercontent.com/u/29878244/unraid_disk-settings_20160609.PNG

 

Would really appreciate any help anyone can offer. This issue is the only thing stopping me from buying the full licence and running this permanently.

There was a issue in beta 21 with this problem.  It is (supposedly) fixed in beta 22.

 

Try that if the issue is not fixed, post the issue in the thread for the beta 22 release along with your diagnostics.zip file.  (Apparently you know how to get this file but, just in case, type  diagnostics  at the CLI and the file should be in the    logs    folder on the Flash Drive.)