HP LeftHand SAN Solutions Support Document - Service Notes - VSA 7.0 for VMware ESX

15
Why RAID May Go Off If A Foreign Drive Is Inserted Prior To Powering Up
The Storage Module [NSM 260] (3341)
Scenario
If the storage module powers up with a drive that does not belong to the RAID
configuration, data corruption may occur causing RAID to go off and
preventing the storage module from coming online. Replacing the original
drive may not result in RAID going to normal.
Data may be lost on this storage module in this case.
Workaround
Never replace a drive when the storage module is off. Replace a drive while
the system is still operational and your are working from the Console.
“Contact support at www.hp.com/go/support to determine if data...” for this
storage module must be rebuilt or restored.
What To Do When A Cache Corruption Alert Is Received [NSM 260] (3321)
Scenario
Cache corruption can occur if the storage module is powered down while there
are data in the RAID cache. If the storage module stays powered-off long
enough (more than 72 hours), data in the cache will be corrupted. When the
storage module powers back up, the cache corruption is detected, and an alert
is posted indicating the cache is corrupt. The storage module will not be
allowed to come online in order to prevent corruption within the cluster. A
“storage module down” alert will also be posted. Please note that data on the
storage module has been lost in this case and must be rebuilt from the cluster,
assuming replication was configured.
Workaround
To resolve the issue, please “Contact support at www.hp.com/go/support".
Rebuilding RAID 5 Takes Too Long When Minimum Setting Is 1 [NSM
200] (2763)
The default setting for the minimum RAID rebuild rate is 1. This setting may
cause RAID 5 rebuild to take too long.