What really needs to be in the LIFS area?

[Geoff Wild]

I have this:

# lifls /dev/dsk/c1t6d0
ODE MAPFILE SYSLIB CONFIGDATA SLMOD2
SLDEV2 SLDRV2 SLSCSI2 MAPPER2 IOTEST2
PERFVER2 PVCU SSINFO HPUX ISL
AUTO LABEL

# lifls /dev/dsk/c2t6d0
ISL AUTO HPUX PAD LABEL

Both disks are bootable - tried, tested and true.

# lvlnboot -v /dev/vg00
Boot Definitions for Volume Group /dev/vg00:
Physical Volumes belonging in Root Volume Group:
/dev/dsk/c1t6d0 (0/0/2/0.6.0) -- Boot Disk
/dev/dsk/c2t6d0 (0/0/2/1.6.0) -- Boot Disk
Boot: lvol1 on: /dev/dsk/c1t6d0
/dev/dsk/c2t6d0
Root: lvol3 on: /dev/dsk/c1t6d0
/dev/dsk/c2t6d0
Swap: lvol2 on: /dev/dsk/c1t6d0
/dev/dsk/c2t6d0
Dump: lvol2 on: /dev/dsk/c1t6d0, 0

# setboot -v
Primary bootpath : 0/0/2/0.6.0
Alternate bootpath : 0/0/2/1.6.0

Autoboot is ON (enabled)
Autosearch is ON (enabled)

TEST CURRENT SUPPORTED DEFAULT NEXT BOOT
---- ------- --------- ------- ---------
all on yes on on
SELFTESTS on yes on on
early_cpu on yes on on
late_cpu on yes on on
FASTBOOT on yes on on
full_memory on yes on on
PDH on yes on on
CEC on yes on on

# cat /stand/bootconf
l /dev/dsk/c1t6d0
l /dev/dsk/c2t6d0


Ran System Health Check:

The LIFS area on LVM mirrored boot disks is not identical.

Boot programs are stored in the boot area in Logical Interchange Format (LIF), which is similar to a file system. For a device to be bootable, the LIF volume on that device must contain at least the ISL (the initial system loader) and HPUX (the HP-UX bootstrap utility) LIF files.
When an LVM mirrored boot disk is created, mkboot is used to install the appropriate LIF files on the mirror (alternate) disk.

This rule indicates that the LIF contents on the primary and alternate boot disks are not identical. This should be investigated further.

Should I make them the same?
If yes, which one is "more" correct?
Do I really need "IOTEST2"? etc...

Rgds...Geoff

[RAC_1]

Geof,

My understanding is that ODE and related stuff is required for offline diagnostics. Does not harm to have them there. So that if you have problems with a disk and boot from recovery CD and want to do some diagnostics, it will be helpful.

With just hpux, pad, lable and others it is just fine. But will not be able to Offline diagnostics.

Hope this helps. Dont know much details about ODE and how that is done.

Anil

[Helen French]

The difference is that the Offline Diag are loaded onto the boot disk from the Diagnostic media when the LIF-LOAD Product is installed. Since the LIF section is not mirrored, this update wont be available on the mirror disk. To make it same:

# cd /usr/sbin/diag/lif

# mkboot -b updatediaglif2 -i ODE -i MAPFILE -i SYSLIB -i CONFIGDATA -i SLMOD -i SLDEV -i SLDRIVERS -i MAPPER -i IOTEST -i PERFVER -i PVCU -i SSINFO -p ISL -p
AUTO -p HPUX -p LABEL /dev/rdsk/cXtXdX

Assuming you are using a 64 bit OS (11.0)

[Sundar_7]

Hi Geoff,

ODE MAPFILE SYSLIB CONFIGDATA SLMOD2
SLDEV2 SLDRV2 SLSCSI2 MAPPER2 IOTEST2
PERFVER2 PVCU SSINFO = these are the ODE LIF volumes that can be used for offline diagnostics.

They need not be present in the LIF volume but if they are present, you can use to perform tests from the ISL when the system has not booted yet.

these LIF files are available from the LIF volumes /usr/sbin/diag/lif/updatediaglif and /usr/sbin/diag/lif/updatediaglif2

On a nut-shell, you dont have to copy ODE lif files to the boot disk. But if you would like to remove that warning from the health check script, then copy them using mkboot using the LIF volumes mentioned above

- Sundar

[RAC_1]

You would need the following command for copying ODE programs to lif area.

mkboot -b /usr/sbin/diag/lif/updatediaglif -p ISL -p HPUX -p AUTO -p LABEL -p PAD
/dev/rdsk/c0t8d0

You need to have STM installed for this.

Anil

[Geoff Wild]

DANGER...DANGER...Will Robinson...

mkboot -b /usr/sbin/diag/lif/updatediaglif2 -i ODE -i MAPFILE -i SYSLIB -i CONFIGDATA -i SLMOD -i SLDEV -i SLDRIVERS -i MAPPER -i IOTEST -i PERFVER -i AUTO -p HPUX -p LABEL /dev/rdsk/c2t6d0
mkboot: ISL will be preserved on target device
mkboot: HPUX will be preserved on target device
Included file SLMOD not found


# lifls /dev/dsk/c2t6d0
ISL AUTO HPUX PAD LABEL


Rgds...Geoff

[Helen French · Accepted solution]

Again, replace SLMOD with SLMOD2 (and whatever appears on your primary boot disk) on the mkboot command. It should be the same parameters like SLDEV2, IOTEST2 etc.

[Steven E. Protter]

All I know is that this process works.

pvcreate -B /dev/rdsk/c1t0d0 #use real disk

mkboot -l /dev/rdsk/c1t0d0
mkboot -a "hpux -lq (;0)/stand/vmunix" /dev/rdsk/c1t0d0 # use real disk


# mkboot -b /usr/sbin/diag/lif/updatediaglif -p ISL -p AUTO -p HPUX -p PAD -p LABEL /dev/rdsk/c?t?d?

If you are running 64-bit OS:

# mkboot -b /usr/sbin/diag/lif/updatediaglif2 -p ISL -p AUTO -p HPUX -p PAD -p LABEL /dev/rdsk/c?t?d?


vgextend /dev/vg00 /dev/dsk/c1t0d0 # same thing
lvextend -m 1 /dev/vg00/lvol1 /dev/dsk/c1t0d0

# real disk. repeat for other lvols

lvlnboot -r /dev/vg00/lvol3 # root fs /
lvlnboot -s /dev/vg00/lvol2 #swap
lvlnboot -d /dev/vg00/lvol2 #swap/dump
lvlnboot -b /dev/vg00/lvol1
lvlnboot -R
lvlnboot -v
setboot
setboot -a 52.1.0 # second disk

I want copies of everything on both disks.

SEP

[Geoff Wild]

Thanks for all the answers - decided to make the LIF on alternate disk the same as primary disk.

mkboot -b /usr/sbin/diag/lif/updatediaglif2 -i ODE -i MAPFILE -i SYSLIB -i CONFIGDATA -i SLMOD2 -i SLDEV2 -i SLDRV2 -i SLSCSI2 -i MAPPER2 -i IOTEST2 -i PERFVER2 -i PVCU -i SSINFO -p ISL -p AUTO -p HPUX -p LABEL /dev/rdsk/c2t6d0

Rgds...Geoff