Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

rootvg removed. How to recreate?

Status
Not open for further replies.

ggitlin

MIS
May 15, 2002
65
AU
Hello,
I was performing system upgrade via alt_disk_copy. After it finished I started cleaning up and accidently removed rootvg via
alt_rootvg_op -X rootvg (instead of old_rootvg).
The system is running but rootvg is missing:
#lsvg
old_rootvg
datavg01
datavg02
#lspv
hdisk0 00cb5d6ded46be29 None
hdisk1 00cb5d6d36a62698 old_rootvg
hdisk2 00c821fdf396fd7b datavg01 active
hdisk3 00c821fdf3970d04 datavg02 active

Is there a way to recreate rootvg definition?
 
hi,

- rebuild the copy of alt_vg, using the same smitty
procedure by which you have created alt_vg
(use smitty!)

- indicate hdisk0 as target disk
- I don't remember how the procedure will name the vg

Try to boot from new Xrootvg, and verify that all is
OK, and there is just a name problem.

If you cannot name or rename it, you can

1) exportvg Xrootvg: this delete Xrootvg from your odm,
but all inside hdisk0 is good.

2) importvg from hdisk0 and name the new vg as rootvg.

May be that during this phase, will be some name conflicts:
/usr already exists, ecc. In this case importvg, imports filesystem, but names them fs001, fs002, ...
Matching the mount points and prev lvname (/dev/hd4...)
rename these lv with the same syntax by which alt_disk_copy
names lvs.

However if these last steps create problems to you,
if after the copy, the boot from alternate disk is ok,
leave all as is: it will be just a name problem,
the reliability of the system will be safe.


ciao
vittorio

 
or just boot off hdisk1(old_rootvg) and when it comes up it should be rootvg.. if i recall correctly..

then just mirror back in hdisk0
extendvg rootvg hdisk0
mirrorvg rootvg hdisk0
bosboot -ad /dev/hdisk0
bootlist -m normal hdisk0 hdisk1
 
Thank you for your suggestions.

My problem is that the old_rootvg contains the old version of the OS, so I have to re-run the OS upgrade and I would have lost all the changes to the OS version on hdisk0, if I remirrored from hdisk1.
I tried running the importvg:
#importvg -y rootvg hdisk0
It worked - there was no name conflict.

Gracias, Vittorio!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top