topic Re: Boot disk query - LIF in Operating System - HP-UX

Boot disk query - LIF

Shouvik Basak — Wed, 01 Jun 2005 06:24:38 GMT

Question 1:
On a server I find that the boot disk on the alternate bootpath has "LABEL" only (I see that with lifls -v /)

To correct the situation I was thinking of the following:

# mkboot -a "hpux -lq" /
# mkboot -b /usr/sbin/diag/lif/updatediaglif2 -p ISL -p AUTO -p HPUX -p PAD -p LABEL /
(64 bit system. The boot disk on primary path has the diagnostics loaded.)
# lvlnboot -R

Please suggest me if my above mentioned steps would solve the problem. I would really appreciate if you would let me know if I am missing something or some other approach is desired.

===============================================
Question 2:
On another server lvlnboot -v output shows that there are 3 "Boot Disks" in /dev/vg00 (total 4 disks - 2 PVGs and mirrored.) On listing the disks with lifls I find that only 2 of the disks have the LIF area.

Why is lvlnboot listing a disk as "Boot Disk" when it does not show a LIF area (lifls on the disk returns: not a LIF volume)?

Would lvlnboot -R solve this ? Or, any thing more is required to fix the issue?

Re: Boot disk query - LIF

Gary L. Paveza, Jr. — Wed, 01 Jun 2005 06:35:33 GMT

First question:

An easy way to get them in sync is the following:

mkboot -b /dev/rdsk/ /dev/rdsk/

This will copy all the boot programs from the first disk to the second disk.

Second question:

My understanding is that you only need a "boot disk" for your primary and alternate boot disks. Any other disk in the volume group does not need this. It was probably created with pvcreate -B to reserve space for the boot programs.

Re: Boot disk query - LIF

RolandH — Wed, 01 Jun 2005 07:41:23 GMT

As you have created the disk with pvcreate I think you have forgett the -B switch.

# pvcreate -fB /dev/rdsk/cXdYtZ

So if it is just a mirror disk, then you should redo the procedure for the mirror.

Roland

Re: Boot disk query - LIF

Kent Ostby — Wed, 01 Jun 2005 08:41:19 GMT

You do need to check to see if it's set up to handle boot files otherwise you'll need to re-mirror it after doing the pvcreate -B.

If you didn't do the pvcreate -B then none of the above will help you out since there wont be space on the physical device that is set aside for boot files.

You may need to:
unmirror each lvol
vgreduce disk out of vg
pvcreate -B disk
add disk to vg
remirror lvols

Best regards,

Kent M. Ostby