beautypg.com

Cx set autodetect=on|off disk=|all – Avago Technologies 3ware SAS 9750-4i User Manual

Page 85

background image

Controller Object Commands

www.lsi.com/channel/products

77

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=on|off disk=|all

This command is only for 9750 and 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 to automatically detect and immediately spin
up the drives. This command can change the default behavior and set the
controller to do a staggered spinup for hot-swapped drives.

autodetect=on|off enables or disables automatic detection of drives on the
controller’s ports for staggered spin-up.

disk=|all specifies one or many disks (that is, drives, ports, or vports).
If a port is empty (no drive is inserted), the echo message of the command
refers to a port. If there is already a drive inserted, the message refers to a
disk. The example below shows that autodetect has been set to off to initiate
staggered spin-up during hot-swapping, where port 3 was empty and ports 5
and 6 had drives inserted.

Note:

Failed drives can be drives that have mechanically failed, or they can be

drives that have been disconnected from the controller long enough to cause a
drive timeout error and for the controller to classify them as failed.

Note:

The autodetect setting cannot be shown in CLI or displayed in 3DM 2 or

3BM. This feature may be added in a future release.