vg01.conf wrong

[TWBSupport]

Ok - I'm finding all kinds of issues working on the vg03 error that I have posted previously. Upon deleting the lvmtab file as suggested by HP 1st tier support and recreating it by a vgscan, my vg01 was deleted out. So.. I know how to fix this, vgcfgrestore..... Upon looking at the vg01.conf file, it's wrong. The actual disks that vg01.conf has allocated to it is c4t4d0 & c4t5d0, vg01.conf shows c4t0d0 and c4t1d0. I know these are not the correct disks. The backup file has the same, the file has been wrong for the last 2 years. UGH! Can I modify the conf file? Or what else can be done to get this back up and functional.

[Victor Fridyev · Accepted solution]

Hi,

Sorry, I'm not familiar with the previous history, so my assumption can be wrong, but why do you need this *conf file.
If you are sure about the disks of the vg, the only thing which you have to do is:

mkdir /dev/vg01
mknod /dev/vg01/group c 64 0x0N0000 (N must be unique on the computer)
vgimport /dev/vg01 /dev/dsk/XXXX /dev/dsk/YYYY

HTH

[TWBSupport]

Good gracious. I'm making this harder than what it needs to be then.. I love these systems, they run forever without any issues, so as long as I keep them maintained, I don't do much on them. Every couple of years something like this happens and I have relearn everything.

So as long as I do the vgimport, my vg01 will come back online with data intact?

[Jaime Bolanos Rojas.]

Denda,

Please post the link you the thread that you are talking about, and do not forget to give points to the poeple that kindly take their time to answer your questions.

Regards,

Jaime.

[Chan 007]

Yes,

if you do a vgimport, you will get all the data on it.

Chan

[Marvin Strong]

Yes your data will be intact with vgimport provided you are 100% certain you have the correct disks.

The questions I have is what date was that conf file created. typically the system automatically makes that when the vg changes.

But as stated above. if you know the disks.

mkdir
mknod
vgimport vg01 {list of disks}

will bring your vg back

[TWBSupport]

The previous thread has really nothing to do with this, but the fact that the lvmtab was deleted and recreated. Here's the link though http://forums1.itrc.hp.com/service/forums/bizsupport/questionanswer.do?threadId=1045419

I always post points when the problem is resolved. As of this posting I still have a problem.

[TWBSupport]

Thanks to all of you for your quick responses! This place is sooooo much faster than tier 1 & 2 support! Do I delete the current vg01 directory that resides in /dev ? I just want to make sure I have all my ducks in a row. Thanks again.

[Victor Fridyev]

Hi,

The data will be stored, take into account the only one thing: such a restore will give the standard names to logical volumes: lvol1, lvoil2 etc...

HTH

[Marvin Strong]

hmm you sure that vgscan removed your vg01?
if you do vgdisplay vg01 what do you get?

[TWBSupport]

don't worry about answering that stupid question of mine. I deleted it and recreated everything and everything looks good, however it tells me the following "vgimport /dev/vg01 /dev/dsk/c4t4d0 /dev/dsk/c4t5d0
vgimport: Warning: Volume Group contains "3" PVs, "2" specified. Continuing." So I'll start investigating that road.

[Torsten.]

Please check the config backup first:

vgcfgrestore -n vg01 -l

vgcfgrestore -n vg03 -l

and check the disk too, e.g.:

pvdisplay -v /dev/dsk/c4t1d0


Does it match?

[Marvin Strong]

That typically means you missed a disk.
It could just be an alternate path that was missing also.

[TWBSupport]

Sorry I reported wrong... I did the vgimport, but no data is showing up still... Any ideas?

[TWBSupport]

If I run the vgcfgrestore -n vg01 will that try to copy the old vg01.conf over? I don't want that since that is not the correct disks

[Jaime Bolanos Rojas.]

Denda, Also if you are running 11.11, this patch PHCO_34196 used to fix that warning when doing the vgimport.

Regards,

Jaime.

[Marvin Strong]

after your vgimport you need to vgchange -a y vg01

then you should be able to vgdisplay vg01

[Torsten.]

Again, the commands I gave you will not write to the disk, only to the screen!

Use this to check the configuration.

[TWBSupport]

Thank you all again for your quick responses. I activated the vg, although I forgot to mount the directories. DOH! But then my 1st tier support person called me back and did not want me to do a vgimport and asked me to undo everything that I just did. And perform several other steps prior to the vgimport, like copying over the old lvmtab, exporting it out and going from there and we bounced around quite a bit and I can't recall everything. I apologize. Everything then started coming up OK. We got rid of the mystery disk by running vgreduce -f on the volume group and that got rid of that error. Thanks again