User's Manual

262 Troubleshooting
• Cannot Create a Virtual Disk
• Virtual Disk Errors on Linux
• Problems Associated With Using the Same Physical Disks for Both
Redundant and Non-Redundant Virtual Disks
A Rebuild Does Not Work
A rebuild does not work in the following situations:
• The virtual disk is non-redundant —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:
– Pull out 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. For
more information on disk size requirements, see Considerations for Hot
Spares on PERC 5/E, PERC 5/i, PERC 6/E, PERC 6/I, and CERC 6/I
Controllers and Considerations for Hot Spares on S100, and S300
Controllers.
•
The hot spare has been unassigned from the virtual disk —This could
happen on some controllers if the hot spare was assigned to more than one
virtual disk and has already been used to rebuild a failed physical disk for
another virtual disk. For more information, see Considerations for Hot
Spares on S100, and S300 Controllers.
•
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. For more information, see
Set Rebuild Rate.
•
The rebuild was cancelled —Another user can cancel a rebuild that you
have initiated.