There is nothing keeping you from using the protected array (/mnt/disk1/) to install your stuff. The convention of using the cache drive came about to keep from having a second drive spindle up all the time (parity + array disk vs only cache). You will probably benefit in other ways from having a cache disk, but you've gotten far enough with learning how things work to make that decision on your own.

This is true, but using an array drive can have the same pitfall of the app creating the directory before the array starts which will cause the array to not start. This is something I hope to get fixed with my plugins soon.

I got rid of Snap and just installed on the array.  I'm not using a parity drive yet as right now this is just for proof of concept for the boss (wife).  Once she sees how easy it is to use with our WDTV, I think she will be sold

Actually, sickbeard plugin downloads sabnzbd which conflicts with the current sabnzbd installation. So basically Sickbeard plugin installs sabnzbd again. I think they changed the download paths over at midgetspy/github. Easy fix is to not use the SickBeard Plugin and install everything manually (aka download files directly from sickbeard, edit go script to run sickbeard). I hope this helps.

I'm not sure I follow what your saying? The Sickbeard plug-in does not download sab in any way, it has some of the same dependencies but if they are already installed they are not re-downloaded or re-installed.

 

 

I was setting up my friends unraid server last night and when using the sickbeard plugin, it basically installs sabnzbd with no sickbeard to be found. The only workaround I found was to avoid the sickbeard plg altogether.

 

Then I read through this post again and realized that the issue that is being discussed is not at all related lol.