Need to activate the VG after chnage the device name

[Aungshuman Paul]

Hi ,

Can anyone help on following issue :

Currently we change the Fibre channel adapter on a server. After change we do necessary for present the disk. Now ioscan o/p shows all disks but the disk's device name is change. So the VG is not activated.

Please help me how can I activate the VG :
gchange: Warning: couldn't query all of the physical volumes.
vgchange: Couldn't activate volume group "vg03":
Quorum not present, or some physical volume(s) are missing.

Aungshu

[Torsten.]

The swap of a HBA should not cause a different path or device file.

Can you please post

# strings /etc/lvmtab

# vgdisplay -v vg03

# ioscan -fn


However, a vgexport/vgimport should solve this.

[Aungshuman Paul]

Hi,

Thanks. My problem is solved by done the following :
1. Execute vgscan for
# vgscan -pav

2. then move lvmtab
# mv /etc/lvmtab /tmp/lvmtab.09082010

3. Then vgscan again for create the lvmtab again :
# vgscan -av

4. Then activate the VG :
# vgchange -a y vg03


Anyway thanks for the post.

Aungshu

[Torsten.]

Just another way to reach the same target. I prefer vgexport/vgimport, because a vgscan may produce other trouble somewhere.

I still wonder about the changed device file ... do you have some more information?

[Aungshuman Paul]

Previous device file with path :
for 838 GB disk :
/dev/dsk/c6t0d6
/dev/dsk/c7t0d6

for 1TB disk :
/dev/dsk/c6t0d3
/dev/dsk/c7t0d3

After Change the Raiser Card and Fibre Channel Adapter the new device file is :
/dev/vg03
/dev/dsk/c13t0d3
/dev/dsk/c13t0d6
/dev/dsk/c14t0d3
/dev/dsk/c14t0d6
/dev/dsk/c1t0d3
/dev/dsk/c1t0d6
/dev/dsk/c8t0d3
/dev/dsk/c8t0d6

But why you think device file will not change?

Aungshu

[Viktor Balogh]

Hi Aungshu,

Torsten is right, with a simple FC HBA change the device name should'nt be changed. Maybe they changed something on the zoning, ask the storage team. I've cooperated in several FC HBA change without any device name change. There was one case where the devices got new names, but it turned out they changed the domain settings at the zoning level.

[Torsten.]

Look at this example:

disk 2 1/0/8/1/0/4/0.13.0.0.0.0.7 sdisk CLAIMED DEVICE
HP HSV200
/dev/dsk/c2t0d7 /dev/rdsk/c2t0d7
/dev/dsk/c2t0d7s1 /dev/rdsk/c2t0d7s1
/dev/dsk/c2t0d7s2 /dev/rdsk/c2t0d7s2
/dev/dsk/c2t0d7s3 /dev/rdsk/c2t0d7s3


This is a boot disk connected to a superdome nPar.


This part is the PCI slot and the combo card

1/0/8/1/0/4

and this part is the switch with domain ID 13, storage is connected to port 0, LUN number is 7

13.0.0.0.0.7


If you replace the HBA with the same type in the same slot, the hardware path (and device file) remains to be the same.


What "riser card" did you change ???

[Aungshuman Paul]

In my cases we change the HBA card on different port after change the RISER card.

Thats why the device file name was changed.

Aungshu

[Torsten.]

OK, if you use a different port (e.g. on HBA) you get new device files.

What is your server model?
I still wonder about the riser card.