User's Manual
The following sections describe troubleshooting procedures for virtual disks.
l "Replacing a Failed Disk that is Part of a Redundant Virtual Disk"
l "A Rebuild Does Not Work"
l "Cannot Create a Virtual Disk"
l "Cannot Create a Virtual Disk"
l "Virtual Disk Errors on Linux"
l "Problems Associated With Using the Same Physical Disks for Both Redundant and Nonredundant Virtual Disks"
A Rebuild Does Not Work
A rebuild will not work in the following situations:
l The virtual disk is nonredundant. For example, a RAID 0 virtual disk cannot be rebuilt because RAID 0 does not provide data redundancy.
l There is no hot spare assigned to the virtual disk. As long as the virtual disk is redundant, you can do the following to rebuild it:
¡ Pull out the failed physical disk and replace it. A rebuild will automatically start on the new disk.
¡ Assign a hot spare to the virtual disk and then perform a rebuild.
l You are attempting to rebuild onto a hot spare that is too small. Different controllers have different size requirements for hot spares. See
"Considerations for Hot Spares on PERC 5/E, PERC 5/i, PERC 6/E, PERC 6/I, and CERC 6/I Controllers" for more information on disk size requirements.
l 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.
l A physical disk has been removed, and the system has not yet attempted to write data to the removed disk. In this case, the system will not recognize
the removal of a physical disk until it attempts a write operation to the disk. If the physical disk is part of a redundant virtual disk, then the system will
rebuild the disk after attempting a write operation.
l The virtual disk includes failed or corrupt physical disks. This situation may generate alert "2083." See alert "2083" for more information.
l 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. See "Set Rebuild Rate" for more information.
l The rebuild was cancelled. Another user can cancel a rebuild that you have initiated.
Cannot Create a Virtual Disk
You might be attempting a RAID configuration that is not supported by the controller. Check the following:
l How many virtual disks already exist on the controller? Each controller supports a maximum number of virtual disks. See "Maximum Number of Virtual
Disks per Controller" for more information.
l Is there adequate available space on the disk? The physical disks that you have selected for creating the virtual disk must have an adequate amount of
free space available.
l The controller may be performing other tasks, such rebuilding a physical disk, that must run to completion before the controller can create the new
virtual disk.
A Virtual Disk of Minimum Size is Not Visible to Windows Disk Management
If you create a virtual disk using the minimum allowable size in Storage Management, the virtual disk may not be visible to Windows Disk Management even
after initialization. This occurs because Windows Disk Management is only able to recognize extremely small virtual disks if they are dynamic. It is generally
advisable to create virtual disks of larger size when using Storage Management.
Virtual Disk Errors on Linux
On some versions of the Linux operating system, the virtual disk size is limited to 1TB. If you create a virtual disk that exceeds the 1TB limitation, your system
may experience the following behavior:
l I/O errors to the virtual disk or logical drive
l Inaccessible virtual disk or logical drive
l Virtual disk or logical drive size is smaller than expected