Users Guide
Resolving Microsoft Windows Upgrade Problems
If you upgrade the Microsoft Windows operating system on a server, you may nd that Storage Management no longer functions after the
upgrade. The installation process installs les and updates registry entries on the server that are specic 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 — Dierent controllers have dierent 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.
• The virtual disk includes failed or corrupt physical disks — This situation may generate alert 2083. For information on alert messages,
see the Server Administrator Messages Reference Guide.
• 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.
• The rebuild is canceled — Another user can cancel a rebuild that you have initiated.
A Rebuild Completes With Errors
A rebuild completes with errors 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 indicates successful completion while also
generating alert 2163. For information on alert messages, see the Server Administrator Messages Reference Guide.
138
Troubleshooting