Ok, a bit of background to begin with in case this affects a step that I've missed.

 

I originally installed unRAID 4.7 after first building my server with the intention of trying unRAID, but quickly discovered that I could not transfer the disks of data I already had onto the machine as 4.7 wasn't recognising my USB3 Icy Box caddy to mount the disks. So I upgraded straight to 5.0-beta6a and found that my USB3 PCIe card was recognised and worked. I added a few shares, including one called Media, and proceeded to move all my data onto the array.

 

Once the transfer was complete, I added the drives originally containing the data into the server and added them to the array. If I click on the Shares page, the total available shows as the correct value I would expect, however when the mover script moves any new data off of the cache disk onto the array it only seems to move the data onto the disks first added, never the 3rd or 4th disks that were added later.

 

The share is set up to be high-water, and it does seem to be conforming to this, but only with disks 1 and 2. When it reaches a threshold, the data is put onto the 2nd drive instead of the 1st and vice versa. My other shares are also set the same way and this is also happening to them.

 

So, the question I'm asking is: did anything change in unRAID 5.0 that I didn't do when I added the new drives / is there a new required step from the 4.x days seeing the guide I followed was based on that? Any help you could offer would be greatly appreciated, I don't want to use up all the space on the first 2 disks before it starts using disks 3 and 4. I'm not even sure where to look to debug this, even if I am fairly knowledgeable in Linux. I've browsed the logs, and the /boot/config/shares folders, which show the same as the Shares webpage, no included drives nor excluded ones.

 

Image showing the installed drives, note the low writes and space usage on disks 3 and 4:

http://i53.tinypic.com/icv9kg.png

 

Image showing how this share is set up, showing no excluded drives:

http://i55.tinypic.com/ezk2hd.png

 

Also, is it a intended feature that the mover script does not run on crontab after it has been run manually? I seem to be having that, and it's annoying when I copy something I'd like instantly copied into the parity array and forget to then press apply afterwards to revert it back to automatic.

 

Thanks for your help

Your split level is likely too low.

Your split level is likely too low.

 

It's going correctly between the first 2 drives, and refusing to add any to the second 2. How does changing split level change which disks are included? My understanding of how split level works should not influence which drive the data ends on, merely that all data from within a folder from that and below should not be spread across multiple drives.

 

As an example though, my set up is similar to what is described on the FAQ as a split level of 2, which is what this share is set to.

 

Here's an example of Split Level = 2: http://lime-technology.com/forum/index.php?topic=1837.msg13416#msg13416

 

/Media/TV/

/Media/Movies/

/Media/Music