HP A3550A User Manual - A3661-90001 - Page 265

Raid-1, Raid-1/0, Raid-3, Or Raid-5 Lun. - manual

Page 265 highlights

Troubleshooting Table 6-5 Sense Key, Additional Sense Code, and Additional Sense Code Qualifier Values (Not a Comprehensive List) (Continued) Sense key Description 0x02 - Not Ready 02/04/00 Logical unit not ready. Cause not reportable. 02/04/01 The LUN is reporting that it is becoming ready (performing an Assign). The initiator (host) should retry after a short time interval (such as 500ms). 02/04/02 Logical unit not ready. Initializing command required. 02/04/03 The LUN reporting this sense data is indicating it is inoperable and manual intervention may be necessary. 0x03 - Media Error 03/11/04 Data cannot be returned for a read operation because of an unrecoverable media error on the LUN in question 03/11/0B A Verify operation failed because of an unrecoverable media error on the LUN in question. 0x04 - Hardware Error 04/00/00 The command could not be completed by the SP because an unrecoverable error was detected. This can be caused by multiple disk failures in a redundant (RAID-1, RAID-1/0, RAID-3, or RAID-5) LUN. 04/05/00 Same definition as 04/00/00. This status is used in place of 04/00/00 for some disk array system types. 04/3A/00 An SP microcode update was attempted, but fewer than two database (microcode-storing) disks were in the cabinet at the time. Two disks are required so that the new microcode does not overwrite all copies of the current version, in case the new microcode does not load correctly. If the new code does not load correctly, the SP will reload the old microcode. 04/44/00 A firmware update failed on one of the disk modules. 0x05 - Illegal Request 05/04/00 The LUN specified in the Identify message accompanying the command descriptor block (CDB) is not assigned to this SP. The initiator (host) can assume that the Auto-Assign attempt failed. 05/1A/00 The length of a parameter (Mode Select page, for example) is incorrect. 05/20/00 The opcode field in the CDB is invalid. 05/21/00 The Logical Block Address specified in the CDB is out of range. 05/24/00 A field in the CDB is invalid. 05/25/00 The LUN specified in the Identify message accompanying the CDB does not exist in the array configuration. Troubleshooting the Disk Array 6-17

  • 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
  • 277
  • 278
  • 279
  • 280
  • 281
  • 282
  • 283
  • 284
  • 285
  • 286
  • 287
  • 288
  • 289
  • 290
  • 291
  • 292
  • 293
  • 294
  • 295
  • 296
  • 297
  • 298
  • 299
  • 300
  • 301
  • 302
  • 303
  • 304
  • 305
  • 306
  • 307
  • 308
  • 309
  • 310
  • 311
  • 312
  • 313
  • 314
  • 315
  • 316
  • 317
  • 318
  • 319
  • 320
  • 321
  • 322
  • 323
  • 324
  • 325
  • 326
  • 327
  • 328
  • 329
  • 330
  • 331
  • 332
  • 333
  • 334
  • 335
  • 336
  • 337
  • 338
  • 339
  • 340
  • 341
  • 342
  • 343
  • 344
  • 345
  • 346
  • 347
  • 348
  • 349
  • 350
  • 351
  • 352
  • 353
  • 354
  • 355
  • 356
  • 357
  • 358
  • 359
  • 360
  • 361
  • 362
  • 363
  • 364
  • 365
  • 366
  • 367
  • 368
  • 369
  • 370
  • 371
  • 372

Troubleshooting the Disk Array
6-17
Troubleshooting
0x02 - Not Ready
02/04/00
Logical unit not ready. Cause not reportable.
02/04/01
The LUN is reporting that it is becoming ready (performing an Assign). The
initiator (host) should retry after a short time interval (such as 500ms).
02/04/02
Logical unit not ready. Initializing command required.
02/04/03
The LUN reporting this sense data is indicating it is inoperable and manual
intervention may be necessary.
0x03 - Media Error
03/11/04
Data cannot be returned for a read operation because of an unrecoverable
media error on the LUN in question
03/11/0B
A Verify operation failed because of an unrecoverable media error on the LUN in
question.
0x04 - Hardware Error
04/00/00
The command could not be completed by the SP because an unrecoverable
error was detected. This can be caused by multiple disk failures in a redundant
(RAID-1, RAID-1/0, RAID-3, or RAID-5) LUN.
04/05/00
Same definition as 04/00/00. This status is used in place of 04/00/00 for some
disk array system types.
04/3A/00
An SP microcode update was attempted, but fewer than two database
(microcode-storing) disks were in the cabinet at the time. Two disks are required
so that the new microcode does not overwrite all copies of the current version, in
case the new microcode does not load correctly. If the new code does not load
correctly, the SP will reload the old microcode.
04/44/00
A firmware update failed on one of the disk modules.
0x05 - Illegal Request
05/04/00
The LUN specified in the Identify message accompanying the command
descriptor block (CDB) is not assigned to this SP. The initiator (host) can
assume that the Auto-Assign attempt failed.
05/1A/00
The length of a parameter (Mode Select page, for example) is incorrect.
05/20/00
The opcode field in the CDB is invalid.
05/21/00
The Logical Block Address specified in the CDB is out of range.
05/24/00
A field in the CDB is invalid.
05/25/00
The LUN specified in the Identify message accompanying the CDB does not
exist in the array configuration.
Table 6-5
Sense Key, Additional Sense Code, and Additional Sense Code Qualifier Values
(Not a Comprehensive List) (Continued)
Sense key
Description