I'm new to unraid and a Linux noob - my apologies in advance!

 

My understanding of cache drive is to write the files on a scheduled basis to the array, as well as you can install plugins there too.  In an effort to keep plugins on a separate hard drive to my array, I want to use the cache drive strictly for plugins, but I'm wondering if plugins like transmission, couchpotato, and sonarr can still automatically move files over to my array if I disable the feature that moves files over on a scheduled basis.

 

Also, how do you effectively disable the mover, as my search results indicates a few different methods, one which is shorter, but a longer method that prevents option 1 from being overwritten whenever updated are made.

Hey, I'm fairly new here as well, but maybe I can help. What you want is actually fairly simple and quite close to what I'm doing. Couchpotato and Sonarr don't actually download anything by themselves so I'll skip those. That leaves sabnzbd and Transmission, they both have a configurable incomplete and finished folder for downloads.

So if you want none of the download stuff on the cache disk you could put the docker image and the appdata on the cache disk and create shares with caching disabled for the incomplete and finished downloads.

 

I personally have a share with caching enabled for the incomplete downloads as that process benefits a lot from caching, and then have the finished downloads on an uncached share.

 

Hope this helps,

activ

I actually do what all the download apps and plugins to live on the cache disk, I just wanted to make sure the mover wasn't trying to dump files over to the storage array, instead I want couch potato and Sonarr to move the completed files over to my array when the downloads are completed.  Cache drive for all my apps, storage for just storing completed files (movies, shows, photos, etc...)

Create a share specifically for your plugins and mark it as "cache only", that will make sure it works.

 

Another way to do it (but not the preferred one) is to create folders on your cache drive that start with a period (so like: .downloads), folders with a period are hidden and will not be moved.

 

Further more make sure you set all your other shares to "use cache drive: no"..

 

From with sabnzbd and transmission you just move your files to /user/movies when they are finished processing (for example).

 

Note however that this will limit the amount of files you can download at the same time to the physical space on your cache drive..

Can the completed files move still be automated with CP and Sonarr?

 

 

Sent from my iPhone using Tapatalk

Can the completed files move still be automated with CP and Sonarr?

 

 

Sent from my iPhone using Tapatalk

 

Yes, if you want to do that you need to make sure you set the share you download to be CACHE ONLY. If it's not cache only mover will move the files to the disk.

Yes, it is simple. Every plugin has access to the complete unraid file structure:

 

/mnt/diskx  (where x is a disknumber)

/mnt/cache (your cachedrive)

and /mnt/user/y  (where y is your usershare)

 

So lets say you create a cache-only share called sabnzbd (you do this from the unraid webgui), then this creates a folder called /mnt/cache/sabnzbd

 

Lets also say you create a user share called "SERIES" and you set it to not use the cache drive. This will create a folder called /mnt/user/SERIES

 

you install the sabnzbd plugin into /mnt/cache/sabnzbd

 

you create a folder (from windows) under that sabnzbd folder called "download", you set up sabnzbd to download into that folder. Then you tell sabnzbd to move completed downloads to (example) /mnt/user/series.

 

Whenever sabnzbd now downloads a movie it places all its temporary files on the cachedrive, when they are completed they are moved into the main array series folder.

 

It looks like you need to read up a bit on how stuff works, that will make it easier to understand this stuff.. Its not that difficult, but if you end up getting it in your head wrong it will remain hard to understand.

Thanks for all the help guys.  I got it all sorted out and working.  Understanding the file structure was my biggest hurdle I think. 

 

Cheers!

Little late to this thread, but I suggest you reconsider the use of plugins. All of these applications mentioned are available as dockers, and everything discussed can be done with dockers once you work out the details of mapping volumes.

What would be the impact on resources to run all these as dockers?

 

 

Sent from my iPhone using Tapatalk

Nvm, I found the answer already

 

 

Sent from my iPhone using Tapatalk

Nvm, I found the answer already

 

 

Sent from my iPhone using Tapatalk

 

What did you find?

Mostly no impact, but everything I read on dockers towards it being preferable.  In my case, I'm only running a handful of plugins.

 

 

Sent from my iPhone using Tapatalk