Users Guide
If the physical disk that you removed is part of a redundant virtual disk that does not have a hot spare, then replace the physical disk and do a rebuild.
See the following sections for information on rebuilding physical disks and assigning hot spares:
l "Understanding Hot Spares" for RAID controllers
l "Rebuild" for PERC 3/SC, 3/DC, 3/QC, 4/SC, 4/DC, 4e/DC, 4/Di, CERC ATA100/4ch, PERC 5/E and PERC 5/i controllers
You can avoid removing the wrong physical disk by blinking the LED display on the physical disk that you intend to remove. See "Blink and Unblink (Physical
Disk)" for information on blinking the LED display.
Resolving Microsoft®Windows®Upgrade Problems
If you upgrade the Microsoft Windows operating system on a server, you may find that Storage Management no longer functions after the upgrade. The
installation process installs files and makes registry entries on the server that are specific to the operating system. For this reason, changing the operating
system can disable Storage Management.
To avoid this problem, you should uninstall Storage Management before upgrading. If you have already upgraded without uninstalling Storage Management,
however, you should uninstall Storage Management after the upgrade.
After you have uninstalled Storage Management and completed the upgrade, reinstall Storage Management using the Storage Management install media. You
can download Storage Management from the Dell Support website support.dell.com.
Virtual Disk Troubleshooting
The following sections describe troubleshooting procedures for virtual disks.
l "Replacing a Failed Disk that is Part of a Redundant Virtual Disk"
l "Replacing a Failed Physical Disk in a RAID 1 on a CERC SATA1.5/2s"
l "A Rebuild Does Not Work"
l "A Rebuild Completes with Errors"
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 3/SC, 3/DC, 3/QC, 4/SC, 4/DC, 4e/DC, 4/Di, 4e/Si, 4e/Di, CERC ATA100/4ch, PERC 5/E, PERC 5/i, PERC 6/E, PERC
6/I, and CERC 6/I Controllers" and "Considerations for Hot Spares on PERC 3/Si, 3/Di, and CERC SATA1.5/6ch 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. See "Considerations for Hot Spares on PERC 3/Si, 3/Di, and
CERC SATA1.5/6ch Controllers" for a description of this situation.
l On SCSI controllers, both redundant and nonredundant virtual disks reside on the same set of physical disks. On the PERC 3/SC, 3/DC, 3/QC, 4/SC,
4/DC, 4e/DC, 4/Di, and CERC ATA100/4ch controllers, a rebuild is not performed for a physical disk that is used by both redundant and nonredundant
virtual disks. In order to rebuild the redundant virtual disk, you need to delete the nonredundant virtual disk. Before deleting this disk, however, you can
attempt to recover data from the failed physical disk by forcing it back online. See "Using the Physical Disk Online Command on Select Controllers" for
more information.