Reconfiguring sonarr/radarr/sabnzbd so that all processing of nzbs occurs on an SSD, then sonarr/radarr grabs the completed files and adds them to a different share that is on 3 HDDs.

 

I have it set up like this:

 

2 shares for nzb handling by SABnzbd, "incomplete" and "complete", under "included drives" I selected only the SSD (disk4). SABnzbd correctly downloads to and unpacks only on the SSD (disk speeds no longer throttling performance as they were when it split these operations across the SSD and one of the HDDs)

 

1 share for storage, called "data" with subfolders "movies" and "tv" - these are the "root folders" designated in radarr and sonarr. Share/folder structure looks like this:

 

user

 -sabnzbd incomplete (share with disk4 as the only included drive)

 -sabnzbd complete (share with disk4 as the only included drive)

 -data (share with all drives except disk4 included)

  --movies

  --tv

 

SABnzbd correctly receives instructions to download, downloads and unpacks all on disk4 as it should. Sonarr then sees the completed episode pop up in the complete folder, and proceeds to move the whole thing onto disk4. With krusader I can see that sonarr creates a data -> tv path on disk4 despite this path/directory not existing at the start of the process.

 

I've tried every combination of include/exclude logic on the data share and nothing seems to work (even after restarting the array). I've tried setting the data share to fill-up since disk1 is one of the 12TB HDDs that I want things to end up on, that didn't work either. What am I doing wrong here?

SSDs in the parity array cannot be trimmed, and can only be written at parity speed, so this was likely the cause of any "throttling".

 

You will probably have to specify a disk path in the docker to get what you want. Linux "move" just "repaths" files in /mnt/user.

 

See the CAUTION section here:

 

https://docs.unraid.net/unraid-os/manual/shares/user-shares/

 

 

By throttling I just mean sabnzbd download speeds were being crippled by write performance to the HDDs and unpack performance was very slow, both of which go much faster now (download speeds max out my 1g connection) and I've verified everything goes to the right disk by watching krusader during downloads/unpacks.

 

By specifying a disk path, do you mean a different parameter than the default host path field provided by unraid on the install page? Would this involve creating a disk share? (I don't know disk shares work but I've seen the section on the shares screen)

 

 

Just read the doc on disk shares. It sounds like I can just set up a disk share on the SSD, then moves from the disk share to the user share when sonarr performs mv would actually copy and delete instead of rename. A problem I can foresee is that sonarr requires read/write access to both of these locations and I'm not sure how to get around such a directory structure. SABnzbd could be installed on the SSD as that's the only disk it needs to access, but I have to pick somewhere to install sonarr.