topic Re: Vgextend failed in Operating System - HP-UX

Vgextend failed

RASE_1 — Tue, 01 Sep 2009 06:28:44 GMT

HP UX 11.23 running on Itanium with 2 Hd, the second Hd wasn't used. Due to a crash disk, the main disk has been replaced.
We installed the Mirror software successfully, and then try to configure the boot mirror.
Here is the sequence we used:

pvcreate -f -B /dev/rdsk/cxtydz: OK
mkboot -l /dev/rdsk/cxtydz: OK
mkboot -a "hpux -lq ($HW_PATH;0)/stand/vmunix" dev/rdsk/cxtydz: OK
vgextend vg00 /dev/dsk/cxtydz : KO with following error message:
vgextend: Warning: Max_PE_per_PV for the volume group (4328) too small for this
PV (4375).
Using only 4328 PEs from this physical volume.
vgextend: Couldn't install the physical volume "/dev/dsk/c2t1d0".
Unable to read the physical volume.

Other information:

#ioscan
0/1/1/0.0.0 disk HP 73.4GST373454LC
0/1/1/0.1.0 disk HP 73.4GMAS3735NC

# dd if=/dev/dsk/c2t1d0 of=/dev/null bs=1024k
70007+1 records in
70007+1 records out

Hard disks aren't the same model, could be the raison of this problem ?

Regards,

Re: Vgextend failed

Sagar Sirdesai — Tue, 01 Sep 2009 06:44:00 GMT

Please send us vgdisplay -v vg00 output

Re: Vgextend failed

Lijeesh N G_1 — Tue, 01 Sep 2009 06:50:26 GMT

Hi,

==>HP UX 11.23 running on **Itanium** with 2 Hd, the second Hd wasn't used. Due to a crash disk, the main disk has been replaced.
We installed the Mirror software successfully, and then try to configure the boot mirror.
Here is the sequence we used:

==>1st up all, Mirroring in Itanium servers has different procudure, its not same like PA-RISC.
Confirm what is the model of your system, #uname -a

==>2nd check and verify the disk to mirror.
#ioscan -fnC disk
#diskinfo /dev/rdsk/cxtydz
#dd if=/dev/rdsk/cxtydz of=/dev/null bs=1024 count=50
Check through SAM as well,
#sam > Go to Disks and File system>

==>Pls provide the following outputs,
#ioscan -fnC disk
#diskinfo /dev/rdsk/cxtydz
#dd if=/dev/rdsk/cxtydz of=/dev/null bs=1024 count=50
#strings /etc/lvmtab
#vgdisplay -v vg00

Regards,
LIJEESH N G

Regards,
LIJEESH N G

Re: Vgextend failed

Fabio Ettore — Tue, 01 Sep 2009 07:25:25 GMT

Hi,

the problem is about the Max PE per PV setting of the volume group.
The first disk that you added when creating the volume group is smaller than the disk that you're trying to add now.

First disk: number of PEs ---> 4328
Disk adding now: number of PEs ---> 4375

To change this setting you have to use vgmodify with -e option, see man vgmodify and the following link:

http://docs.hp.com/en/5992-4589/ch03s04.html

The link refers to HP-UX 11.31 but the concept is exactly the same.

HTH.

Best regards,
Fabio

Re: Vgextend failed

Turgay Cavdar — Tue, 01 Sep 2009 07:27:30 GMT

If this is itanium then your mirroring procedure is wrong...

How do you mirror vg00 on Itanium systems that are running B.11.23?
RESOLUTION
NOTE: There are differences in procedure between 11.22 and 11.23.
Please refer to KBRC00011156 for B.11.22.

1. From HPUX, use vgdisplay to identify the disk that is in vg00. Use
ioscan to find the spare disk.

# vgdisplay -v --> vg00 is on /dev/dsk/c2t1d0s2 in this example
# ioscan -efunC disk --> Let's assume c3t2d0 for this example

2. Create the system, OS, and service partitions.

# cat > /tmp/partitionfile
3
EFI 500MB
HPUX 100%
HPSP 400MB
# idisk -wf /tmp/partitionfile /dev/rdsk/c3t2d0
idisk version: 1.31
********************** WARNING ***********************
If you continue you may destroy all data on this disk.
Do you wish to continue(yes/no)? yes <-- Answer "yes" and not "y"

3. Create device files needed for the new partitions.

# insf -eC disk

4. Verify the partition table.

# idisk /dev/rdsk/c3t2d0

5. Verify that the device files were created properly.

# ioscan -efnC disk --> c3t2d0 is 0/1/1/1.2.0

