Is it safe to run mkboot and lvlnboot commands after physical vol is added to active volume group?

[Jack C. Mahaffey]

I'm in the process of mirroring my system disk and just added another physical volume to the volume group. Physical volume was added with the -fB option and vgextend was used to add the physical volume to the volume group.

Am I still ok for running the mkboot and lvlnboot commands now that the physical volume has been added to an active volume group? I'm a little nervous about making the change to the new volume group after its already part of an existing volume group.

[Victor BERRIDGE]

Hi,
Yes its safe if you know what you are doing...
And you have no choice if you are willing to mirror vg00...

Good luck

All the best
Victor

[Fred Myers]

Yes actually you should run the mkboot command first (remember to fixt the Auto File)

mkboot -a "hpux -lq (;0)/stand/vmunix" BOOTDISK

then make your mirrors with lv extend

then do you lvlnboot's.

[Victor BERRIDGE]

Hi,
I just remembered of a thread you would be interested in:
http://forums.itrc.hp.com/cm/QuestionAnswer/1,1150,0xcf860559ff7cd4118fef0090279cd0f9,00.html

all the best

Victor

[Fred Myers]

try this script you have to set 2 variables, because I am to lazy to have them passed.

[gil paz_2 · Accepted solution]

Hi
To be in the save side my recommendation is.
Before you run the pvcreate and extend the disk.
1.Check if you do not use the disk.
Let say the disk path is /dev/rdsk/c0t5d0.
strings /etc/lvmtab |grep c0t5d0
2.pvcreate -B /dev/rdsk/c0t5d0 (be careful with the -f option).
3.mkboot /dev/rsk/c0t5d0
4.mkboot -a "hpux -lq (10/0.5.0;0)/stand/vmunix" /dev/rdsk/c0t5d0

You need to use all the path (10/0.5.0) if you run hpux-11.

5.vgextend /dev/vg00 /dev/dsk/c0t5d0
6.lvlnboot -b /dev/vg00/lvol1
lvlnboot -r /dev/vg00/lvol3
lvlnboot -s /dev/vg00/lvol2
lvlnboot -d /dev/vg00/lvol2
lvlnboot -R
lvlnboot -v
It need look like this:
Boot Definitions for Volume Group /dev/vg00:
Physical Volumes belonging in Root Volume Group:
/dev/dsk/c0t6d0 (10/0.6.0) -- Boot Disk
/dev/dsk/c0t5d0 (10/0.5.0) -- Boot Disk
Boot: lvol1 on: /dev/dsk/c0t6d0
/dev/dsk/c0t5d0
Root: lvol3 on: /dev/dsk/c0t6d0
/dev/dsk/c0t5d0
Swap: lvol2 on: /dev/dsk/c0t6d0
/dev/dsk/c0t5d0
Dump: lvol2 on: /dev/dsk/c0t6d0
/dev/dsk/c0t5d0
Make the mirroring:
lvextend -m 1 /dev/vg00/lvol1 /dev/dsk/c0t5d0
lvextend -m 1 /dev/vg00/lvol2 /dev/dsk/c0t5d0
lvextend -m 1 /dev/vg00/lvol3 /dev/dsk/c0t5d0
lvextend -m 1 /dev/vg00/lvol4 /dev/dsk/c0t5d0
lvextend -m 1 /dev/vg00/lvol5 /dev/dsk/c0t5d0
lvextend -m 1 /dev/vg00/lvol6 /dev/dsk/c0t5d0
lvextend -m 1 /dev/vg00/lvol7 /dev/dsk/c0t5d0
lvextend -m 1 /dev/vg00/lvol8 /dev/dsk/c0t5d0
7.setboot -a 10/0.5.0
Now you ready to check if you can boot from the alternate disk.

Remark:You can use the scripts to check if you have any stale.

[Jack C. Mahaffey]

The syntax for adding hpux included ";0" as part of the path, as in:
mkboot -a "hpux -lq (10/0.5.0;0)/stand/vmunix" /dev/rdsk/c0t5d0
Since this is not the primary boot disk, should it be used?

jack...