Arcaeus

So it sounds like it should go to /mnt/user/Downloads then? And based on how small my cache drive is, I'm just hinking of setting it to cache-no so I don't have to keep checking on it and/or it locking up my dockers.

Yes, I have SABnzbd's /data path mapped there. I also have been transferring files back and forth from my server to my main rig in order to rename the files properly. I think that may be adding to it too.

@trurl Ok cool, good to know. So I'm still having issues with my cache disk filling up. I have cache = no, have stopperd and restarted the docker multiple times, but it keeps writing to that disk. Do I need to delete all of the undownloaded torrent files out of Deluge and re-add them? or what?

@trurl Ahh that makes more sense. I was trying to figure out how it could do RAID across different sized disks. So now is there a way to decrease the loading times of the array (making it faster), outside of having everything on the cache disk? Or is that just what it is? And in your opinion, what would you say Unraid really excels at? What is the use case where someone would choose Unraid over something else? Say, a Windows 10 computer with a bunch of drives in RAID 5/10?

@trurl I understand, thank you for writing all of that out. Now the more disks you have in the system, the faster your overall transfer/load speed should be, correct? Doesn't Unraid use a Raid 5 kind of system to spread the data across the array?

Alright, I'll work through this. Isn't that what the cache drive is for? To write everything to before moving it out to the array? If I turn that off, doesn't that defeat the whole purpose of having the cache drive there?

tower-diagnostics-20190211-0638.zip

Ok, confirmed that all of those are set as instructed, with new diags on the way.

@johnnie.black Thank you for sending that little walkthrough over. Super helpful. Ok so I got the docker image back and things seem like they're pretty much up and running. However, my cache drive is still not emptying out regularly and I don't want the dockers to lock up again due to it being full. I've manually ran the Mover, but it seems to complete without really moving anything. Why would this be? Do I need to pause my downloads in Deluge so the files aren't being used and it can move them?

Ok, Mover completed. However, When I click on the Docker tab, it still says "Docker service failed to start". is there a terminal command to start that, or do I have to reboot the whole server?

And how often do you have your parity check set to?

Ok, went in there and confirmed that it is set to cache = yes. Mover is still running but after 15 minutes I don't see any change in the used/free space. Shouldn't moving files be a straightforward process? Or is it slower due to a parity check/multiple drives/etc?

@johnnie.black Ahh ok, I misunderstood that. Looks like Mover is running now so we'll see how far that gets. @trurl Alright, that is processing, will post results on completion.

Here it is. I wasn't sure if it was logging anything due to possibly not actually running. tower-diagnostics-20190210-0446.zip

@trurl Yes, both. Mover logging is on and the dockers failed to start, so should be off.

@sminker Ok great I'll try that. However, when I click on the "Move Now" button, it shows the "Disabled - Mover is Running" text. I refresh the page, and the button is lit up again like it's not actually doing anything. If I remember correctly before, I could switch tabs and come back to the Main tab, and if the operation was running, it would still be grayed out. I tried it yesterday, and no data seems to be moved off of the drive.

So that ties into another issue I'm having here: Im working on getting the move log working atm.

tower-diagnostics-20190208-0651.zip

My appdata share is set to Prefer, but that shouldn't take up 170-some-odd-GB, right? I only have like 6 dockers on there at the moment (Plex, Emby, Sonarr, SABnzbd, Krusader, Deluge) so my guess is that there are some torrent files that aren't being moved over properly. And where is move logging located again? If I remember correctly, it was on the Main tab with all of the Mover settings. Which for me is not displaying at all.

So this morning I wanted to change the name that I had for the binhex-deluge docker to just Deluge. So I opened the settings, changed the name, and hit save. The operation failed, and deluge wouldn't start up again. I tried to turn off all of my dockers and restart them, but then they wouldn't restart again. So after waiting for the parity sync to finish, I rebooted the server in hopes that would fix the problem. The server rebooted, and the all the disks mounted after a minute or two. However the array is taking forever to start up. It's been about 40 minutes so far with no change. It's previously never taken so long and I'm trying to figure out why. I haven't rebooted yet in case you guys need the diagnostics files, and figured I'd reach out first before doing anything for this reason. Thoughts?

@sminker I went through and checked all of the shares, and they are all set to use ALL disks. It looks like it started to move some stuff over, but then stopped after it got past the 1TB mark. Based on the guide @trurl sent over, it seemed like it would make multiple passes until the data was spread relatively "evenly" across the disks. Also, my cache drive keeps filling up. I've started Mover manually to get that off of there, but it doesn't seem to be completing the move. It will get down to like 178GB or so and then just stop. Which then fills up again and starts giving me all of these warning messages.

Ok cool. It has about 1.14TB left so that should happen soon.

So I've just set up my Unraid server and got it running (with a HUGE thanks to @Squid @Hoopster @Frank1940 and others). I started with 2x 4TB (one parity and one data) and a 256 GB 850 Pro SSD as cache from an older computer. After I get everything up and running, I cleared off another 2TB and added it into the array. I'm looking through my drives and see that the 4TB data drive is 75%ish full, and the 2TB I added afterwords is basically empty. So I was wondering, how does Unraid move/spread data across the drives? Is that what the Mover does, or does that just transfer from cache to Array? And when I add another drive later on, is there a process I should do to make sure that it's spreading the data evenly? Or any setup tips for that kind of thing.

It has not been yet. I was following SpaceInvader One's video and he was just setting up all of the dockers and everything before doing a full sync. Plus, I didn't have that much data on there and I knew I was going to be adding another drive, so didn't worry about doing the parity sync until I was done setting everything up.