HP Surestore E Disk Array XP256 HP XP P9000 External Storage Access Manager Us - Page 73

Troubleshooting suspended pairs when using RAID Manager

Page 73 highlights

Suspend type VOL Type PSUE, P-VOL S-VOL Failure S-VOL PSUE, MCU IMPL P-VOL S-VOL PSUE, Initial Copy Failed P-VOL S-VOL Error Corrective action 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. The settings for host mode option 52 differ between ports on the primary and secondary storage systems. Do one of the following: • If you do not use cluster systems, disable host mode option 52. • If you use cluster systems, enable host mode option 52 for host groups where an executing node and a standby node belong. The primary storage system could not Resynchronize the pair. This results in an find valid control information in its initial copy operation. nonvolatile memory during IMPL. This condition only occurs if the primary storage system is without power for more than 48 hours (for example, a power failure and fully discharged backup batteries). The pair was suspended before the initial copy completed. Data on the S-VOL is not identical to data on the P-VOL. Do the following: • Release the pair from the primary storage system. • Clear all error conditions at the primary storage system, P-VOL, secondary storage system, and S-VOL. • Restart the initial copy operation. Troubleshooting suspended pairs when using RAID Manager The basic steps involved in resolving suspended volume pairs when using RAID Manager include: • Using the RAID Manager operation log file to identify the cause of the error. • Following the troubleshooting steps based on the SSB1 and SSB2 error codes (the codes are recorded in the log file). Location of the RAID Manager operation log file The 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. Error codes appear on the right of the equal symbol (=). Example log file Two error codes are included in this example (B9E1 and B901). Suspended volume pair troubleshooting 73

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95

Corrective action
Error
VOL Type
Suspend type
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.
Do one of the following:
The settings for host mode option 52
differ between ports on the primary
and secondary storage systems.
P-VOL
S-VOL
PSUE,
S-VOL Failure
If you do not use cluster systems, disable
host mode option 52.
If you use cluster systems, enable host
mode option 52 for host groups where an
executing node and a standby node
belong.
Resynchronize the pair. This results in an
initial copy operation.
The primary storage 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
storage system is without power for
more than 48 hours (for example, a
power failure and fully discharged
backup batteries).
Do the following:
Release the pair from the primary storage
system.
Clear all error conditions at the primary
storage system, P-VOL, secondary storage
system, and S-VOL.
Restart the initial copy operation.
The pair was suspended before the
initial copy completed. Data on the
S-VOL is not identical to data on the
P-VOL.
P-VOL
S-VOL
PSUE,
Initial Copy
Failed
Troubleshooting suspended pairs when using RAID Manager
The basic steps involved in resolving suspended volume pairs when using RAID Manager include:
Using the RAID Manager operation log file to identify the cause of the error.
Following the troubleshooting steps based on the SSB1 and SSB2 error codes (the codes are
recorded in the log file).
Location of the RAID Manager operation log file
The 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.
Error codes appear on the right of the equal symbol (=).
Example log file
Two error codes are included in this example (B9E1 and B901).
Suspended volume pair troubleshooting
73