Controller Object Commands
/cx set autorebuild=onoff
This command is only for 9550SX , 9590SE, and 9650SE controllers.
This command turns the Auto-Rebuild policy on or off. By default, autorebuild is on.
If the policy is on the firmware will select drives to use for rebuilding a degraded unit using the following priority order.
1.Smallest usable spare.
2.Smallest usable unconfigured (available) drive.
3.Smallest usable failed drive.
Note: Failed drives can be drives that have mechanically failed, or they can be drives that have been disconnected from the controller long enough for the controller to classify them as failed.
Enabling Auto-Rebuild allows you to add a drive to the controller and have it be available for a rebuild as soon as you tell the controller to rescan, without having to specify it as a spare. It also means that if you accidentally disconnect a drive (causing the controller to see it as a failed drive) and then reconnect it, the controller will automatically try to use it again.
If the policy is off, spares are the only candidates for rebuild operations.
Example:
//localhost> /c0 set autorebuild=enable
Setting Auto-Rebuild Policy on /c0 to enable ... Done.
/cx set autodetect=onoff disk=<p:-p>all
This command is only for 9000 series controllers.
This command is associated with the staggered spin-up feature when hot- swapping drives. When staggered spin-up is enabled (see command /cx set spinup and /cx set stagger), during a reset or power on, the controller will spin up all detected drives with a delay between each spinup, allowing the spread of power consumption on the power supply. When a drive is hot-swapped, (as opposed to when it has just been powered on or reset), the default behavior of the system is immediate spin-up. This command can change the default behavior and set the controller to do a staggered spinup for hot-swapped drives.
Note: The autodetect setting cannot be shown in CLI or displayed in 3DM or 3BM.
This feature may be added in a future release.
