IBM 86655RY Hardware Maintenance Manual - Page 219

After creating an array, the user must create a logical drive.

Page 219 highlights

combining Record 1 with the check sum data on Drive 3. At this point, the media sector error is discovered. • If the error is minor, the disk can re-create the missing information from its ECC data (as before) and potentially remap the bad sector. • If the error is too severe, the disk cannot recover the data. The rebuild process cannot complete successfully because it does not have a complete Record 1 to combine with the check sum data to rebuild the lost data on Drive 2. The Rebuild, therefore, skips that stripe and continues rebuilding the rest of the logical drive. Once the rebuild has completed, a "rebuild failed" message is displayed. The ServeRAID controller brings the rebuilt drive online and takes the array out of "critical" mode. To protect data integrity, it also blocks access to the damaged stripes of the array. Data files covered by these damaged stripes still report data errors and must be restored from a previous backup. The necessity for a full restore due to a "rebuild failed" message caused by one or two bad stripes is thereby prevented. Configuration procedures required to provide RAID-5 protection: Synchronization and initialization are required before installing an operating system or storing any customer data on a RAID-5 array for data integrity and to provide data protection. The RAID-5 arrays write data out to drives in stripe units. The size of the stripe unit can be configured to: • 8KB • 16KB • 32KB • 64KB Synchronization performs the following operations: • Reads all the data bits in each stripe unit • Calculates the parity for that data • Compares the calculated parity with the existing parity for all stripe units in the array • Updates the existing parity, if inconsistent Initialization writes zeroes out to the logical drive. Operating systems may not install properly if the first few sectors are not set to zero (approximately the first 32 sectors). After creating an array, the user must create a logical drive. Physical drives are the individual disk drives that are inside the machine. A logical drive is the drive that the array controller shows the operating system. A logical drive spans across multiple physical drives. All redundant RAID logical drives are automatically synchronized by the ServeRAID4 controller in the background when the logical drive is defined. No other user action is required. Providing additional protection for redundant RAID logical drives: Full tape backups and automatic data scrubbing provide protection against multiple drive failure and unprotected grown media defects. Full tape backups: Periodic full tape backups force all data files to be read and copied to tape. This procedure provides two advantages: • It provides an archive of all data in case it is needed to restore from a multiple drive failure or user error that could cause data loss/corruption. Installing and configuring ServeRAID controllers 209

  • 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
209
combining Record 1 with the check sum data on Drive 3. At this point, the media
sector error is discovered.
If the error is minor, the disk can re-create the missing information from its ECC
data (as before) and potentially remap the bad sector.
If the error is too severe, the disk cannot recover the data. The rebuild process
cannot complete successfully because it does not have a complete Record 1 to
combine with the check sum data to rebuild the lost data on Drive 2. The Rebuild,
therefore, skips that stripe and continues rebuilding the rest of the logical drive.
Once the rebuild has completed, a
rebuild failed
message is displayed.
The ServeRAID controller brings the rebuilt drive online and takes the array out of
critical
mode. To protect data integrity, it also blocks access to the damaged stripes
of the array. Data files covered by these damaged stripes still report data errors and
must be restored from a previous backup. The necessity for a full restore due to a
rebuild failed
message caused by one or two bad stripes is thereby prevented.
Configuration procedures required to provide RAID-5 protection:
Synchronization and
initialization are required before installing an operating system or storing any
customer data on a RAID-5 array for data integrity and to provide data protection.
The RAID-5 arrays write data out to drives in stripe units.
The size of the stripe unit can be configured to:
8KB
16KB
32KB
64KB
Synchronization performs the following operations:
Reads all the data bits in each stripe unit
Calculates the parity for that data
Compares the calculated parity with the existing parity for all stripe units in the
array
Updates the existing parity, if inconsistent
Initialization writes zeroes out to the logical drive.
Operating systems may not install properly if the first few sectors are not set to zero
(approximately the first 32 sectors).
After creating an array, the user must create a logical drive.
Physical drives
are the
individual disk drives that are inside the machine. A
logical drive
is the drive that the
array controller shows the operating system. A logical drive spans across multiple
physical drives.
All redundant RAID logical drives are automatically synchronized by the ServeRAID-
4 controller in the background when the logical drive is defined. No other user action
is required.
Providing additional protection for redundant RAID logical drives:
Full tape backups and
automatic data scrubbing provide protection against multiple drive failure and
unprotected grown media defects.
Full tape backups:
Periodic full tape backups force all data files to be read and copied
to tape. This procedure provides two advantages:
It provides an archive of all data in case it is needed to restore from a multiple
drive failure or user error that could cause data loss/corruption.