HP Surestore Disk Array FC60 HP SureStore E Disk Array FC60 Service Manual (A5 - Page 225

Discover new GHS drives, Back initiated

Page 225 highlights

Troubleshooting and the appropriate structures are created in memory. If these logical units had dirty data in cache, the controller will flush the data to the drive media. If the controller believes that it's Battery Backup Unit has failed, it will attempt to recover any mirrored data from the alternate controller. Hosts are now allowed access to these previouslyexisting logical units. Non-Inquiry commands will no longer fail with a Not Ready error. 16. The controller will attempt to spin up all remaining drives in the subsystem. If new drives are discovered, their configuration information is read, and any LUNs on these drives are brought on line. If the controller finds LUN information on these "new" drives for a LUN that already exists in the array subsystem, then the LUN number will be changed to the next available LUN number. Please refer to the LUN Migration document for additional information regarding moving drives. 17. Read array subsystem configuration: The controller will read the array subsystem configuration from the dacStore on the drives to confirm the correct mode of redundant controller operation. 18. Drive and controller hot-swap enable: The controller now initializes the firmware components to handle drive and controller hot-swaps. 19. Subsystem component polling: The controller now initializes subsystem component polling. 20. Restart interrupted drive re-constructions: The controller will restart any drive reconstruction processes that were interrupted due to power-fail or resets. With the current release of controller FW, the reconstruction process will be restarted from the beginning of the appropriate LUN. The controller has no knowledge of how much of the reconstruction process was completed, prior to the reset or power-fail. 21. Copy-Back initiated: If a Global Hot Spare (GHS) drive has been sparing for a Failed drive, and the originally Failed drive has been replaced, the controller will now initiate a copy-back from the GHS to the replaced drive. 22. Discover new GHS drives: If the controller discovers a new GHS has been inserted into the subsystem, it will start using the new GHS drive should a Failed drive be found. 23. Discover missing drives: The controller will display a list of drives that had LUN configuration on them but were cold-removed during the last power-down. Controller Enclosure Troubleshooting 225

  • 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
  • 373
  • 374
  • 375
  • 376
  • 377
  • 378
  • 379
  • 380
  • 381
  • 382
  • 383
  • 384
  • 385
  • 386
  • 387
  • 388
  • 389
  • 390
  • 391
  • 392
  • 393
  • 394
  • 395
  • 396
  • 397
  • 398
  • 399
  • 400
  • 401
  • 402
  • 403
  • 404
  • 405
  • 406
  • 407
  • 408
  • 409
  • 410
  • 411
  • 412
  • 413
  • 414
  • 415
  • 416

Controller Enclosure Troubleshooting
225
Troubleshooting
and the appropriate structures are created in memory. If these logical units had dirty
data in cache, the controller will flush the data to the drive media. If the controller
believes that it’s Battery Backup Unit has failed, it will attempt to recover any mirrored
data from the alternate controller. Hosts are now allowed access to these previously-
existing logical units.
Non-Inquiry commands will no longer fail with a Not Ready error.
16.
The controller will attempt to spin up all remaining drives in the subsystem
. If
new drives are discovered, their configuration information is read, and any LUNs on
these drives are brought on line. If the controller finds LUN information on these “new”
drives for a LUN that already exists in the array subsystem, then the LUN number will
be changed to the next available LUN number. Please refer to the LUN Migration
document for additional information regarding moving drives.
17.
Read array subsystem configuration:
The controller will read the array subsystem
configuration from the dacStore on the drives to confirm the correct mode of redundant
controller operation.
18.
Drive and controller hot
-
swap enable
: The controller now initializes the firmware
components to handle drive and controller hot-swaps.
19.
Subsystem component polling
: The controller now initializes subsystem component
polling.
20.
Restart interrupted drive re-constructions
: The controller will restart any drive re-
construction processes that were interrupted due to power-fail or resets. With the
current release of controller FW, the reconstruction process will be restarted from the
beginning of the appropriate LUN. The controller has no knowledge of how much of the
reconstruction process was completed, prior to the reset or power-fail.
21.
Copy
-
Back initiated:
If a Global Hot Spare (GHS) drive has been sparing for a Failed
drive, and the originally Failed drive has been replaced, the controller will now initiate
a copy-back from the GHS to the replaced drive.
22.
Discover new GHS drives:
If the controller discovers a new GHS has been inserted
into the subsystem, it will start using the new GHS drive should a Failed drive be found.
23.
Discover missing drives:
The controller will display a list of drives that had LUN
configuration on them but were cold-removed during the last power-down.