IBM 86655RY Hardware Maintenance Manual - Page 197

Automatically rebuilding the defunct drive, Software and physical replacement

Page 197 highlights

Automatically rebuilding the defunct drive The ServeRAID controller will rebuild a defunct drive automatically when all of the following conditions exist: • The physical drive that failed is part of a redundant RAID logical drive. See "Reference information" on page 192 for more information on data redundancy. • A hot-spare or standby hot-spare drive with a capacity equal to or greater than the capacity of the defunct drive is available the moment the drive fails. - When multiple hot-spare drives are available, the ServeRAID controller searches for a hot-spare drive of the appropriate size. The smallest drive that meets this requirement enters the Rebuild state. - If no hot-spare or standby hot-spare drives are available, the rebuild operation will start the moment you replace the defective drive. Note: If you physically replace the drive and the new drive does not appear in the Physical Drives branch of the Main Tree, you must scan for new or removed Ready drives. • No rebuild, synchronization, logical-drive migration, or RAID level-5E compression/decompression operation is in process. Software and physical replacement When the ServeRAID controller communicates with the hard disk drive and receives an unexpected response, the controller will mark the drive defunct in order to avoid any potential data loss. For example, this could occur in the event of a power loss to any of the components in the SCSI ServeRAID subsystem. In this case, the ServeRAID controller will err on the side of safety and will no longer write to that drive, although the drive may not be defective in any way. It is recommended to use a software replace to recover data when multiple Defunct (DDD) drives occur. In this situation, you may lose data on drives that are not actually defective if you run a normal rebuild process. Perform a software replace or a physical replace according to the following criteria: • A software replace is recommended when trying to recover data when multiple Defunct (DDD) drives occur. Warning: If you use the wrong order when you attempt a software replace, your data will be corrupted. • Do not perform a software replace for a single Defunct (DDD) drive. All single defunct drives should be physically replaced. • Replace the Defunct (DHS) drive physically if a Defunct (DDD) drive has been replaced by an HSP. The drive must be replaced physically to ensure that a good HSP drive is present in the system. Using ServeRAID Manager to determine the correct order to software replace The following lists describe the correct order to software replace under two conditions: operating system is accessible and operating system is not accessible. When the operating system is accessible, to determine the correct order to software replace follow the following steps: 1. Using ServeRAID Manager, note the hard disk drive(s) that are defunct. Installing and configuring ServeRAID controllers 187

  • 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
187
Automatically rebuilding the defunct drive
The ServeRAID controller will rebuild a defunct drive automatically when all of the
following conditions exist:
The physical drive that failed is part of a redundant RAID logical drive. See
Reference information
on page 192 for more information on data redundancy.
A hot-spare or standby hot-spare drive with a capacity equal to or greater than
the capacity of the defunct drive is available the moment the drive fails.
When multiple hot-spare drives are available, the ServeRAID controller
searches for a hot-spare drive of the appropriate size. The smallest drive that
meets this requirement enters the Rebuild state.
If no hot-spare or standby hot-spare drives are available, the rebuild
operation will start the moment you replace the defective drive.
Note:
If you physically replace the drive and the new drive does not appear
in the Physical Drives branch of the Main Tree, you must scan for new
or removed Ready drives.
No rebuild, synchronization, logical-drive migration, or RAID level-5E
compression/decompression operation is in process.
Software and physical replacement
When the ServeRAID controller communicates with the hard disk drive and receives
an unexpected response, the controller will mark the drive defunct in order to avoid
any potential data loss. For example, this could occur in the event of a power loss to
any of the components in the SCSI ServeRAID subsystem. In this case, the ServeRAID
controller will err on the side of safety and will no longer write to that drive, although
the drive may not be defective in any way.
It is recommended to use a software replace to recover data when multiple Defunct
(DDD) drives occur. In this situation, you may lose data on drives that are not actually
defective if you run a normal rebuild process.
Perform a software replace or a physical replace according to the following criteria:
A software replace is recommended when trying to recover data when multiple
Defunct (DDD) drives occur.
Warning:
If you use the wrong order when you attempt a software replace,
your data will be corrupted.
Do not perform a software replace for a single Defunct (DDD) drive. All single
defunct drives should be physically replaced.
Replace the Defunct (DHS) drive physically if a Defunct (DDD) drive has been
replaced by an HSP. The drive must be replaced physically to ensure that a good
HSP drive is present in the system.
Using ServeRAID Manager to determine the correct
order to software replace
The following lists describe the correct order to software replace under two
conditions: operating system is accessible and operating system is not accessible.
When the operating system is accessible, to determine the correct order to software
replace follow the following steps:
1.
Using ServeRAID Manager, note the hard disk drive(s) that are defunct.