Removing hard drives from rootvg 1

[Skeater]

IBM came out and replaced two drives without getting rid of the descriptions for the original two drives. I am getting messages like this:

# chpv -v r 00091540b4a7aea6
0516-022 lquerypv: Illegal parameter or structure value.
0516-724 chpv: Unable to change physical volume 00091540b4a7aea6.
There is an open logical volume.
0516-722 chpv: Unable to change physical volume 00091540b4a7aea6.
#

When trying to delete it from the volume group I get:
0516-304 putlvodm: Unable to find device id 00023575f18b62b6 in the Device
Configuration Database.
0516-896 reducevg: Warning, cannot remove physical volume 00023575f18b62b6 from
Device Configuration Database.

Any advice would be greatly appreciated.

 

[aixqueen]

Check this doc out...

http://techsupport.services.ibm.com...mode=9&documents=290605220714596&database=aix

you will probably have to reduce everything by using the pvid number.
MAKE SURE YOU STILL HAVE YOUR DATA BACKED UP with a mksysb if
you have it............any new data backed up since the last mksysb etc...
-----------------------------------
Deallocating physical partitions from the disk

Every physical partition (PP) on the disk allocated to any logical
volume (LV), including file systems or paging
spaces, must be deallocated, either by moving the contents
of those PPs to another disk or by removing them.

To determine what logical volumes have PPs allocated
to that disk, run:

lspv -l <hdisk#>

If the hdisk name no longer exists, and the disk is identifiable
only by its 16-digit PVID (you might see this from
the output of lsvg -p <VGname>), substitute the PVID for the
disk name. For example:

lspv -l 0123456789abcdef

You may receive the following error:

0516-320 : Physical volume 00001165a97b10c6 is not assigned to
a volume group.

If so, run the following command:

putlvodm -p `getlvodm -v <VGname>` <PVID>

VGname refers to your volume group, PVID refers to the 16-digit physical volume
identifier, and the characters around the getlvodm command are grave
marks, the backward single quote mark. The lspv -l <PVID>
command should now run successfully.


If another disk in the volume group has space to contain the partitions
on this disk, and the disk to be replaced has not failed, the migratepv
command may be used to move the used PPs on this disk. See the man
page for the migratepv command on the steps to do this.

If the partitions cannot be migrated, they must be removed.
The output of the lspv -l <hdisk#>, or lspv -l<PVID>,
command indicates what logical volumes will be affected. Run the
following command on each LV:

lslv <LVname>

The COPIES field shows if the LV is mirrored. If so, remove
the failed copy with:

rmlvcopy <LVname> 1 <hdisk#>

hdisk# refers to all the disks in the copy that contain the failed disk.
A list of drives can be specified with a space
between each. Use the lslv -m <LVname> command to see
what other disks may need to be listed in the
rmlvcopy command. If the disk PVID was previously used with the lspv
command, specify that PVID in the list of disks given to the rmlvcopy
command. At AIX Version 4.2.1 or higher, the unmirrorvg command may be
used in lieu of the rmlvcopy command. See the man pages for rmlvcopy and
unmirrorvg, or other documentation, for additional information.

If the LV is not mirrored, the entire logical volume must be removed,
even if just one physical partition resides on
the drive to be replaced and cannot be migrated to another disk.
If the unmirrored LV is a JFS file system,
unmount the file system and remove it. Enter:

umount /<fsname>
rmfs /<fsname>

If the unmirrored logical volume is a paging space, see if it is active. Enter:

lsps -a

If it is active, set it to be inactive on the next reboot. Enter:

chps -a n <LVname>

After you reboot, remove it by entering:

rmps <LVname>

Remove any other unmirrored logical volume with the following command:

rmlv <LVname>

NOTE: If the LV is serving as a dump device, the dump pointer must first be
reassigned. The same is true if the LV was mirrored and the copy is
being removed. Check the dump pointers by entering:

sysdumpdev -l

Reassign the dump pointers. Enter:

sysdumpdev -Pp /dev/sysdumpnull (for the primary device)
sysdumpdev -Ps /dev/sysdumpnull (for the secondary device)

The pointers can be reassigned to the appropriate logical volume
after it is recreated.

 

[Skeater]

Thank you very Much!