Adaptec 133U2 User Guide - Page 101

Pausing I/O on an, Array, Creating Dedicated Spares or, a Spare Pool

Page 101 highlights

Performing Array, Spare, and Disk Operations As long as the array member is physically functional, you can reconstruct it with the Reconstruct command. You can reconstruct the array immediately, or you can schedule the reconstruct to occur at a later time. Since the reconstruction process may take a long time, you may want to schedule it for a time when there is less activity on the system. Note: The Reconstruct operation can take up to several hours for a large array. Follow these steps to reconstruct an array when a disk fails: 1 Determine which array is in Critical status and which disk in the array has failed. It is possible that a RAID 0/1 array in Critical status may have more than one failed disk. The array can still be reconstructed without data loss as long as at least one disk of each mirrored pair is still good. 2 If the array enclosure does not support hot swapping1, pause I/O to the array before you continue. (See Pausing I/O on an Array on page 7-5.) Skip this step if the array enclosure supports hot swapping. 3 Remove the failed disk and allow I/O to resume. 4 Insert a good disk of at least the same storage capacity. Be sure that the SCSI ID of the new disk is different from the SCSI ID of other installed devices. Or, if an array disk was accidentally disconnected, reconnect it. 5 Issue a Rescan command to detect the new disk. 6 If you installed a new disk (or disks), make the disk into a spare by following the directions in Creating Dedicated Spares or a Spare Pool on page 5-14. Be sure the new spare disk is at least as large as the smallest array member. 1 Hot swapping support means that the array enclosure electrically isolates the bad disk's SCSI connector from the SCSI bus while the disk is being swapped to prevent data corruption. Data can still be transferred to and from the remaining good disks while the bad drive is replaced. 7-3

  • 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

7-3
Performing Array, Spare, and Disk Operations
As long as the array member is physically functional, you can
reconstruct it with the Reconstruct command. You can reconstruct
the array immediately, or you can schedule the reconstruct to occur
at a later time. Since the reconstruction process may take a long time,
you may want to schedule it for a time when there is less activity on
the system.
Note:
The Reconstruct operation can take up to several
hours for a large array.
Follow these steps to reconstruct an array when a disk fails:
1
Determine which array is in Critical status and which disk in
the array has failed.
It is possible that a RAID 0/1 array in Critical status may have
more than one failed disk. The array can still be reconstructed
without data loss as long as at least one disk of each mirrored
pair is still good.
2
If the array enclosure does not support hot swapping
1
, pause
I/O to the array before you continue. (See
Pausing I/O on an
Array
on page 7-5.) Skip this step if the array enclosure
supports hot swapping.
3
Remove the failed disk and allow I/O to resume.
4
Insert a good disk of at least the same storage capacity. Be sure
that the SCSI ID of the new disk is different from the SCSI ID of
other installed devices. Or, if an array disk was accidentally
disconnected, reconnect it.
5
Issue a Rescan command to detect the new disk.
6
If you installed a new disk (or disks), make the disk into a
spare by following the directions in
Creating Dedicated Spares or
a Spare Pool
on page 5-14. Be sure the new spare disk is at least
as large as the smallest array member.
1
Hot swapping
support means that the array enclosure electrically isolates the
bad disk’s SCSI connector from the SCSI bus while the disk is being
swapped to prevent data corruption. Data can still be transferred to and
from the remaining good disks while the bad drive is replaced.