unknown LIF files in boot disks.

[Jdamian]

Hi.

One of the boot disk (primary path) contains several LIF files that aren't included in the other boot disk (alternate path).

# lifls -l /dev/dsk/c1t6d0
volume ISL10 data size 7984 directory size 8 99/04/22 03:47:46
filename type start size implement created
===============================================================
ISL -12800 584 240 0 99/04/22 03:47:46
AUTO -12289 824 1 0 02/12/04 15:53:14
HPUX -12928 832 800 0 99/04/22 03:47:47
PAD -12290 1632 1700 0 99/04/22 03:47:47
LABEL BIN 3336 8 0 00/06/15 05:04:39
SSINFO -12286 3344 2 0 04/06/16 09:50:34
# lifls -l /dev/dsk/c2t6d0
volume ISL10 data size 7984 directory size 8 99/10/28 15:23:53
filename type start size implement created
===============================================================
ISL -12800 584 240 0 99/10/28 15:23:53
AUTO -12289 824 1 0 99/10/28 15:23:53
HPUX -12928 832 800 0 99/10/28 15:23:53
PAD -12290 1632 1700 0 99/10/28 15:23:54
LABEL BIN 3336 8 0 03/03/31 12:50:55

Pay attention on file SSINFO whose date/time is past June 30th... (last patch installation).

Is this right ?

I'm checking the headers of boot disks because recently I had to recover a system from an Ignite tape due to the alternate boot disk couldn't boot.

Thanx a lot

[John Palmer · Accepted solution]

Hi,

SSINFO is one of the diagnostic LIF files. It is not required in order to boot the server.

Your disk c2t6d0 has all the required LIF files for normal boot.

It's likely that a patch installation installed SSINFO to your primary boot disk. If I remember correctly, the file /stand/bootconf is used by swinstall in order to identify boot disks. One step in mirroring your boot disk is to update /stand/bootconf to include the new disk. Have you done this?

Regards,
John

[Kent Ostby]

Those are correct to be on there.
AUTO contains your autoboot string.

ISL is the Initial Secondary Loader

HPUX is the boot loader for the kernel

PAD is simply a padding area that keeps some of the other files on the proper boundries.

I'm unsure of what SSINFO does, but it is standard (i.e. if I search my HP database for SSINFO, I see 74 hits and none of them are bad).

Hope that helps,

Kent M. Ostby

[john korterman]

Hi,

there is a bit of an explanation in Document id KBRC00004704 in the tech base, try it:
http://www5.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&docId=200000071239187

regards,
John K.