IBM 86655RY Hardware Maintenance Manual - Page 199

Recovery from ServeRAID controller failure, Recovery procedures, CTRL+I, Advanced Functions

Page 199 highlights

• SID 1: HSP • SID 2: ONL • SID 3: ONL • SID 4: ONL The format is as follows: date time error type: Ax Cx Bxx message The x following A is the controller number; the x following C is the channel, and the xx following B is the SID number. An error type can be either informational or critical. The message gives a brief description of the RAID event that has occurred. The first two lines of the ServeRAID log show that a synchronization was started and proceeded to complete successfully. At a later point in time, on line 3 of the ServeRAID log, a dead drive is detected on controller 1, channel 3, SID 3. In this case, since an HSP drive is defined, the rebuild starts automatically. Both the start and finish of the rebuild is logged by the controller. Later on, the drive in SID 4 is marked dead, but no rebuild is started because the HSP drive has already been used. In the current ServeRAID log, the drive in SID 4 is the "inconsistent" drive, and must be physically replaced. If this is the case, you should mark other drives ONL and then rebuild drive SID 4. Note: If the drive containing the operating system is not accessible see "Using ServeRAID Manager to determine the correct order to software replace" on page 187. Before you perform any actions on the hardware, make a photocopy of the Channel Record table, Table 22 on page 191. Use Netfinity Manager or ServeRAID monitor to fill in the copy of the Channel Record table at the end of this manual with the current status of all the drives, both internal and external. This table provides a four-channel diagram to accommodate all types of ServeRAID controllers. For the ServeRAID controllers, if power is lost or another drive is marked Defunct (DDD) during a rebuild operation, the rebuild fails and the drive being rebuilt remains in the Rebuild (RBL) state. Consequently, the "inconsistent" drive remains recognizable. Recovery from ServeRAID controller failure When a ServeRAID controller fails, you must replace the ServeRAID controller and then restore the ServeRAID configuration to the new ServeRAID controller. To restore the ServeRAID configuration: 1. Press CTRL+I during POST to enter the Mini-Configuration. 2. Select Advanced Functions. 3. Select Copy Configuration from Drives to Controller. Recovery procedures This section describes the recovery procedures for the following conditions: • "Recovery procedures for one defunct drive" on page 190 • "More than one defunct (DDD) drive, all logical drives in critical or OK state" on page 190 • "More than one defunct (DDD) drive and one or more arrays offline" on page 190 Installing and configuring ServeRAID controllers 189

  • 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

Installing and configuring ServeRAID controllers
189
SID 1: HSP
SID 2: ONL
SID 3: ONL
SID 4: ONL
The format is as follows:
date time error type: A
x
C
x
B
xx
message
The
x
following A is the controller number; the
x
following C is the channel, and the
xx
following B is the SID number. An error type can be either
informational
or
critical
.
The message gives a brief description of the RAID event that has occurred.
The first two lines of the ServeRAID log show that a synchronization was started and
proceeded to complete successfully. At a later point in time, on line 3 of the
ServeRAID log, a dead drive is detected on controller 1, channel 3, SID 3. In this case,
since an HSP drive is defined, the rebuild starts automatically. Both the start and
finish of the rebuild is logged by the controller. Later on, the drive in SID 4 is marked
dead, but no rebuild is started because the HSP drive has already been used.
In the current ServeRAID log, the drive in SID 4 is the
inconsistent
drive, and must
be physically replaced. If this is the case, you should mark other drives ONL and then
rebuild drive SID 4.
Note:
If the drive containing the operating system is not accessible see
Using
ServeRAID Manager to determine the correct order to software replace
on
page 187.
Before you perform any actions on the hardware, make a photocopy of the Channel
Record table, Table 22 on page 191.
Use
Netfinity Manager or ServeRAID monitor to
fill in the copy of the Channel Record table at the end of this manual with the current
status of all the drives, both internal and external. This table provides a four-channel
diagram to accommodate all types of ServeRAID controllers.
For the ServeRAID controllers, if power is lost or another drive is marked Defunct
(DDD) during a rebuild operation, the rebuild fails and the drive being rebuilt
remains in the Rebuild (RBL) state. Consequently, the
inconsistent
drive remains
recognizable.
Recovery from ServeRAID controller failure
When a ServeRAID controller fails, you must replace the ServeRAID controller and
then restore the ServeRAID configuration to the new ServeRAID controller. To restore
the ServeRAID configuration:
1.
Press
CTRL+I
during POST to enter the Mini-Configuration.
2.
Select
Advanced Functions
.
3.
Select
Copy Configuration from Drives to Controller
.
Recovery procedures
This section describes the recovery procedures for the following conditions:
Recovery procedures for one defunct drive
on page 190
More than one defunct (DDD) drive, all logical drives in critical or OK state
on
page 190
More than one defunct (DDD) drive and one or more arrays offline
on page 190