HP A3550A User Manual - A3661-90001 - Page 266

x06 - Unit Attention, 0x0B - Aborted Command

Page 266 highlights

Table 6-5 Sense Key, Additional Sense Code, and Additional Sense Code Qualifier Values (Not a Comprehensive List) (Continued) Sense key Description 05/25/01 05/26/02 05/27/00 This LUN is a global hot spare. This LUN cannot be accessed for data operations by the host. A parameter was set to an invalid value, for example, a nonchangeable field was changed on a Mode Select. The initiator (host) is attempting to download drive firmware without disabling the peer SP. 05/3A/00 The initiator (host) is performing a microcode download operation, but there are no disk drives to which the SP can appropriately install the microcode. 0x06 - Unit Attention 06/29/00 The LUN has been reset. This is reported after a power-up sequence completes or when a LUN is reset due to a SCSI Bus Reset, Bus Device Reset message or Trespass operation. The SP generates this key as part of a Unit Attention condition. 06/2F/00 A SCSI Clear Queue message has been received by this LUN from another initiator (host). This status indicates that all of the initiator's requests to this LUN have been aborted by the Clear Queue message. 06/80/01 The SCSI Reservation for this LUN has been changed by a Force Reserve operation. This Sense Key is reported to all initiators (hosts) other than the one that issued the Force Reserve command. 0x0B - Aborted Command 0B/00/00 The SP has aborted a command due to a condition in which the initiator (host) is encouraged to retry the command at a later time. 0B/00/06 The SP has aborted a command due to an unrecoverable error (includes retries exhausted) on the SCSI bus. 0B/2C/00 The initiator (host) has issued a nontagged CDB during a Contingent Allegiance that was not a Request Sense while TAGGED I/Os were present on the board for the I_T_L nexus. The SP considers this to be an invalid sequence of commands. The initiator is encouraged to reissue the command with a valid tag. 0B/43/00 The SP has aborted the command because a SCSI message the SP needed to complete the command was rejected by the initiator (host). 0B/47/00 The SP has aborted the command due to Parity Errors exhausting their retry count. 0B/48/00 The SP has received a SCSI Initiator Detected Error message. 6-18 Troubleshooting the Disk Array

  • 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

6-18
Troubleshooting the Disk Array
05/25/01
This LUN is a global hot spare. This LUN cannot be accessed for data
operations by the host.
05/26/02
A parameter was set to an invalid value, for example, a nonchangeable field was
changed on a Mode Select.
05/27/00
The initiator (host) is attempting to download drive firmware without disabling the
peer SP.
05/3A/00
The initiator (host) is performing a microcode download operation, but there are
no disk drives to which the SP can appropriately install the microcode.
0x06 - Unit Attention
06/29/00
The LUN has been reset. This is reported after a power-up sequence completes
or when a LUN is reset due to a SCSI Bus Reset, Bus Device Reset message or
Trespass operation. The SP generates this key as part of a Unit Attention
condition.
06/2F/00
A SCSI Clear Queue message has been received by this LUN from another
initiator (host). This status indicates that all of the initiator’s requests to this LUN
have been aborted by the Clear Queue message.
06/80/01
The SCSI Reservation for this LUN has been changed by a Force Reserve
operation. This Sense Key is reported to all initiators (hosts) other than the one
that issued the Force Reserve command.
0x0B - Aborted Command
0B/00/00
The SP has aborted a command due to a condition in which the initiator (host) is
encouraged to retry the command at a later time.
0B/00/06
The SP has aborted a command due to an unrecoverable error (includes retries
exhausted) on the SCSI bus.
0B/2C/00
The initiator (host) has issued a nontagged CDB during a Contingent Allegiance
that was
not
a Request Sense while TAGGED I/Os were present on the board
for the I_T_L nexus. The SP considers this to be an invalid sequence of
commands. The initiator is encouraged to reissue the command with a valid tag.
0B/43/00
The SP has aborted the command because a SCSI message the SP needed to
complete the command was rejected by the initiator (host).
0B/47/00
The SP has aborted the command due to Parity Errors exhausting their retry
count.
0B/48/00
The SP has received a SCSI Initiator Detected Error message.
Table 6-5
Sense Key, Additional Sense Code, and Additional Sense Code Qualifier Values
(Not a Comprehensive List) (Continued)
Sense key
Description