Vg00 mirror procedure fails at vgextend.

[Juan Gonzalez_2]

I am mirroring the root volume group on a new Itanium server and have done
I have create a partition file called partitionfile with
2
EFI 100MB
HPUX 100%

Then I did a idisk -wf /partitionfile /dev/rdsk/c2t1d0

Then I did insf -e -C disk

Then mkboot -e -l /dev/rdsk/c2t1d0s1

Then I did efi_ls -d /dev/rdsk/c2t1d0s1 to verify that the files from /usr/lib/efi directory where copied.

Then I did lifls -l /dev/rdsk/c2t1d0s2 to verify that the LIF colume was populated with the ISL, AUTO, HPUX,LABEL information.

Then did mkboot -a "boot vmunix" /dev/dsk/c2t1d0

Then I verified with efi_cp -d command.
Then I did pvcreate -f -B /dev/rdsk/c2t1d0s2
Everything look good until the vgextend part
I did vgextend -f /dev/vg00 /dev/dsk/c2t1d0s2
and got the error below:
vgextend: Physical Volume "/dev/dsk/c2t1d0s2" contains no LVM information

I can not figure out what went wrong when everything else before it work successfully without any errors. I have try the mirrior vg00 from the begin with idisk coomand and keep getting this error. This mirror did have veritas volume before but with the pvcreate that should have over written the disk.

[Pupil_1]

Your command mkboot -e -l /dev/rdsk/c2t1d0s1

Should be

mkboot -e -l /dev/dsk/c2t1d0

From mkboot man page
Install EFI utilities to the EFI partition on an Itanium-based system, treating it as an LVM or VxVM disk:
mkboot -e -l /dev/dsk/c3t1d0

[Juan Gonzalez_2]

Pupil I did do a mkboot -e -l /dev/rdsk/c2t1d0
I just mistyped it here.

[Pupil_1]

what's the o/p of
idisk -p /dev/rdsk/c2t1d0

[Juan Gonzalez_2]

Here it is Pupil
#idisk -p /dev/rdsk/c2t1d0
idisk version: 1.31

EFI Primary Header:
Signature = EFI PART
Revision = 0x10000
HeaderSize = 0x5c
HeaderCRC32 = 0x2126ca7c
MyLbaLo = 0x1
AlternateLbaLo = 0x1117732f
FirstUsableLbaLo = 0x22
LastUsableLbaLo = 0x1117730c
Disk GUID = 7b3ee7ec-e4f4-11dc-8001-d6217b60e588
PartitionEntryLbaLo = 0x2
NumberOfPartitionEntries = 0xc
SizeOfPartitionEntry = 0x80
PartitionEntryArrayCRC32 = 0x98ecbfb9

Primary Partition Table (in 512 byte blocks):
Partition 1 (EFI):
Partition Type GUID = c12a7328-f81f-11d2-ba4b-00a0c93ec93b
Unique Partition GUID = 7b3eea76-e4f4-11dc-8002-d6217b60e588
Starting Lba = 0x22
Ending Lba = 0x32021
Partition 2 (HP-UX):
Partition Type GUID = 75894c1e-3aeb-11d3-b7c1-7b03a0000000
Unique Partition GUID = 7b3eea94-e4f4-11dc-8003-d6217b60e588
Starting Lba = 0x32022
Ending Lba = 0x1117730b

[Pupil_1]

that shows that the EFI information has been created in the disk.

just curious what would happen if you vgextend without the -f ?

Did you receive any error during the pvcreate?
Cheers

[Juan Gonzalez_2]

Pupil
No error during pvcreate see below.
#pvcreate -f -B /dev/rdsk/c2t1d0s2
Physical volume "/dev/rdsk/c2t1d0s2" has been successfully created.

The vgextend without the -f gives the same error message see below.
#vgextend /dev/vg00 /dev/dsk/c2t1d0s2
vgextend: Physical Volume "/dev/dsk/c2t1d0s2" contains no LVM information

By the way the server is running HPUX 11.23

[Pupil_1]

I did this on my test node and worked.

what does diskinfo on dev/rdsk/c2t1d0s2 and dev/rdsk/c2t1d0 report?