- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: vgdisplay -v unsuccessful
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
тАО02-03-2004 09:50 AM
тАО02-03-2004 09:50 AM
B5725AA B.4.4.30 HP-UX Installation Utilities (Ignite-UX)
IUX-Recovery B.4.4.30 Ignite-UX network recovery tool subset
Ignite-UX-11-00 B.4.4.30 HP-UX Installation Utilities for Installing 11.00 Systems
Ignite-UX-11-11 B.4.4.30 HP-UX Installation Utilities for Installing 11.11 Systems
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-03-2004 10:58 AM
тАО02-03-2004 10:58 AM
SolutionI'm attaching a script that checks for that and can let you figure out if its lvm or a bad disk.
Later version of ignite require all disks in lvmtab to be working.
SEP
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-03-2004 11:02 AM
тАО02-03-2004 11:02 AM
Re: vgdisplay -v unsuccessful
* Backing Up Volume Group /dev/vglock
* /usr/sbin/vgcfgbackup /dev/vglock
vgcfgbackup: Warning: couldn't query physical volume "/dev/dsk/c51t0d1":
It appears that you have a bad disk or LUN or do not have access to it. The error is telling you that it can't query the LUN at /dev/dsk/c51t0d1. You need to figure out what the problem there is.
This could also be bad news because this appears to be your MC/SG lock disk in the vglock VG. If it is and you have a problem with one of the machines in the cluster, you could have real problems like "split brain syndrome" where each machine tries to form the cluster.
Take care of the disk/LUN problem and your make_tape_recovery problem will probably go away.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-03-2004 11:27 AM
тАО02-03-2004 11:27 AM
Re: vgdisplay -v unsuccessful
I ran your script but it indicating that my SG lock disk is not responding. That should be true because right now the primary node has it activated. The recovery log does give Warning messages about the /dev/vglock VG but it continues until ignite creates the Archive File List. Then it just hangs with a NOTE: vgdisplay -v unsuccessful. Thanks.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-03-2004 11:36 AM
тАО02-03-2004 11:36 AM
Re: vgdisplay -v unsuccessful
my mistake. The lock disk is not activated in either node. Neither node can do a vgdisplay on the VG or a pvdisplay on the LUN. I did get a successful ignite on the primary node on the same night.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-03-2004 11:38 AM
тАО02-03-2004 11:38 AM
Re: vgdisplay -v unsuccessful
Same reply as above. The LUN is inactive on both node but the primary node was able to get a successful ignite image. Thanks.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-03-2004 01:32 PM
тАО02-03-2004 01:32 PM
Re: vgdisplay -v unsuccessful
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-03-2004 01:36 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-04-2004 08:31 PM
тАО02-04-2004 08:31 PM
Re: vgdisplay -v unsuccessful
That care that you are in a cluster environment.
If you vglock is part of a Serviceguard,
you surely put it under cluster control,
with command "vgchange -c y vglock".
The only way to activate a vg in a cluster
is to activate it with exclusive option to discard data corruption.
You could perform this with the command
"vgchange -a e y vglock".
If the command works, you will need to run this command before launching ignite backup.
and then deactivate it with command
"vgchange -a n vgsglock" and performeing vgdisplay
For your information SG doesn't use public part of vg for lock mechanisn, put the private structure part.
Hope this help!
--Vincent