New Drives Attached to a MegaRAID Controller
When you insert a new drive on a MegaRAID system, if the inserted drive does not contain valid DDF metadata, the drive appears as JBOD for MegaRAID entry-level controllers, such as the SAS 9240-4i/8i. If the drive does contain valid DDF metadata, its drive state is Unconfigured Good.
A new drive in JBOD drive state is exposed to the host operating system as a stand-alone drive. Drives in a JBOD drive state are not part of the RAID configuration because they do not have valid DDF records. The operating system can install and run anything on JBOD drives.
Automatic rebuilds always occur when the drive slot status changes, for example, when you insert a drive or remove a drive, so that a hot spare can be used. However, a new drive in JBOD drive state (without a valid DDF record), does not perform an automatic rebuild.
To start an automatic rebuild on the new JBOD drive, you have to change the drive state from JBOD to Unconfigured Good. (Rebuilds start only on Unconfigured Good drives.) After you set the drive state to Unconfigured Good, the drive state information always remains on the drive, and you can use the drive for configuration.
See Marking a Drive Offline or Missing for the procedure to change a drive to the Unconfigured Good drive state. See Rebuilding a Drive for the procedure to rebuild a drive.
DB09 000202 -14 37857 -02, Rev O, November, 2012 |
Copyright© 2012 by LSI Corporation. All rights reserved. |