vgdisplay: Volume group not activated .

[sysad_boy]

Hi Guys,

I have a problem with my vg01, as it can no longer be seen by vgdisplay command. When I am executing vgdisplay -v, it only sees vg00 but not vg01. This is kind of strange, but the server went down unexpectedly due to temperature problem earlier today. After the server went up that's the time I experienced the problem


Here is the full message being shown to me by the OS after invoking the vgdisplay command:

vgdisplay: Volume group not activated.
vgdisplay: Cannot display volume group "/dev/vg01".


Is there a way to activate the volume group?


TIA

[Torsten. · Accepted solution]

If the server is NOT part of a cluster, use

# vgchange -a y vg01

[Pete Randall]

You need to look at your /etc/rc.log to see why it wasn't activated automatically during normal startup. In the meantime, as Torsten says:

vgchange -a y /dev/vg01


Pete

[UVK]

Is this server in cluster ? If not just use the below.

#vgchange -a y vg01

if in cluster ensure this VG is not active on other node. generally you should not be able to activate this if this vg is active on othernode and you will know that from the error message you get

[sysad_boy]

Yes I did tried that but it didnt work:

vgchange: Warning: Couldn't attach to the volume group physical volume "/dev/dsk/c5t0d0":
Unknown error
vgchange: Warning: couldn't query physical volume "/dev/dsk/c5t0d0":
The specified path does not correspond to physical volume attached to
this volume group
vgchange: Warning: couldn't query all of the physical volumes.
vgchange: Couldn't activate volume group "/dev/vg01":
Quorum not present, or some physical volume(s) are missing.



I tried re-running the very same command but to no avail but this time with a different message:

Cannot lock "/etc/lvmconf//lvm_lock" still trying ...

[sysad_boy]

this server is not a member of a cluster

[Avinash20]

The above steps included when it is not in cluster.
You could if this server is part of cluster via

# cmviewcl
<< If no cluster, the above will say command not found >>
or vgchange will not work, and give error, vg conflict node.

DO the following if not a cluster

# vgchange -a y vg01
# fsck -y
# mount -a
# vgdisplay vg01
# bdf

[sysad_boy]

/etc/rc.log:


"Mount file systems
Output from "/sbin/rc1.d/S100localmount start":
----------------------------
mountall: cannot mount /dev/vg01/mjj_temp
mountall: diagnostics from mount
vxfs mount: Cannot open /dev/vg01/mjj_temp: No such device or address
mountall: cannot mount /dev/vg01/lvoper
mountall: diagnostics from mount
vxfs mount: Cannot open /dev/vg01/lvoper: No such device or address
mountall: cannot mount /dev/vg01/lvol1
mountall: diagnostics from mount
vxfs mount: Cannot open /dev/vg01/lvol1: No such device or address
mountall: cannot mount /dev/vg01/lvol2
mountall: diagnostics from mount
vxfs mount: Cannot open /dev/vg01/lvol2: No such device or address
mountall: cannot mount /dev/vg01/lvbak
mountall: diagnostics from mount
vxfs mount: Cannot open /dev/vg01/lvbak: No such device or address
checking quotas

[Sivakumar MJ._1]

Execute as per Pete and Torsten

#vgchange -a y /dev/vg01

http://docs.hp.com/en/B2355-90692/vgchange.1M.html

[sysad_boy]

I am scared executing the fsck command, is it really safe? what if there are inconsistencies in the metadata area? won't it delete some of my files?