HP Surestore Disk Array FC60 HP SureStore E Disk Array 12H User's and Service - Page 161

Duplicate Disk, Drive Identifier

Page 161 highlights

Troubleshooting Troubleshooting Event Code Descriptions Event Number (DEC/hex) Event Name Event Predictive Suspected Logged Maintenance Components Implication Description 143/0x8f Duplicate Disk Drive Identifier Y Single Controller Occurrence Erroneous Operator Activity As part of its stamp, each drive indicates its logical position in the disk set to which it is attached. This event indicates that the controller has detected two disk drives with identical stamps, indicating that they occupy the same logical position of the same disk set. The most likely source of this error is the erroneous assignment of duplicate disk set ID's by the controller. This would generally originate with incorrect controller serial number assignment, and/or loss of NVRAM. This error would also occur if a user made an image copy of a drive. The solution to this difficult problem involves two steps: 1. Try to determine which of the disk drives share the conflicting stamp. This can be done by removing disk drives until the problem disappears. Concentrate on any previously used or unincluded disks first. 2. When you have isolated the two conflicting disks, determine which one contains valid data. 161

  • 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
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276

Troubleshooting
Event Code Descriptions
161
Troubleshooting
Event
Number
(DEC/hex)
Event Name
Event
Logged
Predictive
Maintenance
Implication
Suspected
Components
Description
143/0x8f
Duplicate Disk
Drive Identifier
Y
Single
Occurrence
Controller
Erroneous
Operator
Activity
As part of its stamp, each
drive indicates its logical
position in the disk set to
which it is attached. This
event indicates that the
controller has detected two
disk drives with identical
stamps, indicating that they
occupy the same logical
position of the same disk set.
The most likely source of this
error is the erroneous
assignment of duplicate disk
set ID’s by the controller. This
would generally originate with
incorrect controller serial
number assignment, and/or
loss of NVRAM. This error
would also occur if a user
made an image copy of a
drive.
The solution to this difficult
problem involves two steps:
1.
Try to determine which
of the disk drives share
the conflicting stamp.
This can be done by
removing disk drives
until the problem
disappears. Concentrate
on any previously used or
unincluded disks first.
2.
When you have isolated
the two conflicting disks,
determine which one
contains valid data.