IBM RS/6000 - Manual (Page 73)

3.3.3 Replacing a Previously Defined Drive
If you add a disk drive which was already configured to the system and was
removed using the procedures described above, then you can simply add the new
drive as described in 3.3.1, “Adding a New Drive to a Live System” on page 47.
3.3.3.1 Replacing a Previously Defined Drive into the Same Bay
If a drive was physically removed without first being logically removed from the
operating system, then AIX may have problems. If there were no writes to the disk
after the removal of the disk, then there may be no requirement to run any
commands. If a write occurred after or during the removal of the drive and the
drive has been re-added, then you should perform the following:
1. Unmount all filesystems on the disk.
2. fsck -y filesystems on the disk.
3. Remount the filesystems on the disk.
3.3.3.2 Replacing a Previously Defined Drive into a Different Bay
If you replace a drive into a different bay from the one from which it was removed,
the one configured to the system by running the
cfgmgr command, and you didn't
remove the device from the ODM before physically removing the device, then you
will have to clear up the ODM because there will be a duplicate entry for the drive.
The following shows a scenario where there were three disks in the system and
two volume groups on two separate disks. The disk belonging to
testvg was
physically removed without telling AIX.
Running the lspv command shows the three disks:
lspv
hdisk
a641877c rootvg
hdisk1 b a645b testvg
hdisk2 a62746 4 None
hdisk1 was removed from the system before telling AIX. The disk was replaced
into a different bay than it was removed from. The
cfgmgr command was run to
configure the disk back into the system, and now lspv shows:
lspv
hdisk
a641877c rootvg
hdisk1 b a645b testvg
hdisk2 a62746 4 None
hdisk3 b a645b testvg
There are now two entries for the testvg volume group, both with the same
physical volume identifier. This is incorrect and can be cleared up by performing
the following:
1. Umount all filesystems in the testvg volume group.
2. varyoffvg testvg
3. exportvg testvg
At this point, you may get the following error which you can ignore:
516- 24 /usr/sbin/lqueryvg: Unable to open physical volume.
Either PV was not configured or could not be opened. Run
diagnostics.
Chapter 3. Hot-Swap Subsystem 49