In article <vqvbkpegn1di2d@corp.supernews.com>, Mike wrote:
> The nimadm migration worked fantastically. Now to destroy old_rootvg,
> mirror hdisk0 back to hdisk1, then change bootlist back to hdisk0.
> However, the only way I can find to destroy the old_rootvg is
> through smitty, but smitty (the commands it executes) wants old_rootvg
> to be vary'd on (varyonvg old_rootvg), but this command can't
> find the device(?) and wants me to run redefinevg before it will
> vary on old_rootvg. I'm reluctant to go forward.
>
> The question is what to do now? I want to destroy old_rootvg
> (this contains the old 4.3.3 os), extendvg rootvg hdisk0,
> mirrorvg -c 2 rootvg hdisk0, bootlist -m normal hdisk0 hdisk1,
> bootlist -ad /dev/hdisk0.
>
> Suggestions?
>
> Mike

Thanks to help I have two ways and another command to execute.
The documentation says to use alt_disk_install -X old_rootvg.
This needs to run on the client, so ftp the file over (binary)
and chmod 755 alt_disk_install, then ./alt_disk_install -X rootvg.
Worked nicely. The other way someone suggested is to use
exportvg old_rootvg to remove it. Didn't try that. I did run
into another problem adding the disk back with extendvg rootvg hdisk0
in that extendvg complained that hdisk0 already belonged to a
vg. Running extendvg -f rootvg hdisk0 fixed that problem.

Then I ran mirrorvg -c 2 rootvg hdisk0, then manually ran
syncvg -l LVNAME on those things that came up stale.

All is well, thanks for the help.

Mike