A Rebuild Does Not Work
A rebuild does not work in the following situations:
- The virtual disk is nonredundant — For example, a RAID 0 virtual disk cannot be rebuilt because RAID 0 does not provide data redundancy.
- There is no hot spare assigned to the virtual disk — As long
as the virtual disk is redundant, to rebuild it:
- Remove the failed physical disk and replace it. A rebuild automatically starts on the new disk.
- Assign a hot spare to the virtual disk and then perform a rebuild.
- You are attempting to rebuild onto a hot spare that is too small — Different controllers have different size requirements for hot spares.
- The hot spare has been unassigned from the virtual disk — This occurs on some controllers if the hot spare is assigned to more than one virtual disk and is being used to rebuild a failed physical disk for another virtual disk.
- The virtual disk includes failed or corrupt physical disks — This situation may generate alert 2083. For information on alert messages, see the Server Administrator Messages Reference Guide.
- The rebuild rate setting is too low — If the rebuild rate setting is quite low and the system is processing a number of operations, then the rebuild may take an unusual amount of time to complete.
- The rebuild is canceled — Another user can cancel a rebuild that you have initiated.