6. Initialize the efi partition for use.

# efi_fsinit -d /dev/rdsk/c3t2d0s1

7. Populate the /efi/hpux/ directory in the new EFI system partition.

# mkboot -e -l /dev/rdsk/c3t2d0

8. Change the auto file for the mirror to boot without quorum.
NOTE: Using "s1"

# echo "boot vmunix -lq" > /tmp/AUTO.lq
# efi_cp -d /dev/rdsk/c3t2d0s1 /tmp/AUTO.lq /EFI/HPUX/AUTO

NOTE: We assume that if we boot from the primary, the mirror is fully
functional and therefore we don't need to override quorum. Your site
might require that both disks override quorum.

9. Verify the contents of the auto file on the primary and the mirror.
NOTE: Using "s1"

# efi_cp -d /dev/rdsk/c2t1d0s1 -u /EFI/HPUX/AUTO /tmp/AUTO.pri
# efi_cp -d /dev/rdsk/c3t2d0s1 -u /EFI/HPUX/AUTO /tmp/AUTO.alt
# cat /tmp/AUTO.pri
# cat /tmp/AUTO.alt

10. Add the new partition to vg00.
NOTE: Using "s2"

# pvcreate -fB /dev/rdsk/c3t2d0s2
# vgextend vg00 /dev/dsk/c3t2d0s2

11. Mirror all logical volumes in vg00.
NOTE: Using "s2"

# lvextend -m 1 /dev/vg00/lvol1 /dev/dsk/c3t2d0s2
# lvextend -m 1 /dev/vg00/lvol2 /dev/dsk/c3t2d0s2
# lvextend -m 1 /dev/vg00/lvol3 /dev/dsk/c3t2d0s2
.
.
.
# lvextend -m 1 /dev/vg00/lvol8 /dev/dsk/c3t2d0s2

12. Add the new disk to /stand/bootconf.
NOTE: Using "s2"

# echo "l /dev/dsk/c3t2d0s2" >> /stand/bootconf

13. Verify that the new disk was added to vg00, and the lv's are in sync.

# vgdisplay -v vg00

14. Verify that the BDRA was updated properly. Take note of the HW paths for
step 15.

# lvlnboot -v

15. Add EFI primary and high availability boot path menu entries.

# setboot -p 0/1/1/0.1.0 <-- Set primary disk
# setboot -h 0/1/1/1.2.0 <-- Set mirror disk
# setboot -b on <-- Set autoboot on

16. Verify that the primary and mirror boot paths are configured properly.

# setboot

17. Test the new mirror by booting off of it.

# shutdown -r -y 0

18. Select "HP-UX HA Alternate Boot" to test the mirror.

EFI Boot Manager ver 1.10 [14.61] Firmware ver 2.21 [4334]
Please select a boot option
HP-UX Primary Boot: 0/1/1/0.1.0
HP-UX HA Alternate Boot: 0/1/1/1.2.0
EFI Shell [Built-in]

20. Verify which disk/kernel you booted from.

# grep "Boot device" /var/adm/syslog/syslog.log
vmunix: Boot device's HP-UX HW path is: 0.1.1.1.2.0

21. Remove temporary files.

# rm /tmp/partitionfile /tmp/AUTO*

Done.

Re: Vgextend failed

Lijeesh N G_1 — Tue, 01 Sep 2009 07:34:08 GMT

Hi,

Here is the procedure for Itanium servers,

Mirroring in Itanium servers
==============================

1) Create partition file
#cat /tmp/partitionfile
>3
>EFI 500MB
>HPUX 100%
>HPSP 400MB
>EOF

2) Create EFI partitions
In this eg. /dev/rdsk/c3t2d0 is disk, you may replace with your disk.

#idisk -wf /tmp/partitionfile dev/rdsk/c3t2d0

3) Create device files needed for the new partitions.
#insf -eC disk

4) Verify with idisk and ioscan command.
#idisk dev/rdsk/c3t2d0
#ioscan -efnC disk

5) Initialize the efi partition for use,
# efi_fsinit -d dev/rdsk/c3t2d0s1

6) Populate the /efi/hpux/ directory in the new EFI system partition.
# mkboot -e -l dev/rdsk/c3t2d0

7) Change the auto file for the mirror to boot without quorum.
NOTE: Using "s1"
# echo "boot vmunix -lq" > /tmp/AUTO.lq
# efi_cp -d /dev/rdsk/c3t2d0s1 /tmp/AUTO.lq /EFI/HPUX/AUTO

