- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Couldn't activate volume group
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-30-2004 06:52 AM
тАО04-30-2004 06:52 AM
I have a server which runs a MC/SG package. This package mounts several disks from our SAN which are also presented to another server in our cluster where the package can fail over. This set up works fine.
I have connected to the first server where my package runs, a SCSI disk array which I use to mirror the volumes from the SAN. So, if for some reason my SAN becomes unavailable, the mirror on my disk array will keep my apps going. This set up also works fine.
Here is my problem :
If my first server crashes and my package fails over to the cluster's other server which does not have the disk array connected, when the package tries to activate my VGs I get the following error message :
vgchange: Couldn't activate volume group "/dev/vg10":
Quorum not present, or some physical volume(s) are missing.
Is there a way for my package to activate the VGs even though the physical volume used for the mirror is not defined on my second cluster server?
Thanks.
Richard.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-30-2004 07:00 AM
тАО04-30-2004 07:00 AM
Re: Couldn't activate volume group
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-30-2004 07:01 AM
тАО04-30-2004 07:01 AM
SolutionSince you do not the local disks on your second cluster then please try the option -q n which says no quorum. I would however rethink this solution as when the cluster fails back you will have to resynch the disks and this may take a long time.
A better way of doing this would be to ensure that you have a good raid level on your SAN.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-30-2004 07:07 AM
тАО04-30-2004 07:07 AM
Re: Couldn't activate volume group
see man for vgcreate.
vgimport -m /vgxx.map -v /dev/vgdrnfsa
/dev/dsk/cxtxdx /dev/dsk/cxtxdx ......
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-30-2004 07:51 AM
тАО04-30-2004 07:51 AM
Re: Couldn't activate volume group
It did solve my problem although the vgchange man page does not recommend using the -q n option.
Hari,
Yes, I know that it will rebuild the mirror as soon as I transfer the package back. This set up was put in place just in case the SAN gets physically destroyed by fire or any other circumstance. The server on which the disk array is connected is in a different location from the SAN. Since we can't afford 2 SANs, this is the best we can do.
Thanks again to all,
Richard.