Software Support

Setting The Physical Disk Online Or Offline
Recovering From Removing The Wrong Physical Disk
If the physical disk that you mistakenly removed is part of a redundant virtual disk that also has a hot spare, then the
virtual disk rebuilds automatically either immediately or when a write request is made. After the rebuild has completed,
the virtual disk no longer has a hot spare since data has been rebuilt onto the disk previously assigned as a hot spare. In
this case, assign a new hot spare.
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 perform a rebuild task.
For information on rebuilding physical disks and assigning hot spares, see Understanding Hot Spares.
You can avoid removing the wrong physical disk by blinking the LED display on the physical disk that you intend to
remove. For information on blinking the LED display, see Blinking And Unblinking A Physical Disk.
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 updates registry entries on the server that are
specific to the operating system. Changing the operating system can disable Storage Management.
To avoid this problem, you should uninstall Storage Management before upgrading.
After you have uninstalled Storage Management and completed the upgrade, reinstall Storage Management using the
Storage Management install media.
Virtual Disk Troubleshooting
The following sections describe troubleshooting procedures for virtual disks:
• Replacing A Failed Disk That Is Part Of A Redundant Virtual Disk
• A Rebuild Does Not Work
• A Rebuild Completes With Errors
• Cannot Create A Virtual Disk
• Virtual Disk Errors On Systems Running 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 nonredundant — 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:
– Remove 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.
• The hot spare has been unassigned from the virtual disk — This occurs on some controllers if the hot spare is
assigned to more than one virtual disk and is being used to rebuild a failed physical disk for another virtual disk.
178