Here's how to create and mount an encrypted unassigned device in UnRAID.
1) Make sure the unassigned devices plugin is installed in UnRAID. :-)
2) Wipe the device
I do this to remove any old partition tables, etc., and I think the easiest way to do it is on the command line. Change the "of" device to your unassigned device. Confirm you have the right device!
dd if=/dev/null of=/dev/sdb1
3) Create partition table in UnRAID
You can also do this via the command line, but I prefer to use the UnRAID GUI for this to ensure it's created the proper UnRAID way. It will also format it.
4) Encrypt and format the device again
Encrypt it using the same passphrase you used for any encrypted array. Otherwise, it won't mount in the GUI.
5) Try mounting it in the GUI
Try mounting it in unassigned devices. Hopefully it will mount and you're good to go!
I've been figuring out how to block or redirect web traffic in Nginx based on the country geoIP.
* You need the package nginx-extras for this because this package has the geoIP Nginx plugin.
* I used Japan (JP) in these examples, so change the country code to whatever you wish.
APPROACH #1 - BASIC
This uses a locally-downloaded GeoIP database.
- Rsync plugin
- User Scripts plugin (if you want to schedule the jobs)
- Unassigned Devices plugin
RSYNC TO UNASSIGNED BACKUP DRIVE
I often configure rsync jobs to backup critical data to an unassigned drive outside the array. My scheduled job looks something like this:
rsync --archive --delete /mnt/user/SourceFolder/ /mnt/disks/TOSHIBA_MD05PBA60_1900876554/DestinationFolder/
RSYNC TO ARRAY BACKUP DRIVE
I read about a very interesting alternative backup approach with UnRAID. Instead of creating an unassigned drive to use for the backup, you actually add it to your array. Configure your shares to never use this drive. The idea here is that the backup drive will be a member of the array, but completely excluded from any and all shares. Then setup an rsync job like this:
rsync --archive --delete /mnt/user/SourceFolder/ /mnt/disk4/DestinationFolder/
* Where disk4 is your backup disk.
An advantage to this approach is that the backup drive is an array member, so it's protected by parity. A disadvantage is that the drive is an array member, so it's not as easy to just pull the backup drive out if necessary. One scenario that comes to mind is if you want to rotate the backup drive with another one (e.g. off-site). Physically pulling the drive would affect the array and parity would have to be rebuilt. It would be easier to use an unassigned drive in that scenario.