MAP 6000: This procedure replaces a solid-state drive (SSD) that
has failed while it is still a member of a managed disk (MDisk) group.
If you are not familiar with these maintenance analysis
procedures (MAPs), first read Using the maintenance analysis procedures.
This MAP applies to all SAN Volume Controller models. Be sure that you know which model you are using before
you start this procedure. To determine which model you are working
with, look for the label that identifies the model type on the front
of the node.
Perform the following steps to delete all the VDisks and
VDisk host mapping or the managed disk group that contains the failed
managed disk.
Attention: Back up your SAN Volume Controller configuration
before you begin these steps.
- Is the MDisk a managed mode MDisk or an
image mode MDisk?
- Managed mode MDisk
- Go to step 2.
- Image mode MDisk
- Go to step 3.
- (From step 1)
- Record the properties of all VDisk copies,
including unmirrored VDisks, that use storage from the managed disk
group that contains the offline managed disk.
Note: You can recover the copied VDisk data from the copy.
All the data on the unmirrored VDisks will be lost and will need to
be restored from backup.
- Record the properties of the managed disk
group and the list of managed disks in that managed disk group. Make
particular note of the node_name, controller_name,
and location of the SSD managed disk that needs
to be replaced.
- Submit the command svcinfo lsnodevpd (node_name),
where (node_name) is the value of that property
variable recorded in step b. Record the front_panel_id property
of this node.
- Delete the MDisk group that contains the
offline MDisk. Use the force parameter to remove the MDisk group because
it will still contain VDisks.
- Follow the instructions to replace an SSD
or to remove an SSD. Use
the front_panel_id to identify the correct node
from the label on the front panel of the node and the location of
the MDisk to identify the correct drive slot.
- Run the svctask detectmdisk command
to detect the new managed disk.
- Create a new managed disk group with the same properties
as the deleted MDisk group and add the new managed disk to the group.
- Add all other managed disks that had been present in
the deleted MDisk group into the new managed disk group.
- Use the information that you recorded in substeps a
and b to:
- Add a VDisk copy for all VDisks that had been mirrored in the
original managed disk group.
- Re-create all standard VDisks and VDisk host mapping that had
been members of the original managed disk group and restore the data
from the backups.
- (From step 1)
- Record the properties of the
image mode VDisk or VDisk copy that corresponds to the offline image
mode managed disk.
- Record the properties of the
offline managed disk, especially the node_name, controller_name,
and location.
- Submit the command svcinfo lsnodevpd (node_name),
where (node_name) is the value of that property
variable recorded in step b. Record the front_panel_id property
of this node.
- If the image mode VDisk is mirrored, remove the VDisk
copy that is residing on the offline MDisk; otherwise, delete the
image mode VDisk that corresponds to the offline MDisk.
- Follow the instructions to replace an SSD
or to remove an SSD. Use
the front_panel_id to identify the correct node
from the label on the front panel of the node and the location of
the MDisk to identify the correct drive slot.
- Re-create the image mode VDisk or re-add the image mode
VDisk copy on the new managed disk using the information that you
recorded in substeps a and b.