mkboot

[Martijn Bos_1]

Hi all,

I'm creating mirrors in vg00

first I do :

# mkboot -l /dev/rdsk/c2t2d0
There appear to be non-boot logical volumes on this device.
Overwriting them could destroy all the data on this device
Should the logical volumes be overwritten [y/n]? y

Then I create the mirrors of all LV's in vg00 with lvextend.

When I arrive at lv04 I get following messages :
Logical volume "/dev/vg00/lvol4" has been successfully extended.
lvlnboot: LIF information corrupt or not present on "/dev/dsk/c2t2d0".
Use the "mkboot" command to initialize the LIF area.
lvlnboot: LIF information corrupt or not present on "/dev/dsk/c2t2d0".
Use the "mkboot" command to initialize the LIF area.

How can I resolv this?


Best Regards

Martijn Bos

[James R. Ferguson]

Hi:

It aoppears that you have skipped the most critical step in establishing a bootable disk -- 'pvcreate -B'.

Here are the apppropriate steps to create a bootable disk:

# pvcreate ???B /dev/rdsk/cXtYdZ
# vgextend /dev/vg00 /dev/dsk/cXtYdZ
# mkboot /dev/rdsk/cXtYdZ
# mkboot ???a "hpux ???lq" /dev/rdsk/cXtYdZ
# for LV in 1 2 3 4 5 6 7 8
> do
> lvextend ???m 1 /dev/vg00/lvol${LV} /dev/dsk/cXtYdZ
> done
# lvlnboot ???v

# mkboot ???a "hpux ???lq" /dev/rdsk/cXtYdZ #...for original volume, too...
# setboot ???a [alternate_path] #???for new mirror...
# lifcp /dev/rdsk/xCtYdZ:AUTO - #???copy to stdout for verification...

Regards!

...JRF...

[Stefan Farrelly]

just run mkboot again but dont use the raw devicefile;

mkboot -l /dev/dsk/c2t2d0

[RolandH]

Do it like this.
To set up a mirrored root config you need to add an additional disk (e.g. c1t6d0) to the root
VG mirror all the LVs and make it bootable.
Initialize the disk and add it to vg00:
# pvcreate [-f] -B /dev/rdsk/c1t6d0
# vgextend vg00 /dev/dsk/c1t6d0
mirror the LVs:
# for i in lvol1 lvol2 ... lvol8 (specify any LV in the VG you like to mirror)
> do lvextend -m 1 /dev/vg00/$i /dev/dsk/c1t6d0
> done

After that
(c#t#d# = c1t6d0 in our example

1. Write LIF header and LIF files (ISL, AUTO, HPUX, LABEL):
# mkboot -l /dev/rdsk/c#t#d#
# lifls ???l /dev/rdsk/c#t#d# (to ckeck it)
2. Write content of AUTO File (may be skipped):
# mkboot -a hpux /dev/rdsk/c#t#d#
# lifcp /dev/rdsk/c#t#d#:AUTO - (to ckeck it)
3. Install ODE files (may be skipped):
# cd /usr/sbin/diag/lif
# getconf HW_CPU_SUPP_BITS (the result is either 32, 32/64 or 64)
# mkboot -b updatediaglif -p ISL -p AUTO -p HPUX -p LABEL
/dev/rdsk/c#t#d# (if 32 or 32/64)
# mkboot -b updatediaglif2 -p ISL -p AUTO -p HPUX -p LABEL
/dev/rdsk/c#t#d# (if 64)
(the -p option preserves the specified file so that it is not overwritten)
Refer to section Offline Diagnostics (ODE) if you have problems with this.
4. Write content of LABEL file,i.e set root, boot, swap and dump device:
NOTE: This step can be omitted if you replace a failed mirror disk. Then this information has already
been restored by vgcfgrestore. To be sure to have the latest information on the disk just do the
following steps.
# lvlnboot -r /dev//lvol3 (lvol1 for <= UX 10.10)
# lvlnboot -b /dev//lvol1 (not for <= UX 10.10)
# lvlnboot -s /dev//lvol2
# lvlnboot -d /dev//lvol2
# lvlnboot ???v (to ckeck it)


And then

specify mirror disk as alternate boot path:
# setboot ???a


HTH
Roland

[Martijn Bos_1]

James,

Thanks for your comments.

Indeed I didn't created the PV with the -B option.

So I think I wil start all over.

Stefan,

In the man-pages I see that all examples are done on the raw device.

Are you sure it will work on the block device?

Best Regards

Martijn Bos

[Paulo A G Fessel]

Martin, take a look at the following document:

http://www.software.hp.com/products/IUX/docs/diskmirror.pdf

It talks about implementing mirroring with IUX and it has a section describing exactly what is neccesary to have a mirrored vg00.

HTH
Paulo Fessel

[Stefan Farrelly]

Yes, to be safe recreate all the mirrors again with all steps.

The man page for mkboot on 11i gives as the first example; mkboot -l /dev/dsk/c0t5d0
ie. not a raw devicefile. I dont think it really matters for mkboot or else this manpage is in error ?

[RolandH]

Hey Martin,

I have a litte but important typo in my mirror procedure.

type
# mkboot ???a "hpux ???lq" /dev/rdsk/cXtYdZ #...for original volume, too...

instead of

# mkboot -a hpux /dev/rdsk/c#t#d#


This must be done if one of the disk fails.
Because you can not boot from the mirror disk/original, because you are then in qourom state. Thsi means less or equal of the half disks, which belongs to the vg are not available. This prevents the system to boot correct. The "-lq" switch prevents this behvior.

HTH
Roland

[James R. Ferguson]

Hi:

According to the 11i man pages, either a character or block device may be specified with 'mkboot' (although I have always used the character device). These man pages note, "Install the boot programs on the given device special file. The specified device can identify either a character-special or block-special device. However, mkboot requires that both the block and character device special files be present."

Regardless, since you failed to initially 'pvcreate' your disk as bootable '-B' which reserves space in the LVM header for the LIF information, you most definitely should start over.

Regards!

...JRF...

[GK_5]

pvcreate -B /dev/rdsk/c2t2d0
vgextend /dev/vg00 /dev/dsk/c2t2d0
mkboot /dev/rdsk/c2t2d0
mkboot -a "hpux -lq" /dev/dsk/c2t2d0
mkboot -a "hpux -lq" /dev/dsk/cxtyd0 ( other disk )
Then do "lvextend -m 1"on each volume.

[TelstraMidrange]

Hi Team,

Just want to know the difference between below . Just giving hpux is wrong ? will that corrupt the boot paths / boot settings

mkboot -a "hpux" /dev/rdsk/c12t0d4
mkboot -a "hpux" /dev/rdsk/c12t0d3

mkboot -a "hpux /stand/vpmon -a"  /dev/rdsk/c12t0d4
mkboot -a "hpux /stand/vpmon -a" /dev/rdsk/c12t0d3

Thanks and Regards,

HPUX Admin

[Torsten.]

mkboot -a "hpux" /dev/rdsk/c12t0d4
mkboot -a "hpux" /dev/rdsk/c12t0d3

This is making a boot entry to start the HPUX kernel.

mkboot -a "hpux /stand/vpmon -a"  /dev/rdsk/c12t0d4
mkboot -a "hpux /stand/vpmon -a" /dev/rdsk/c12t0d3

This is making a boot entry to start the VPMON (vPARS) on the host system and start all virtual machines automatically.