R/Evolution 2000 Series, Troubleshooting Manual

Page: 43 / 130

Chapter 4 Troubleshooting Using RAIDar 43
Reviewing the Event Logs
If all the steps in “Identifying a Faulty Disk Drive” on page 40 and “Reviewing
Disk Drive Error Statistics” on page 41 have been performed, you have determined
the following:
■
A disk drive has encountered a fault
■
The location of the disk drive
■
What the fault is
The next step is to review the event logs to determine if there were any events that
led to the fault. If you skip this step, you could replace the faulty drive and then
encounter another fault.
To view the event logs from any page, click the icon in the System Panel.
See “Troubleshooting Using Event Logs” on page 65 for more information about
using event logs.
Reconstructing a Virtual Disk
If one or more drives fail in a redundant virtual disk (RAID 1, 3, 5, 6, 10, or 50) and
properly sized spares are available, the storage system automatically uses the spares
to reconstruct the virtual disk. Virtual disk reconstruction does not require I/O to be
quiesced, so the virtual disk can continue to be used while the Reconstruct utility
runs.
A properly sized spare is one whose capacity is equal to or greater than the smallest
drive in the virtual disk. If no properly sized spares are available, reconstruction
does not start automatically. To start reconstruction manually, replace each failed
drive and then do one of the following:
■
Add each new drive as a vdisk spare (Manage > Virtual Disk Config > Vdisk
Configuration > Add Vdisk Spares) or a global spare (Manage > Virtual Disk
Config > Global Spare Menu > Add Global Spares). Remember that a global
spare might be taken by a different critical virtual disk than the one you intended.
■
Enable the Dynamic Spare Configuration option on the Manage > General Config
> System Configuration page to use the new drives without designating them as
spares.
Reconstructing a RAID-6 virtual disk to a fault-tolerant state requires two properly
sized spares to be available.