dirrtyjoe Posted June 17, 2011 Share Posted June 17, 2011 Upon restart the array is not starting automatically despite having the setting enabled. Does anyone have anything that might cause this to happen? I believe it started happening after installing the unMENU script to install/start sab/sickbear/couchpotato which are stored on the cache drive. What appears to be happening it that the script to start those services is creating /mnt/cache before it has time to come online...does this sound accurate? Is there a fix? Link to comment
Joe L. Posted June 17, 2011 Share Posted June 17, 2011 Upon restart the array is not starting automatically despite having the setting enabled. Does anyone have anything that might cause this to happen? I believe it started happening after installing the unMENU script to install/start sab/sickbear/couchpotato which are stored on the cache drive. What appears to be happening it that the script to start those services is creating /mnt/cache before it has time to come online...does this sound accurate? Is there a fix? yes, don't start those until after the array is started. In other words, get the author of those scripts to wait until AFTER the /mnt/cache drive is present. Joe L. Link to comment
dgaschk Posted June 17, 2011 Share Posted June 17, 2011 You can delay the start of those scripts by adding "sleep 60" to your go script before they are called. If 60 seconds is not long enough try 120 then 180, etc.. Link to comment
dirrtyjoe Posted June 17, 2011 Author Share Posted June 17, 2011 Thanks guys, I delay for 10 seconds up to 7 times until the cache drive is online then I continue my Go script and it seems to be working ok. Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.