Bad LIF file

[Richard Boutot]

I was having a power failed problem but we replaced the power supply. When I do a SEA I can see all my SCSI drives. When I try to do a boot off the pri or alt path, I get Bad LIF. What is that and what can I do to fix it.

[Robert-Jan Goossens]

Hi Richard,

Try to open next doc, you will need a registered support agreements to open the doc.

http://www11.itrc.hp.com/service/cki/docDisplay.do?docLocale=en&docId=emr_na-c01003420-4

Title: How do I fix the boot message IPL error bad LIF magic at 11.X?
Document ID: emr_na-c01003420-4

Regards,
Robert-Jan

[Dan Copeland]

Boot through a recovery cd or tape and run the recovery shell to retrive the bootlif.

[Ron Irving]

Bad LIF usually means bad drive. It's unusual to have both PRI and ALT go bad at the same time(?) Do you have an ignite tape?

Thx

Ron

[Richard Boutot]

I have a make recover tape which I plan to use this morning to go ahead and reload the system. Thanks to all for your quick responses.

[Richard Boutot]

Iâ m running into another error when I try to restore from my make recover tape. â LVM: lost quorm in VG[0] too many PVâ s missing. Install_PV: restore PV0 header, flags=0x0 count=0

VGCREATE: VGCREATE: vg(/dev/vg00) could not be created.

The path does not specify a valid physical volume.

ERROR command â /sbin/vgcreate â A n â e 2169 â l 255 â p 16 â s 4 /dev/vg00/dev/dsk/c0t6d0â fail

Configuration process has incurred an error. Would you like to run a debug to push a shell



I type yes for the debug and the following comes up



Creating logical volume: vg00/lv011 (/stand).

LVCREATE: volume group â /dev/vg00â does not exist in the â /etc/lvmtabâ file

ERROR command /sbin/lvcreate â A n â n lvoll â r n â C y vg00 failed

[DC.]

Richard,
Why you are not trying this steps as i also faced this problem before some time.
Steps.
1). Boot from the installation media with no interaction with ISL.
2). Select [Run Recovery Shell].
3). Disable Network by pressing "N".
4). HP-UX CORE MEDIA SYSTEM RECOVERY MAIN MENU will display the following options.
s. Search for a file
b. Reboot
l. Load a file
r. Recover an unbootable HP-UX system
x. Exit to shell

Here you have to select "r" option to recover system.

5). DEVICE FILE VERIFICATION MENU will display the following options.

INFORMATION to verify:
Device file used for '/'(ROOT) is c2t0d0.
The hardware path to disk is 0/0/2/0.0.0.

Select one of the following:
a. The above information is correct.
b. WRONG!! The device file used for '/'(ROOT) is incorrect.
m. Return to the 'HP-UX Recovery MENU.'
x. Exit to the shell.

Here if the information is correct then press "a".

6). HP-UX Recovery MENU will appear and give the following options.

Use this menu to select the level of recovery desired.

Select one of the following:
a. Mount the root disk and exit to a shell only.
b. Recover the bootlif/os partitions.
c. Replace the kernel on the root file system.
d. Both options: b and c.
v. Read information about LVM recovery (LVM.RECOVER).
m. Return to 'HP-UX Recovery Media Main Menu'.
x. Exit to the shell.

Here, You have to select recovery the boot lif option by selecting "b" option.

7). BOOTLIF PATH VERIFICATION MENU will apear for verification purpose.

Select one of the following:
a. The above information is correct.
b. WRONG!! Prompt the user for a new bootlif path.

m. Return to the 'HP-UX Recovery MENU.'
x. Exit to the shell.
Here select "a" option if the information is correct.

8). BOOT STRING VERIFICATION MENU will apear like this. . .

Select one of the following:
a. The above information is correct.
b. WRONG!! Prompt the user for the system boot string.

m. Return to the 'HP-UX Recovery MENU.'
x. Exit to the shell.

here press "a", if your boot string is "hpux -lm /stand/vmunix".

9). After that you will see the bootlif installation.

10). HP-UX Recovery MENU will apear and select the option to returen the recovery media main menu.
11). After that reboot the server by "reboot" command on recovery shell prompt.
12). After you get the prompt then
# lvlnboot -b /dev/vg00/lvol1
# lvlnboot -s /dev/vg00/lvol2
# lvlnboot -d /dev/vg00/lvol2
# lvlnboot -R /dev/vg00
# mkboot -a "hpux(;0)/stand/vmunix" /dev/rdsk/c0t6d0 #Primary
# mkboot -a "hpux-lq(;0)/stand/vmunix" /dev/rdsk/c0t5d0 #Secondary

Follow these steps might help you to solve the problem.

Regards,
Piyush Mathiya

[Richard Boutot]

Thank you everyone who answered my question. All of your suggestions were kicked around and some were acted upon. I managed to fix the problem using a little of my own "magic" get it....Anyway thanks again everyone.

[Patrick Wallek]

So what "magic" did you do to fix the problem?

If you could elaborate it may help other people to solve a similar problem in the future.

[Richard Boutot]

Well it wasn't really magic. The machine I have has 5 different SCSI devices. I just took the SCSI that held my temp db files and replaced it with my main harddrive. Then ran a make recover.