| Troubleshooting & |
| Module Replacement |
|
|
NOTE! An important side effect of the | commands is that the LVM configuration |
backup file used by the | command in step 3 is updated. If this hot plug procedure |
is being performed now on another host system and there was no need to execute lvreduce commands, then the configuration file has not been updated. However, the LVM
vgcfgbackup command.
Step 4
he replaced disk module to the active volume group with the
vgchange
#vgchange a y <volume group name>
#vgchange a y /dev/vg00
Note for MC/ServiceGuard If the disk array is used in an MC/ServiceGuard cluster volume
| vgchange – |
/dev/vgcluster |
|
| VG Status from the vgdisplay: |
VG Status | Command |
Available | |
Availble, exclusive | vgchange – |
Available, shared, server | Not sure what to do with SLVM |
| Not sure what to do with SLVM |
*available may |
|
Step 5 |
|
| 6. If the disk is the mirror of a root disk: |
a.mkboot command on the replaced disk.
If you use the example from “Example of a Disk Module Failure”, the host will display:
# mkboot /dev/rdsk/c2t4d0
Run the | |||
# lv1nboot | R |
|
|
|
| 5 |
|
|
| mkboot and |
commands are repeatable with no harm.
65
Troubleshooting