Raid Array Remains Degraded After Hot Spares Rebuild; Servicing Controller Incorrectly Presented In The Svmc - HP storevirtual 3200 User Manual

Cause
The Windows host does not recover from the disconnection in time and loses all paths to the volume. Extend
the time that the host continues to retry the connection by modifying the LinkDownTime registry key, so that
it has enough time to recover the paths. LinkDownTime determines how long requests will be held in the
device queue and retried if the connection to the target is lost. The default value is 15 seconds.
Action
Procedure
1. Change the Windows Registry setting for the default LinkDownTime to 120 seconds
NOTE:
Back up your registry before changing it.
1. Run regedit.exe.
2. Navigate to HKLM\SYSTEM\CurrentControlSet\Control\Class\{4D36E97B-E325-11CE-
BFC1-08002BE10318}\<Instance Number>\Parameters.
3. Double-click LinkDownTime in the right-hand pane.
The Edit DWord Value window opens.
4. Enter a value of 120.
5. Click OK.
6. Save your changes and exit the Registry.
7. Reboot the system.

RAID array remains degraded after hot spares rebuild

Symptom
After a disk drive fails and the disk drive designated as the hot spare is rebuilt, RAID remains in a degraded
state.
Cause
The RAID configuration remains degraded until the failed drives are replaced and the new drives rebuild.
Action
Procedure
1. Replace the failed drives. After the new drives rebuild, the degraded state clears.

Servicing controller incorrectly presented in the SVMC

Symptom
A RAID device is owned by only one controller in the storage system. This servicing controller may be
incorrectly presented in the SVMC.
Cause
The misreporting of the servicing controller can happen if all three following conditions are met:
• RAID has been configured
• A management group has not been created yet
• One of the storage controllers fails
RAID array remains degraded after hot spares rebuild 89