Volume groups not getting activated when server getting rebooted!!

[Amit Manna_6]

HI,
I am rebooting a HP server. The volume groups are not gettting activated when we reboot the server.
Can anybody suggest whats the issue and what may be the workarond.

[Steven E. Protter]

Check the /etc/lvmrc file.

Perhaps the ACTIVATE variable is set to 0. Set it to 1 for auto activate.

DO NOT do this for volume groups that fail from node to node with ServiceGuard.

Make sure the init level in /etc/inittab is not set to 1. That can cause troubles like this.

strings /etc/lvmtab

ioscan -fnC disk

look for failed disks. A volume group will not activate unless more than 50% of its members (a quorum) are present and working.

mstm/xstm/cstm are useful for diagnosing hardware issues.

SEP

[Todd McDaniel_1]

Are these local or array VGs? direct connect or via network?

I would also suggest checking cabling and whether or not you can pvdisplay the disks.

[Raj D.]

Hi Amit ,

Check /etc/lvmrc file for auto activation is on.

Also check you , all the disk are ok.
# ioscan -fnC disk should be CLAIMED status.

You can use this command to see deactivated Volume groups:
# /usr/sam/lbin/vginfo -D


Cheers.
Raj.

[baiju_3]

Hi ,

Please make uster AUTO_VG_ACTIVATE=1 is set in /etc/lvmrc .

This value will be 0 if MC/SG is configured and in that case you can add the VGs which you want to activate and are not a part of any MC/SG package by adding vg name in following section of lvmrc.
custom_vg_activation()
{
# e.g. /sbin/vgchange -a y -s
# parallel_vg_sync "/dev/vg00 /dev/vg01"
# parallel_vg_sync "/dev/vg02 /dev/vg03"
/sbin/vgchange -a y /dev/vgswap

return 0
}


Bye,
bl.

[Mel Burslan]

if you are running serviceguard, anything other than vg00 should not be activated by default as they may be serviceguard related volumegroups. If you have non-vg00 volume groups which still needs activation in a serviceguard environment, you need to edit the /etc/lvmrc and make the necessary changes in the custom_vg_activation section, following the examples given there like:

/sbin/vgchange -a y /dev/myvg_new

if this is not a serviceguard system, again in the /etc/lvmrcfile, change the following line:

AUTO_VG_ACTIVATE=1


it needs to be set to 1

[Geoff Wild]

Check the /etc/lvmrc file....

See section on "Preventing Automatic Activation of Volume Groups "

http://docs.hp.com/en/B3936-90079/ch05s08.html

Rgds...Geoff

[yyghp]

I have the same issue on one of my servers as well.
There is no MC/SG on the server, and "AUTO_VG_ACTIVATE=1" was set in /etc/lvmrc
Why?