low quorum

[Abubakkar]

1.what is mean # mkboot –e –l /dev/rdisk/disk37
2.what is mean# mkboot -a "boot vmunix -lq" /dev/rdisk/disk36
3.what is mean# efi_cp –d /dev/rdisk/disk36_p1 –u /efi/hpux/auto /dev/tty
boot vmunix -lq
4.what is mean # vi /stand/bootconf
1 /dev/disk/disk36_p2
2 /dev/disk/disk37_p2
:wq

[Duncan Edmonstone · Accepted solution]

1.what is mean # mkboot â e â l /dev/rdisk/disk37

This writes the EFI bootup utilities from /usr/lib/efi onto the EFI partition on disk_37 (which would be disk37_p1)

2.what is mean# mkboot -a "boot vmunix -lq" /dev/rdisk/disk36

This writes an auto boot string into the AUTO file in the EFI partition - the "-lq" means still boot if only 50% or less of the disks in the root volume group are available. The default behaviour without the -lq would be to report an error and stop the boot. For boot volume groups with 2 disks it makes sense to set this.


3.what is mean# efi_cp â d /dev/rdisk/disk36_p1 â u /efi/hpux/auto /dev/tty
boot vmunix -lq

This is just checking that what was done for Q2 above has worked correctly by copying the contents of the AUTO file to your terminal screen

4.what is mean # vi /stand/bootconf
1 /dev/disk/disk36_p2
2 /dev/disk/disk37_p2

From the man page for bootconf:

The /stand/bootconf file contains the address and disk layout type of
the system's boot devices or lif volumes. It is used by the Software
Distributor and HP-UX kernel control scripts (fileset OS-Core.KERN-
RUN) to determine how and where to update the initial boot loader.

HTH

Duncan

[Duncan Edmonstone]

oops for Q1 I should have added that the "-l" option on mkboot also writes out the LIF label file to the LIF area on the LVM partition (disk37_p2). The label file tells the HPUX boot loader where to find the offsets for the start of the root, boot, swap and dump filesystems in the LVM partition.

HTH

Duncan