VG Activation problem on hp-ux 11iv1

[Subhash_5]

I have added NetApp LUN in HP 2405 server & created VG02 & its working fine.
but after reboot VG is not getting activated automatically. we are having vg01 & Vg00 from internal disk they are getting activated.i checked /etclvmrc & auto_activate_vg is set to 1.
please advice what may be the problem?

Regards
Subhash

[Prashant Zanwar_4]

do you have any messages from startup?
Please check for /etc/rc.log & paste it here..

Regards
Prashant

[Subhash_5]

Thanks for your reply
message i get is cant activate vg02 when system is booting.
do we need any latest patches as this server is 2 years oldinstallation?
please advice.

[Prashant Zanwar_4 · Accepted solution]

It would be always advisible to update the system with latest patches and also upgrade firmware to latest revision..

I am just thinking that VG is not getting activated because LUN isnt available to system at that time of boot..?? Are there any relevant messages regarding that..

For time being you might put a rc script which would run at the end when all system is started up and activate VG..

Also it would be worth checking HP compatibility list of supported SAN products..

Thanks and good luck
Prashant

[Pete Randall]

Can you manually activate the VG after the system boots?


Pete

[Nick W]

Subhash,

Please post the contents of "strings /etc/lvmtab"

Has the VG been exported (vgexport) at any time since the VG was activated (vgchange)?


Regards,
Nick

[Fabien GUTIERREZ]

without any further information it makes me think your vg isn't activated since there is no quorum for this vg. you can activate it through vgchange -a y -q n

regards
Fabien

[Nguyen Anh Tien]

In order to mount all file system you must declare them in /etc/fstab.
such as:
/dev/vg00/lvol3 / vxfs delaylog 0 1
/dev/vg00/lvol1 /stand hfs defaults 0 1
/dev/vg00/lvol4 /home vxfs delaylog 0 2
/dev/vg00/lvol5 /opt vxfs delaylog 0 2
/dev/vg00/lvol6 /tmp vxfs delaylog 0 2
/dev/vg00/lvol7 /usr vxfs delaylog 0 2
/dev/vg00/lvol8 /var vxfs delaylog 0 2

[Devender Khatana]

Hi,

There are a few irrelevant replies earlier so I will just summarize the things to be checked for this to happen

1. The entry in /etc/lvmtab for the VG should be there for it to be activated. Just check by
#strings /etc/lvmtab

2. The availability of the LUN during the VG activation stage. This can be confirmed by looking at the messages during boot. If the lun is not available it will clearly throw a message on screen and will probably wait for some grace period of 300 Sec.

The quorum option and mount entry are not related to this.

Importantly if the issue is not there with manual activation after boot then option 2 can be the case.

HTH,
Devender

[Josiah Henline]

I can think of two things that may affect the VG activation.

1.) The VG is part of or was part of an HA cluster.

2.) Your /etc/lvmrc file may have custom_vg_activation set only activate certain VGs.