I've seen a few people mention that you need to get unRaid to delay the starting of some things otherwise they lock up the array on startup and it never finished starting (I have experienced this myself). I was just wondering how you go about this? My array doesn't start up automatically when I boot up the system for some reason so that makes it somewhat inconsistent. I guess what I'm really asking is:

 

1. How do I get my array to auto-start on boot?

2. Where do I add delays for installation of plugins (.plg)? I see that packages are installed in the go script, so I guess I could easily just add a sleep to the go script, but see no mention of where plugins are installed.

3. Is there a script which runs once the array has finished starting which I could append the installation commands to? This seems like it would be the best solution as it would mean that if the array doesn't start on boot (which, as I said, mine does not) then it won't run these scripts until the array has finished starting.

4. This is more of a general question, but why does the cache drive need to be started as part of the array? Can't it just be automatically mounted on boot?

Oh also - does setting plugins to "enable" mean that they're installed on startup, or that they're started on startup (with them being installed whether or not they're enabled). Because again obviously I could put a delay in the go script to run the program with a delay, but I'd need to know:

 

a) if setting it to disabled still installs it, then I'd just need to put the run command in the go script with a delay

b) if setting it to disabled does not, I assume I'd need to do "installplg", in which case, does it automatically start when unRaid starts?

I'd like to know how to do this as well.  My plugins are trying to start and it's causing the array to hang while starting.  It would be nice to delay the install until the array if up.

I also need this question answered.

Thanks

cache_dirs is designed to not start until after the array is online.  You can start it at any time.  It will simply re-schedule itself to check if the array is up each minute.  It will not start until /mnt/disk[1-9]* directories exist.

 

For others, the beginnings of event handling is in place, and still evolving in the 5.X series of unRAID.  There is a after array start and before array stop event, but very littly structure on how to best use them so far.  There is no package manager as of yet for .plg plugins.

 

So... write a package manager startup/shutdown module, and then convince all the developers to adopt it. 

 

Or, you can try the one I've been using that works in all versions of unRAID from the mid 4.5 series (4.5beta7 and newer).

 

Search for  "unraid_addon_control.sh" and use it to control your add-ons.  (I've been using it for about 2 years now)

 

Joe L.

Thanks Joe.