Users Guide

Table Of Contents
Table 33. Possible scenarios for reconfiguring a virtual disk (continued)
Controller Starting RAID Level Target RAID Level Comments
RAID 6 RAID 6 Add at least one additional
disk
RAID 10 RAID 10 Without adding additional
disks
PERC S100, S110, S130, S140,
S300, and S150
RAID 0 RAID 0 With or without additional
disks
RAID 1 RAID 1 Without additional disks
RAID 5 RAID 5 With or without additional
disks
RAID 10 RAID 10 Without additional disks
NOTE: The order of the controllers displayed on Storage Management may differ with the order of the controllers displayed
in the Human Interface (HII) and PERC Option ROM. The order of the controllers does not cause any limitation.
NOTE: When creating virtual disks using software RAID controllers, the information related to the physical disks linked
to the virtual disk is enumerated or displayed on Storage Management after a short delay. This delay in displaying the
information does not cause any functional limitation. If you are creating partial virtual disks, it is recommended that you
provide Storage Management adequate time between each partial virtual disk creation process.
NOTE: RAID 10 virtual disk reconfiguration operation is not supported with Intelligent Mirroring.
Maintaining The Integrity Of Redundant Virtual Disks
Does my controller support this feature? See Supported Features.
The virtual disk Check Consistency task verifies the accuracy of the redundant (parity) information. This task only applies to
redundant virtual disks. When necessary, the Check Consistency task rebuilds the redundant data.
To verify redundant information of a virtual disk:
1. Locate the controller on which the virtual disk resides in the tree view. Expand the controller object until the Virtual Disks
object is displayed.
2. Select the Check Consistency task from the virtual disks Tasks drop-down list box and click Execute.
Rebuilding Redundant Information
Does my controller support this feature? See Supported Features.
If you have a redundant virtual disk, you can reconstruct the contents of a failed physical disk onto a new disk or a hot spare. A
rebuild can take place during normal operation, but it degrades performance.
A global hot spare drive can be part of different RAID level Virtual drives rebuilding operation on SWRAID controllers.
Managing Virtual Disk Bad Block Management
Virtual disk bad blocks are bad blocks on one or more member physical disks. The read operation on the virtual disks having bad
blocks may fail.
Storage Management generates a critical alert (2387) to notify you of the bad blocks on the virtual disk.
Virtual disk bad blocks are discovered when the controller performs any operation that requires scanning the disk. Examples of
operations that may result in this alert are:
Consistency check
Rebuild
122
Virtual Disks