Is it possible to setup a separate drive that only SABNZBD uses to do its "dirty work" like downloading, verifying and unpacking, outside the array. The unpacking can be done straight to the array without using the cache drive.

Can someone give me a detailed description on how to do this, maybe by using SMB extra? I'm not a linux expert.

I am currently using 2.5" hdd mounted via /boot/config/go script

 

#!/bin/bash
# Start the Management Utility
/usr/local/sbin/emhttp &
mkdir /mnt/apps
mount -t reiserfs /dev/sdb1 /mnt/apps

 

SABnzbd config files are in /mnt/apps/sabnzb and that's where 'dirty work' is being done - I see no problem configuring SAB so it's extracting downloads straight to user shares (I'm moving them manually once a day, to minimize the disk spin up time)

Right now I have sab installed in the apps directory on my cache drive. It is setup so that the mover is moving the unpacked files to the array at night.

 

I want to use a SSD for cache drive where the apps incl. sab are installed. I want to setup sab so that it is doing its "dirty work" on  a separate scratch_drive(poss. 2.5")  outside the array and the unpacking straight to mnt/user0/file_dir.

So I like to setup this "scratch_drive" separately with SMB-extra.conf. I like detailed information on how to do this.

 

Just mounting this drive also works I think. Is it at all possible with SMB-extra.con? What are the drawbacks and benefits of both methods?