NOTE: We assume that if we boot from the primary, the mirror is fully
functional and therefore we don't need to override quorum. Your site
might require that both disks override quorum.

8) Verify the contents of the auto file on the primary and the mirror.
NOTE: Using "s1"

# efi_cp -d /dev/rdsk/c2t1d0s1 -u /EFI/HPUX/AUTO /tmp/AUTO.pri
# efi_cp -d /dev/rdsk/c3t2d0s1 -u /EFI/HPUX/AUTO /tmp/AUTO.alt
# cat /tmp/AUTO.pri
# cat /tmp/AUTO.alt

9) Create PV,
NOTE: Using "s2"
#pvcreate -fB /dev/rdsk/c3t2d0s2

10) Extend vg00
#vgextend vg00 /dev/dsk/c3t2d0s2

11) 11. Mirror all logical volumes in vg00.
NOTE: Using "s2"

# lvextend -m 1 /dev/vg00/lvol1 /dev/dsk/c3t2d0s2
# lvextend -m 1 /dev/vg00/lvol2 /dev/dsk/c3t2d0s2
# lvextend -m 1 /dev/vg00/lvol3 /dev/dsk/c3t2d0s2
# lvextend -m 1 /dev/vg00/lvol4 /dev/dsk/c3t2d0s2
# lvextend -m 1 /dev/vg00/lvol5 /dev/dsk/c3t2d0s2
# lvextend -m 1 /dev/vg00/lvol6 /dev/dsk/c3t2d0s2
# lvextend -m 1 /dev/vg00/lvol7 /dev/dsk/c3t2d0s2
# lvextend -m 1 /dev/vg00/lvol8 /dev/dsk/c3t2d0s2

12) Add the new disk to /stand/bootconf.
NOTE: Using "s2"
# echo "l /dev/dsk/c3t2d0s2" >> /stand/bootconf

13) Verify that the new disk was added to vg00, and the lv's are in sync.
#vgdisplay -v vg00

14) Verify that the BDRA was updated properly.
#lvlnboot -v

15) Update NVRAM for the alternate/high availability boot disk and verify,
#setboot -h
#setboot

16) Test the new mirror by booting from that.

# shutdown -r -y 0

17) Select "HP-UX HA Alternate Boot" to test the mirror.

EFI Boot Manager ver 1.10 [14.61] Firmware ver 2.21 [4334]
Please select a boot option
HP-UX Primary Boot: 0/1/1/0.1.0
HP-UX HA Alternate Boot: 0/1/1/1.2.0
EFI Shell [Built-in]

18) Verify which disk/kernel you booted from.

#grep "Boot device" /var/adm/syslog/syslog.log
vmunix: Boot device's HP-UX HW path is: 0.1.1.1.2.0
or
#dmesg|grep -i boot
Boot device's HP-UX HW path is: 0/1/1/1.2.0

19) Remove temporary files.
# rm /tmp/partitionfile /tmp/AUTO*

Regards,
LIJEESH N G

Re: Vgextend failed

RASE_1 — Tue, 01 Sep 2009 08:19:28 GMT

First of all, thanks.
Points 1 to 7 : OK

Point 8: content of /tmp/AUTO.pri: boot vmunix, content of /tmp/AUTO.alt : boot vmunix -lq

Is it serious ?

Re: Vgextend failed

Turgay Cavdar — Tue, 01 Sep 2009 08:23:19 GMT

Serious? It depends on you actually "boot vmunix -lq" means override quorum, when one disk fails then system boot from the other disk automatically. If you dont set as lq them you manually give this command to boot from other disk.

Re: Vgextend failed

RASE_1 — Tue, 01 Sep 2009 08:26:10 GMT

So it's recommended to add this -lq parameter to the master disk ?

Re: Vgextend failed

Turgay Cavdar — Tue, 01 Sep 2009 08:29:32 GMT

Yes, the prosedure i sent is HP's document.

Re: Vgextend failed

Fabio Ettore — Tue, 01 Sep 2009 09:01:34 GMT

Hi,

nothing about the procedure of mirror which is good and it should help to solve the problem on vgextend.
Anyway don't ignore the message that you got:

vgextend vg00 /dev/dsk/cxtydz : KO with following error message:
vgextend: Warning: Max_PE_per_PV for the volume group (4328) too small for this
PV (4375).
Using only 4328 PEs from this physical volume

So your second disk won't use 47 extents (4375 - 4328) and this will happen on each disk you'll add to the volume group until you don't change Max_PE_per_PV setting by vgnodify as already mentioned in my previous post. By that you have to increase that value to 4375 or something more.

Best regards,
Fabio