September 15, 200916 yr I'm running unRAID 4.5b6. Until recently, my array consisted primarily of two 1.5TB drives and a couple of <300GB drives. This week I replaced one of the small drives with a third 1.5TB. the array is up and running, and all appears to be normal, but for some reason unRAID appears to be reluctant to place files on the new drive. For instance, I have a \Backups share defined with Allocation method: High-water Min. free space: 0 Split level: 0 Included disk(s): <blank> Excluded disk(s): <blank> but every time I create a new Windows Image Backup to that share, it places the file on the drive that's aready 80% full, completely ignoring the new drive. I have tried changing the allocation method to Most-free, and have deleted the entire \\Tower\Backups\WindowsImageBackup directory, but I keep getting the same behavior. The system hasn't even created a /Backups directory on the new drive. Is there a hole in my understanding of the allocation algorithms, or is something awry?
September 15, 200916 yr The problem, I think, is that the definition of split level 0 has changed between the version you were using and the new one. See here in the release notes: http://lime-technology.com/forum/index.php?topic=3760.0 If YOU create a "Backups" folder on the other disk it will probably start using it. (you create the folder using the disk share) Or, if you change the split level to 1 or greater, it will create the "Backups" folder for you (I think) Joe L.
September 15, 200916 yr Author Aha! You are correct, sir. I changed the Split Level from 0 to <blank>, and it's back to functioning as I expected. Thanks!
Archived
This topic is now archived and is closed to further replies.