Operating System - HP-UX
1832274 Members
1960 Online
110041 Solutions
New Discussion

Re: Ignite error vgdisplay unsuccessful

 
kholikt
Super Advisor

Ignite error vgdisplay unsuccessful

I am running make_recovery with -AvC option for one of the MC/SG cluster node. This node is not the active one, I get the following fatal error which actually complain about those in-activated VG

Option -A specified. Entire Core Volume Group/disk will be backed up.
NOTE: vgdisplay -v unsuccessful
NOTE: vgdisplay -v unsuccessful
NOTE: vgdisplay -v unsuccessful
NOTE: vgdisplay -v unsuccessful
ax=120: No such file or directory
make_recovery(214): make_recovery(1M) encountered a fatal error.
make_recovery(216): Please fix errors and re-try.
Cleanup


Is there any way to get around with this problem.
abc
6 REPLIES 6
Rajeev  Shukla
Honored Contributor

Re: Ignite error vgdisplay unsuccessful

Hi,
I am soure its not vgdisplay problem. Coz the vg's are not activated so its just gives a Note saying vgdisplay was unsuccessful.
Look at the logs in /var/opt/ignite/logs
It think you need to check the /etc/fstab and /etc/mnttab which are reporting something wrong.
It is actually failing at statvfs() function which i assume is to do with the filesystem. Either a filesystem is defined in /etc/mnttab or /etc/fstab which no longer exists.
Fix that and try make_recovery again. Also i presume you are aware of the patches required of a version of Ignite-UX. So what version are you using if possible upgrade the Ignite-UX to a lates version from HP site.

Cheers
Rajeev
T G Manikandan
Honored Contributor

Re: Ignite error vgdisplay unsuccessful

For what all VG's you are running ignite.

Can you just do a

vgdisplay -v
on those vg's.

I think those VG's are not activated or the VG's do not exist but their entries remain in the /dev directory.

I would suggest you to use the latest make_tape_recovery instead of make_recovery
and also the latest version of Ignite.

What version of Ignite you are using?

Download the latest version from
http://www.software.hp.com/products/IUX/download.html

Thanks

Manikandan
T G Manikandan
Honored Contributor

Re: Ignite error vgdisplay unsuccessful

For what all VG's you are running ignite.

Can you just do a

vgdisplay -v
on those vg's.

I think those VG's are not activated or the VG's do not exist but their entries remain in the /dev directory.

I would suggest you to use the latest make_tape_recovery instead of make_recovery
and also the latest version of Ignite.

What version of Ignite you are using?

Download the latest version from
http://www.software.hp.com/products/IUX/download.html

Thanks

Manikandan
Ravi_8
Honored Contributor

Re: Ignite error vgdisplay unsuccessful

Hi, Kholikt

This error is due to the inactive node in Mc/SG

activate the node/vg's, do the vgdisplay on all vg's present and i would recommend to use make_tape_recovery instead of make_recovery
never give up
monasingh_1
Trusted Contributor

Re: Ignite error vgdisplay unsuccessful

As long as all your packages are running on nodes and you can do vgdisplay manually for the VGs activated on a node , you do not need to worry at all.

This error will always come on a node which is adaptive node for at least one package because that corresponding vg is not activated in normal situation.

Make_recovery or make_tape recovery will still save your lvmtab, so no worries.

It is good that you are getting errors so that you know that your lvmtab does have the VG for failover packages..

hope this explains...

So
monasingh_1
Trusted Contributor

Re: Ignite error vgdisplay unsuccessful

one more things to add,

I store archive or central server, I can not confirm if make_recovery saves the map file for vgexport, but make_net recovery does export the vg in -p mode and saves the map file.

(which I will agree is not of any use since it does not do this with -s option, besides, you can always get the map file from primary node.)

I will suggest you start using make_net_recovery (use Ignite GUI from central server and create archives from there centrally). It saves lot of time and is lot of ease as well. No more loading unloading of tapes..

hope this explains