- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Error in VGID
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
Forums
Discussions
Discussions
Discussions
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
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
11-26-2001 10:11 AM
11-26-2001 10:11 AM
Error in VGID
On host A (uname -i: 438563351)
#pvcreate -f /dev/rdsk/c0t9d0
#echo 0x2008?4D|adb /dev/dsk/c0t9d0
2008: 438563351 1006797988 0 0
On host B (uname -i: 431564361)
#pvcreate -f /dev/rdsk/c0t9d0
#vgcreate /dev/vg01 /dev/dsk/c0t9d0
#echo 0x2008?4D|adb /dev/dsk/c0t9d0
2008: 431564361 1006371258 431564361 1006371262
Host A (uname -i: 438563351)
# echo 0x2008?4D|adb /dev/dsk/c0t9d0
2008: 431564361 1006797997 431564361 1006798119
Conclusion:
The last number is the VGID, so someone can tell if adb extract bad information or what ?!! (and it sure, that the same disk).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-26-2001 10:50 AM
11-26-2001 10:50 AM
Re: Error in VGID
I'm not sure it's a VGID, but you can get the same thing is you did this:
echo 0x2008?4X|adb /dev/dsk/c0t9d0
and this:
dd if=/dev/dsk/c0t9d0|od -xc|more
live free or die
harry
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-26-2001 10:57 AM
11-26-2001 10:57 AM
Re: Error in VGID
An easy way to check this is with vgexport -s -p -m mapfile vg01 from system B. The first line wil show you the VGID.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-26-2001 11:04 AM
11-26-2001 11:04 AM
Re: Error in VGID
I was correct about the starting point, but the VGID is, of course, 2 words long. I was confused because you are pulling it out in decimal rather than hex, so the string was longer than I expected. Just for grins, try using dd to pull the string on each system:
dd if=/dev/rdsk/cxtxdx bs=1024 skip=8 count=9 | dd bs=8 skip=2 count=1 | od -a|head -1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-26-2001 11:12 AM
11-26-2001 11:12 AM
Re: Error in VGID
# dd if=/dev/rdsk/c0d0s2 bs=1k skip=8 count=1 of=/tmp/xxx
This will let you seet the PVRA physical volume reserve area on the disk
# xd -c /tmp/xxx
0000000 L V M R E C 0 1 + ab G 15 . 91 06 E
0000010 + ab G 15 . 91 06 J \0 14 2 13 \0 \0 \0
\00000020 \0 \0 02 0 \0 \0 \b ` \0 \0 01 06 \0 \0 \0
0000030 \0 \0 \b ` \0 \0 \t x \0 \0 \0 \b \0 \0 \t p
0000040 \0 \0 \n 88 \0 14 \0 \0 \0 0b ` \0 \0 \0 16
0000050 \0 \0 10 \0 \0 \0 06 b3 \0 14 + ` \0 \0 \0 a1
0000060 \0 \0 \0 \0 \0 \0 \0 10 \0 \0 \0 80 \0 \0 \0
020000070 \0 \0 \0 80 \0 \0 \0 88 \0 \0 \0 06 \0 \0 \0
0000080 \0 \0 \0 8a \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0
0000090 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \03.
# xd /tmp/xxx
0000000 4c56 4d52 4543 3031 2bab 4715 2e91 0645
" L V M R E C 0 1"
0000010 2bab 4715 2e91 064a 0014 3213 0000 0000
--------- last physical sector number. (1323539. physical sector = 1k)
0000020 0000 0230 0000 0860 0000 0106 0000 000a
0000030 0000 0860 0000 0978 0000 0008 0000 0970
0000040 0000 0a88 0014 2000 0000 0b60 0000 0016
0000050 0000 1000 0000 06b3 0014 2b60 0000 00a1
0000060 0000 0000 0000 0010 0000 0080 0000 0002
0000070 0000 0080 0000 0088 0000 0006 0000 0082
0000080 0000 008a 0000 0000 0000 0000 0000 0000
0000090 0000 0000 0000 0000 0000 0000 0000 0000
Tony
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-26-2001 11:24 AM
11-26-2001 11:24 AM
Re: Error in VGID
The hexadecimal VGID can be found as:
echo 0x2010?2X | adb $BDEV | expand | tr -d " " | sed "s/2010://"
...and the PVID as:
echo 0x2008?2X | adb $BDEV | expand | tr -d " " | sed "s/2008://"
If the VGID's truly differ, by any chance have you done a 'vgchgid'?
Regards!
...JRF...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-26-2001 11:46 AM
11-26-2001 11:46 AM
Re: Error in VGID
Try exporting everything and then import
the volume groups. Do not do pvcreate once you are done with the volume group creation. It will wipe off the VGID.
-Sri
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-26-2001 12:21 PM
11-26-2001 12:21 PM
Re: Error in VGID
It's really a problem in the kernel. adb doesn't repport the good think..