Noob

I mounted it so I could answer your question. Explorer shows Media to have 160GB free, which differs from the free space being reported in the unRAID GUI.

It doesn't report free space because the share isn't mounted, it's mapped. See screenshot of "My Computer" for reference.

It was already set that way, but I changed it, applied the change, and set it back. Still getting the same error.

Very little has changed since I posted my last diagnositc, other than shuffling some drives around. New data is attached. In order, the answers to your questions are: 1) There are six data disks in the array. Free space is as follows: 31GB, 125GB, 71GB, 186GB, 7GB, 250GB. Total free space is nearly 700GB. 2) I'm copying to the Media share which is set to include all drives. The error pops up in Windows File Explorer when I try to drag & drop my new data onto the share. See attached error message screenshot. It is immediate, the transfer doesn't even begin. The 140GB is split over roughly 20 files. 3) Yes, I understand how minimum free space works. I don't anticipate moving any files to the media share that are over 40GB at this time. If I do in the future, I will update the setting accordingly. Thanks for your help.

So, I'm back again guys. Unbalance worked itself out after I manually rearranged some files, but I still can't copy anything large to my array. I have 700GB free with minimum free space set to 40GB. When I try to copy over 140GB unRAID gives me an error saying I'm short 80GB (same error as in my initial post). What causes this? How can I try to resolve it? Having an array that won't accept data is wearing on me :-/

Thanks so much! I appreciate your help. Exporting the flash drive as a Samba share was a perfect solution.

I mentioned the old data in my original post. I suspected this was the trouble with formatting the disk and dropping it from the array. So, if I must zero the disk before reassigning it as parity, how can I access the flash drive to add the "clear-me" script to the correct folder? Are there any options other than SSH?

I've looked over the documentation on the Wiki's Shrink Array page: https://lime-technology.com/wiki/index.php/Shrink_array#The_.22Clear_Drive_Then_Remove_Drive.22_Method This process is quite long considering how simple the task is that I'm trying to accomplish. Perhaps I'm not understanding the way parity works? It looks to me like some of these steps aren't necessary. I emptied my drive using rclone, so it has an XFS file system on it but contains no files/folders. It is not empty, though, because that data is still on the platter. Rather than using the "clear-me" script and writing zeroes to the entire disk, can't I reformat it to another file system and then drop it from the array before writing any data to it? The Wiki says when the disk is clean formatted parity will be automatically updated to reflect that the disk is empty. Why is there a second step of using the disk clear script at all? I'm trying to accomplish reassigning this emptied data disk as a 2nd parity disk. If there's an easier way to do this than dropping it and reassigning it, please let me know. My only requirement is that parity not be lost during the reassignment. Thanks guys!

Bingo! I think I've sorted out this problem. The folder that is causing unBalance to generate an error is 506GB, whereas my largest target disk is only 500GB. It looks like unBalance doesn't want to split the folder to fit on two drives, so I need any single drive to have at least 506GB of space in order to make the move. I'm going to manually shuffle a few files off of that drive and onto another and I expect unBalance will move right along after that. Thank you all for the suggestions Live and learn!

I never configured that setting, so that must have been the default that came with the plugin. Any idea how to adjust it? EDIT: I found it with only a cursory amount of searching. See screenshot. It's 450MB, so that should not be creating this failure. What's next? Anyone have additional suggestions?

Thank you all for your helpful replies. To be clear, I understand that unRAID doesn't stripe data. My minimum free space settings are set above what I need by quite a lot and, even considering that, I have space left, but unRAID will not allow me to store data to the disk. My split settings are as generous as the GUI will allow me to configure them to be. I found the log for unBalance, which I think is a helpful addition to the diagnostics. I've included a helpful execpt from unBalance, indicating that each drive has reserved free space of 450000000 (is that 45GB?), which doesn't correspond to any of my share settings. Any help is greatly appreciated. unBalance_Log.txt diagnostics-20170215-0053.zip

I found it! The Docker Safe New Permissions Command is a new option located in the tools tab of the unRAID GUI. It's not run from within the App.

I've looked through this thread a little bit (admittedly, I didn't go all the way to the beginning), but I cannot find sufficient information on the Docker New Safe Permissions Command. How do I run it? Where do I run it from? Thanks guys! Great plugin, I'm just a little lost.

First, I don't know how to post my diagnostics. More detail would be great. Second, my split level for all shares is set to "Automatically split any directory as required," so I don't believe that to be the cause.

I've had two failures during my current evaluation/trial period that both seem odd to me. Perhaps someone more familiar can explain how the storage limits work in unRAID. First, my array had 400GB of space left in it and I attempted to copy 150GB to it using Windows File Explorer. I got an error stating that I was 80GB short to complete the transfer. That roughly corresponded to the minimum free space setting I configured for the share earlier. I went back to the settings page for the share, made minimum free space zero, and tried to copy a second time. Same error: 80GB short for a 150GB copy. I have 400GB free. What gives? Second, I'm running the Unbalance plugin to clear a drive with 900GB on it in order to assign that drive my second parity disk after it's empty. I added two 500GB disks to the array, precleared and formatted them, and they had over 900GB of free space collectively. Using unbalance, I selected the 900GB drive as the "From" drive, and left all of the other drives checked as "To" drives. Unbalance gave me an error stating that I didn't have enough space available to clear the 900GB of data off my drive. Lies! I had about 250GB on the array before I added the two 500GB drives. I have more space than I need for this transfer. What gives? Why am I getting so many weird and blatantly wrong free space errors with unRAID?