|
Symptom(s):
After a system reset or reboot with an array under going a full initialization, a background initialization is not started after the system becomes ready.
Cause:
During a full array initialization, if the system is reset or rebooted, the controller does not mark the array as inconsistent. Marking the array as inconsistent would enable a background initialization to be started after the system becomes ready.
Solution:
This issue would not be the default operation of the controller, as fast initialization must be disabled, then a full initialization started, and reboot or reset while the full initialization is on-going.
The user has the option to just ignore (no problems if the array is not fully initialized) and start a consistency check. Alternately, just delete the uninitialized array and recreate with the fast initialization option enabled.
This applies to:
| 
