Originally posted by: teletype

We are in the process of migrating from HP3PAR storage to IBM svc storage. We use migratepv for this. It has bin done on a 100+ systems without a problem.
On one system however we see errors in extendvg:

# extendvg rootvg hdisk3

0516-1398 extendvg: The physical volume hdisk3, appears to belong to
another volume group. Use the force option to add this physical volume
to a volume group.
0516-792 extendvg: Unable to extend volume group.
# extendvg -f rootvg hdisk3
0516-078 extendvg: Incomplete device driver configuration. Probable
    cause is the special file for the VG is missing. Execute
    varyoffvg followed by varyonvg to build correct environment.
 

We also see strange things using lspv and lsvg -p:

# lspv
hdisk0          00c646e7d51d62ba                    rootvg          active
hdisk3          00c646e7c1e568a2                    None

# lsvg -p rootvg
rootvg:
PV_NAME           PV STATE          TOTAL PPs   FREE PPs    FREE DISTRIBUTION
hdisk0            active            399         156         00..00..23..54..79
hdisk3            active            399         399         80..80..79..80..80
hdisk3            active            399         399         80..80..79..80..80
hdisk3            active            399         399         80..80..79..80..80
hdisk3            active            399         399         80..80..79..80..80
hdisk3            active            399         399         80..80..79..80..80

# readvgda hdisk0 |  grep pv_id
pv_id:          00c646e7d51d62ba
pv_id:          00c646e7c1e568a2
pv_id:          00c646e7c1e568a2
pv_id:          00c646e7c1e568a2
pv_id:          00c646e7c1e568a2
pv_id:          00c646e7c1e568a2

# lqueryvg -Ptp hdisk0
Physical:       00c646e7d51d62ba                1   0
                00c646e7c1e568a2                1   0
                00c646e7c1e568a2                1   0
                00c646e7c1e568a2                1   0
                00c646e7c1e568a2                1   0
                00c646e7c1e568a2                1   0

I also tried to read the secondary vgda. Same result for readvgda -p and -s.
Is there a way, other than backup / restore, to remove hdisk3 from the volumegroup?

Some other info on this system. It is a virtual machine running AIX 7100-04-01-1543. The disks are mapped from two vio servers though a vscsi adapter.

I asked the same question here but that seems a more general forum then this one