Troubleshooting using raid manager – HP XP P9500 Storage User Manual
Page 59
![background image](/manuals/398732/59/background.png)
Table 10 Troubleshooting suspended ESAM pairs (continued)
Corrective action
Description
Applies to
Suspend type
the failure is recovered, resynchronize the
pair from the MCU (Pairresync).
•
Because of the quorum disk failure, the
multipath software will show that the S-VOL
is offline. Resynchronize the pair as
described above, and then make the path
to the S-VOL online with the multipath
software.
Resynchronize the pair. This results in an
initial copy operation.
The primary system could not find
valid control information in its
P-VOL
S-VOL
PSUE,
MCU IMPL
nonvolatile memory during IMPL. This
condition only occurs if the primary
system is without power for more than
48 hours (i.e., power failure and fully
discharged backup batteries).
Release the pair from the primary system.
Clear all error conditions at the primary
The pair was suspended before the
initial copy completed. Data on the
P-VOL
S-VOL
PSUE,
Initial Copy
Failed
system, P-VOL, secondary system, and S-VOL.
Restart the initial copy operation.
S-VOL is not identical to data on the
P-VOL.
Troubleshooting using RAID Manager
When an error occurs in pair operations using RAID Manager, you can identify the cause of the
error by referring to the RAID Manager operation log file. This file is stored in the following directory
by default:
/HORCM/log*/curlog/horcmlog_HOST/horcm.log
Where:
*
is the instance number.
HOST
is the host name.
Example:
Error codes appear on the right of the equal symbol (=).
RAID Manager error codes for Continuous Access Synchronous are provided in the following table.
If you receive error codes that are not described here, see HP P9000 Continuous Access
Synchronous User Guide.
Description
Error code
(SSB2)
Error code
(SSB1)
One of the following causes apply:
CBEF
B90A
•
An ESAM pair cannot be created because Continuous Access Synchronous
or ESAM is not installed.
•
An ESAM pair cannot be created or resynchronized because of one of the
following causes:
- The specified quorum disk ID is not added to secondary system.
- The specified quorum disk ID does not match the quorum disk ID that the
S-VOL uses.
Troubleshooting using RAID Manager
59