MAP 6002: This procedure replaces a flash drive that
has failed while it is still a member of a storage pool.
Before you begin
If you are not familiar with these maintenance analysis
procedures (MAPs), first read Using the maintenance analysis procedures.
This
map applies to models with internal flash drives.
Be sure that you know which model you are using before you start this
procedure. To determine which model you are working on, look for the
label that identifies the model type on the front of the node.
Attention: - Back up your SAN Volume Controller configuration
before you begin these steps.
- If the drive use property is member and
the drive must be replaced, contact IBM support before taking any
actions.
About this task
Perform the following steps if a drive fails in a RAID 1
or RAID 10 array:
Procedure
- Make sure the drive property use is not member.
Use the lsdrive CLI command to determine the use.
- Record the drive property values of the node
ID and the slot ID for use in step 4. These
values identify which physical drive to remove.
- Record the error sequence number for use in
step 11.
- Use the drive ID that you recorded in
step 2 to
set the use attribute property of the drive to unused with
the chdrive command.
chdrive -use failed <id of offline drive>
chdrive -use unused <id of offline drive>
The drive
is removed from the drive listing.
- Follow the physical instructions to replace or remove a
drive. See the "Replacing a SAN Volume Controller
2145-CG8 flash drive" documentation
or the "Removing a SAN Volume Controller
2145-CG8 flash drive" documentation
to find out how to perform the procedures.
- A new drive object is created with the use property set
to unused.
- Change the use property for the drive to candidate.
chdrive -use candidate <id of new drive>
- Change the use property for the drive to spare.
chdrive -use spare <id of new drive>
- If you are using spare drives, perform a member exchange. Move
data from the spare to the newly inserted device.
- If you do not have a spare, when you mark the drive object as spare,
the array starts to build on the newly inserted device.
- If the spare is not a perfect match for the replaced drive,
then the array is considered unbalanced, and error code 1692 is recorded
in the error log.
- Follow the fix procedure to complete the procedure.
- Mark the drive error as fixed using the error
sequence number from step 3.
cherrstate -sequencenumber <error_sequence_number>