failure in vg00

[navin]

Hi i may have to replace my root disk,it is the vg00.i have 5 more volume groups in the system.those are from external disks.How what should be the procedure to import and export the volume groups.in the below cases
1)System wont boot after reboot ..ignite restore from tape - just vg00
2)System wont boot after reboot....cold install

Thanks Much in advance.

[James R. Ferguson]

Hi Navin:

First, read the white paper on "Good Disks Go Bad".

http://docs.hp.com/en/5991-1236/When_Good_Disks_Go_Bad_WP.pdf

If you need to Ignite (cold install) then you can use 'vgscan -pva' to scan your physical disks by LVM VGID and show which volumes below together.

You can 'vgimport' your non-vg00 disks by specifying the physical paths of those that belong together based on the 'vgscan' output; _OR_ you can 'vgimport' using the '-s' option to analogously query physical volumes with the same LVM VGID. Remember that a "mapfile" can be manufactured with the default logical volume mappings if you don't have one available. You should, though, since Ignite backs up '/etc/lvmconf' which contains LVM mapfiles for your volume groups. These _include_ the VGID within so they are designed to be used with a 'vgimport -s' syntax!

Consult the manpages for 'vgimport' for more details.

Regards!

...JRF...

[Sajjad Sahir]

Dear Navin

please see the above posting with an attachment when good disk go bad
this document contains step by step procedure how to do it. I follow up the above pdf

thanks and regards


Sajjad Sahir

[Ganesan R]

Hi Navin,

If you have mirrored your root disk and one disk failed you can very well replace the failed disk without any downtime. But it is advisable to have latest ignite backup to recover the system if something happened.
>>
1)System wont boot after reboot ..ignite restore from tape - just vg00
<<

No need to import the non-root volume groups. Ignite will restore all the vg configurations.

>>
2)System wont boot after reboot....cold install
<<

If you have to cold install by any chance, then you need map files of all the vg's to import it. So take the map files before the activity by using the command.

#vgexport -p -v -m -s /tmp/vgname.map vgname

backup the map files on some other server

#vgimport -v -m /tmp/vgname.map vgname

You can also import the vg's without map file if you know which disks part of which vg.

#vgimport -v vgname pv1 pv2 ...

Refer man pages for more details.