May 24, 201214 yr What is the intended behavior of this setting besides starting up the array automatically upon boot ? is there any circunstance when this setting will revert back to NO ? or is there any circunstance when the array will start even if this setting is set to NO ? or vice-versa, the array wont't start even if it is set to YES ? is there a bug that displays the wrong info on this setting ?
May 24, 201214 yr What is the intended behavior of this setting besides starting up the array automatically upon boot ? is there any circunstance when this setting will revert back to NO ? or is there any circunstance when the array will start even if this setting is set to NO ? or vice-versa, the array wont't start even if it is set to YES ? is there a bug that displays the wrong info on this setting ? what version of unRAID?
May 24, 201214 yr What is the intended behavior of this setting besides starting up the array automatically upon boot ? is there any circunstance when this setting will revert back to NO ? or is there any circunstance when the array will start even if this setting is set to NO ? or vice-versa, the array wont't start even if it is set to YES ? is there a bug that displays the wrong info on this setting ? My understanding is that it is what you stated -"autostart upon boot". Now, for the real-world and my setup..... I DO NOT use the auto-start. Why? Because the question becomes WHY did the system boot. In my case, if I'm manually restarting the server with proper shut-down, etc -- then I'm standing there to do the final step of starting the array anyway. BUT, if the system has crash/rebooted, or power-fail rebooted, then I, personally, don't want the array to auto-start. My procedure is to manually start the array in "maintenance" mode (a feature of 5.x I believe) and do a Parity-Check without Fix. That lets me see how bad things might be, before I make any rash commitments of a "repairing Parity Scan" that I can't "unring-that-bell" if I wanted to. As an aside, this is how I found a problem with the SIL controllers and multi-ports -- I had a hard power failure, ran Parity-Check without fix several times -- and got differing amounts of errors to correct. That told me I also had some sort of inconsistent results coming from my box. Tracked it down to the SIL controller and mult-port external cabinet... And yes, if there is a drive missing or other reason the Unraid server "thinks" there is an invalid confirmation, the array will not start, regardless of the setting. Regarding your other questions about bugs, strange behavior, etc -- I haven't seen those.
May 24, 201214 yr Author currently using 5.0-RC3 I am more interested in understanding when the array will or won't autostart, based on the setting, and based on different events that might happen with the array in parallel, I've seen events when the array started automatically, but the setting was NO, so I was wandering if there is any known bugs. if not, I will do more testing
Archived
This topic is now archived and is closed to further replies.