B5rc-4

Array autostarted despite "Enable Auto Start" set to "No."

Anyone else have problems with B5rc4 autostarting the array when it is set to not autostart?

Just tried it here. No issues.

 

Edit: What I did notice was that "Enable Auto Start" defaulted to "Yes" after a reboot.

Same as mbryanr, does not start on reboot, but goes back to autostart.

Same as mbryanr, does not start on reboot, but goes back to autostart.

So the error (bug) is that the autostart=no does not survive a reboot. 

(it is apparently only effective for the immediate next reboot)

Same as mbryanr, does not start on reboot, but goes back to autostart.

So the error (bug) is that the autostart=no does not survive a reboot. 

(it is apparently only effective for the immediate next reboot)

 

Some would say that's a "feature"    But I'll fix it.

Some would say that's a "feature"    But I'll fix it.

 

;D

Same as mbryanr, does not start on reboot, but goes back to autostart.

So the error (bug) is that the autostart=no does not survive a reboot. 

(it is apparently only effective for the immediate next reboot)

 

Some would say that's a "feature"    But I'll fix it.

 

I would say it is fine the way it is, but for those that are reading the upgrade instructions would not know to uncheck auto start. I like this feature, but need to remember to uncheck it on a upgrade. I have forgot this once or twice.

Same as mbryanr, does not start on reboot, but goes back to autostart.

So the error (bug) is that the autostart=no does not survive a reboot. 

(it is apparently only effective for the immediate next reboot)

Correct

Why am I having the opposite problem?

 

Yesterday I went into disk settings to change the 'Force NCQ disabled' and 'Tunable (md_sync_window)' settings.

 

Now I can't get the array to autostart.

 

I can get startState in disk.cfg to show two different values - "" and "STOPPED", but neither seems to result in an autostart action.  I've tried setting it to "STARTED", but that had no effect.

 

Edit:

Oops ... I appear to have lied - now with the value of "STOPPED", the array has started up! 

I have it set to no and it has worked for many restarts.

I have it set to no and it has worked for many restarts.

 

"Worked", as in it has started, or "worked" as in it has done what it's supposed to do?

I have it set to no and it has worked for many restarts.

 

"Worked", as in it has started, or "worked" as in it has done what it's supposed to do?

 

My array has never automatically started after many restarts. I set it to "no" a single time, and it's stuck for a months. Running RC4 currently.