Raw volume groups are not getting activated

[Umamaheswara Reddy]

Hello guys,
We have three cluster nodes with HP-UX 11i V2 using MC-Service guard.After reboot, the raw volumes are not getting activated automatically.Please let me know if I can use vgchange -a y command on raw volume group.

see below for the error message.

vgdisplay: Volume group not activated.
vgdisplay: Cannot display volume group "/dev/vgraw2".
vgdisplay: Volume group not activated.
vgdisplay: Cannot display volume group "/dev/vgraw3".
vgdisplay: Volume group not activated.
vgdisplay: Cannot display volume group "/dev/vgraw4".
vgdisplay: Volume group not activated.
vgdisplay: Cannot display volume group "/dev/vgraw1".
root.uxblrh04:(/root) >

[Suraj K Sankari]

Hi,

Have you checked your package scripts from where these file system are mounted.

Suraj

[Matti_Kurkela]

It depends on the configuration of the VGs.

If the VG has been configured as a cluster VG, "vgchange -a y " will not work: you could use "vgchange -a e " or "vgchange -a s ", depending on whether your raw VGs are supposed to be activated Exclusively in one cluster node at a time only, or Shared between multiple cluster nodes.

But if the VGs have been configured as cluster VGs, in the normal situation you should not have to activate them manually. The VGs should be included in the configuration of some Serviceguard package(s), and starting the package should automatically activate the appropriate VGs in the correct mode. The most likely root cause for the missing VG activation is that the packages have not started for some reason.

You should first verify the cluster state using the "cmviewcl" command. If the node has not joined the cluster, or the entire cluster has not been started, you should fix that first, using the commands cmrunnode/cmruncl as appropriate. The exclusive and shared VG activation options will not be usable on a cluster node until that node is up and running in the cmviewcl listing.

If Serviceguard did not start on a cluster node, check the file /etc/rc.config.d/cmcluster: if the AUTOSTART_CMCLD has been set to 0, Serviceguard won't start/join a cluster automatically.

Once Serviceguard is up and running, check the status of Serviceguard packages. This information is also available in the "cmviewcl" output. If some packages have been configured to not start automatically, you must restart them using the "cmrunpkg" command after restarting the cluster.

After all the cluster packages are in their proper states, check the VG status again. If Serviceguard has not activated the appropriate VGs on the appropriate nodes, your Serviceguard package configuration has some problems, and you should diagnose and fix them if you want your cluster to really be Highly Available.

MK

[Viktor Balogh]

Hi,

I think that you get this message from the output of vgdisplay. Without any parameters, vgdisplay will display information about every activated volume group, and for any inactive vg you'll get such an error message. This is rather informative, as the volume groups belonging to HA packages should be only available where the package is running. For the vgchange: as Matti said, in a cluster environment you should activate the vg in exclusive mode, but this is done automatically when the package starts. (For further reference about exclusive mode, see man vgchange)