EMC volumes not available after reboot

[Shawn Miller_2]

After every reboot I have to manually run vgchange -a y vg** on the same six volume groups and then run a mountall to get every thing back up. Any suggestions on how to resolve this.

[Jeff Schussele · Accepted solution]

Hi Shawn,

Do you have, or have you had Service Guard on this system?
If so, then check the /etc/lvmrc file as you may need to set
AUTO_VG_ACTIVATE=1
if you no longer use MC/SG.
If you are using it, then add them to the
custom_vg_activation()
function.

HTH,
Jeff

[Shawn Miller_2]

I do have MC Service Guard running on this server. The volume groups I have problems with are not part of the service guard cluster. They are for an application that only runs on this server. Service Guard is needed on this server since it is a failover node for two other servers.

[Sanjay_6]

Hi,

check you /etc/lvmrc file and see if the entry AUTO_VG_ACTIVATE is set to "0". If this is set to zero, no vg other than root will get activated automaticallt at the system boot. Any vg that gets activated automatically in this situation may be mentioned in the custom_vg_activate section in the same file.

If you want all the vg's on the system to be activated at the time of system boot, change the auto_vg_activate to "1" from "0".

Hope this helps.

Regds

[Jeff Schussele]

Hi (again) Shawn,

Then you'll need to add these non-MC/SG VGs to that custom_vg_activation() function or they won't be auto-activated at boot.
You just add them all as follows:

/sbin/vgchange -a y /dev/vg_name1
/sbin/vgchange -a y /dev/vg_name2
etc...

Rgds,
Jeff

[Todd McDaniel_1]

Did you recently create these VGs? also, what are the mount options you are using on them. Sometimes I have noticed if your license is not fully enabled, the filesystems will not mount upon reboot. Where you get a warning, when mount -a is executed, saying mount options are not compatible with this version of vxfs...?

Also, I think I remember seeing a posting about a similar problem where the startup scripts didnt allow enough time to recognize the Frame disks. And that a sleep statement in the RC script solved the problem... However, I can't remember exactly what it referred to.

[Todd McDaniel_1]

Sorry one more thing... did you run vgcfgbackup after you created them? just a thought.

[Shawn Miller_2]

I just want to clarify.
Is it true that I should not change AUTO_VG_ACTIVATE=0 to 1 since I am currently using service guard on this server.
Second I can without effecting service guard and any of it's volumes add the volume groups that I want to be activated under
custom_vg_activation right after vg00.

For example:
/sbin/vgchange -a y /dev/vg00
/sbin/vgchange -a y /dev/vg_y101


So, leave AUTO set at 0 and add under custom_vg_activation in /etc/lvmrc

[Jeff Schussele]

Hi Shawn,

Yes - exactly.
Leave it at 0 & add the non-MC/SG VGs to the activate function.

Rgds,
Jeff