Cannot display volume group "/dev/vgdb2bip".

[sunil_chhabra]

Hi All,

i am new to HP-UX. in our infra we have two node cluster having HP-UX with SG on it. at sudden one node got crashed and we were not having ignite backup of crashed node on that sudden moment. so some Expert suggested us to take ignite backup of first node and build the crashed node from it. we did the same and made changes in IP and hostname.

after that when we started SG than crashed system was not showing any application related mount points. when we run VGDISPLAY it was showing error ( vgdisplay: Cannot display volume group "/dev/vgPIPdb2".     vgdisplay: Volume group not activated.). also when we run ioscan -m lun than all /dev/rdisk/disk (LUN) name was in changed state. please suggest what to do?

root>vgdisplay
vgdisplay: Couldn't query volume group "/dev/vg00".
Possible error in the Volume Group minor number; Please check and make sure the group minor number is unique.
vgdisplay: Cannot display volume group "/dev/vg00".
vgdisplay: Volume group not activated.
vgdisplay: Cannot display volume group "/dev/vglock".
vgdisplay: Volume group not activated.
vgdisplay: Cannot display volume group "/dev/vgBIPERS10".
vgdisplay: Volume group not activated.
vgdisplay: Cannot display volume group "/dev/vgBIPlog_dir".
vgdisplay: Volume group not activated.
vgdisplay: Cannot display volume group "/dev/vgBIP".
vgdisplay: Volume group not activated.
vgdisplay: Cannot display volume group "/dev/vgBIPdb2dump".
vgdisplay: Volume group not activated.
vgdisplay: Cannot display volume group "/dev/vgdb2bip".
vgdisplay: Volume group not activated.

attaching old and new ioscan -m lun outputs. please help me for the same.

[sunil_chhabra]

also now second node is showing the same error. that is below error.

root>vgdisplay
--- Volume groups ---
VG Name /dev/vg00
VG Write Access read/write
VG Status available
Max LV 255
Cur LV 8
Open LV 8
Max PV 16
Cur PV 1
Act PV 1
Max PE per PV 4461
VGDA 2
PE Size (Mbytes) 32
Total PE 4451
Alloc PE 4416
Free PE 35
Total PVG 0
Total Spare PVs 0
Total Spare PVs in use 0
VG Version 1.0
VG Max Size 2284032m
VG Max Extents 71376

vgdisplay: Volume group not activated.
vgdisplay: Cannot display volume group "/dev/db2pip".
vgdisplay: Volume group not activated.
vgdisplay: Cannot display volume group "/dev/vgBIP".
vgdisplay: Volume group not activated.
vgdisplay: Cannot display volume group "/dev/vgBIPASCS00".
vgdisplay: Volume group not activated.
vgdisplay: Cannot display volume group "/dev/vgBIPDEVMSG01".
vgdisplay: Volume group not activated.
vgdisplay: Cannot display volume group "/dev/vgBIPERS10".
vgdisplay: Volume group not activated.
vgdisplay: Cannot display volume group "/dev/vgBIPSCS03".
vgdisplay: Volume group not activated.
vgdisplay: Cannot display volume group "/dev/vgBIPdb2dump".
vgdisplay: Volume group not activated.
vgdisplay: Cannot display volume group "/dev/vgBIPlog_dir".
vgdisplay: Volume group not activated.
vgdisplay: Cannot display volume group "/dev/vgBIPsapdata1".
vgdisplay: Volume group not activated.
vgdisplay: Cannot display volume group "/dev/vgBIPsapdata2".
vgdisplay: Volume group not activated.
vgdisplay: Cannot display volume group "/dev/vgBIPsapdata3".
vgdisplay: Volume group not activated.
vgdisplay: Cannot display volume group "/dev/vgBIPsapdata4".
vgdisplay: Volume group not activated.
vgdisplay: Cannot display volume group "/dev/vgBIPsapmnt".
vgdisplay: Volume group not activated.
vgdisplay: Cannot display volume group "/dev/vgBIPsaptemp1".
vgdisplay: Volume group not activated.
vgdisplay: Cannot display volume group "/dev/vgBIPtrans".
vgdisplay: Volume group not activated.
vgdisplay: Cannot display volume group "/dev/vgPIP".
vgdisplay: Volume group not activated.
vgdisplay: Cannot display volume group "/dev/vgPIPASCS00".
vgdisplay: Volume group not activated.
vgdisplay: Cannot display volume group "/dev/vgPIPDEVMSG01".
vgdisplay: Volume group not activated.
vgdisplay: Cannot display volume group "/dev/vgPIPERS10".
vgdisplay: Volume group not activated.
vgdisplay: Cannot display volume group "/dev/vgPIPSCS03".
vgdisplay: Volume group not activated.
vgdisplay: Cannot display volume group "/dev/vgPIPdb2dump".
vgdisplay: Volume group not activated.
vgdisplay: Cannot display volume group "/dev/vgPIPlog_dir".
vgdisplay: Volume group not activated.
vgdisplay: Cannot display volume group "/dev/vgPIPsapdata1".
vgdisplay: Volume group not activated.
vgdisplay: Cannot display volume group "/dev/vgPIPsapdata2".
vgdisplay: Volume group not activated.
vgdisplay: Cannot display volume group "/dev/vgPIPsapdata3".
vgdisplay: Volume group not activated.
vgdisplay: Cannot display volume group "/dev/vgPIPsapdata4".
vgdisplay: Volume group not activated.
vgdisplay: Cannot display volume group "/dev/vgPIPsapmnt".
vgdisplay: Volume group not activated.
vgdisplay: Cannot display volume group "/dev/vgPIPsaptemp1".
vgdisplay: Volume group not activated.
vgdisplay: Cannot display volume group "/dev/vgPIPtrans".
vgdisplay: Volume group not activated.
vgdisplay: Cannot display volume group "/dev/vgdb2bip".
vgdisplay: Volume group not activated.
vgdisplay: Cannot display volume group "/dev/vglock".

[Torsten.]

>> vgdisplay: Volume group not activated.

Hence you cannot see a vgdisplay output.

Whatever you have done with the bad node, the other node should still work, right?

What does "cmviewcl" say?

[Stephen Doud]

vgdisplay will not show any VG that is not activated.

A cluster-owned VG will not activate until it's package is started

Failover packages can only start on one node at a time.  Run vgdisplay on the node where the package is running, to see details about the VG.