All,

 

First of all I would like thank the creators and contributors to the UnMenu addon.  It works well, and really expands on the functionality of UnRaid... thank you!

 

Now to my question.  As I go through the UnRaid addons, as well as those on this forum, I started thinking of the impact some of these addons could have on the life of my flash drive.  I've also seen some addons offer the option to choose the install directory, while others don't.  I'm assuming that the authors of these various addons have taken this into account, but I figured it couldn't hurt to verify.  So I've listed below the addons that I'm going to be installing that I feel could cause a number of writes.  Any feedback I could get would be appreciated.  Thanks in advance!

 

AirVideo (I'm not sure if while converting files that it doesn't create a temp directory)

Transmission (I see this already has the option to install to a new location)

CouchPotato & Dependencies

Sickbeard & Dependencies

SABnzbd & Dependencies (thanks prostuff1)

Subsonic & Dependencies

The flashdrive is bootdevice only, during normal operation writes to it are very limited. The filesystem UnRaid is actually running in is completely in RAM, with as the only exception the /boot directory (and of course the mountpoints for the physical disks and shares). Any addon will need to be reinstalled each time you boot the system, the installation files should normally be placed somewhere under /boot (/boot/packages is used by unmenu and possibly others) and some kind of installation command is included in the script /boot/config/go.

 

Most of the apps you list will have some application and configuration files that will be placed in the RAM filesystem but the serious writing should be done to a physical drive in the system (this could be one or more parity protected drives, the cache drive or a standalone drive; with the first option not recommended for write intensive apps like SABnzbd)

The flashdrive is bootdevice only, during normal operation writes to it are very limited. The filesystem UnRaid is actually running in is completely in RAM, with as the only exception the /boot directory (and of course the mountpoints for the physical disks and shares). Any addon will need to be reinstalled each time you boot the system, the installation files should normally be placed somewhere under /boot (/boot/packages is used by unmenu and possibly others) and some kind of installation command is included in the script /boot/config/go.

 

Most of the apps you list will have some application and configuration files that will be placed in the RAM filesystem but the serious writing should be done to a physical drive in the system (this could be one or more parity protected drives, the cache drive or a standalone drive; with the first option not recommended for write intensive apps like SABnzbd)

 

Question about SABnzbd I/O - how much writing is done with this package? If your temp download and complete download are in your array, what's really being written to the flash? Once the package loads on boot, what is needed from the flash? Also, having SABnzbd's log file going to /var/log/* removes that writing. What am I missing here? I'm asking because I have SABnzbd installed on my flash, but I'm not too sure how to detect the I/O. Thanks!