Users Guide
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. This situation applies to PERC 3/SC, 3/DC, 3/QC, 4/SC, 4/DC, 4e/DC, 4/Di, and CERC ATA100/4ch
controllers.
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.
A Rebuild Completes with Errors
This section applies to PERC 3/SC, 3/DC, 3/QC, 4/SC, 4/DC, 4e/DC, 4/Di, 4e/Si, 4e/Di, and CERC ATA100/4ch
controllers
In some situations, a rebuild may complete successfully while also reporting errors. This may occur when a portion of the disk containing redundant (parity)
information is damaged. The rebuild process can restore data from the healthy portions of the disk but not from the damaged portion.
When a rebuild is able to restore all data except data from damaged portions of the disk, it will indicate successful completion while also generating alert
"2163." The rebuild may also report sense key errors. In this situation, take the following actions to restore the maximum data possible:
1. Back up the degraded virtual disk onto a fresh (unused) tape.
If the backup is successful. If the backup completes successfully then the user data on the virtual disk has not been damaged. In this case, you can
continue with "step2."
If the backup encounters errors. If the backup encounters errors then the user data has been damaged and cannot be recovered from the virtual disk.
In this case, the only possibility for recovery is to restore from a previous backup of the virtual disk.
2. Perform a "Check Consistency" on the virtual disk that you have backed up onto tape.
3. Restore the virtual disk from the tape onto healthy physical disks.
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