- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- HPE 9000 and HPE e3000 Servers
- >
- IPL error: bad LIF image
HPE 9000 and HPE e3000 Servers
1823072
Members
3398
Online
109645
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-19-2006 03:31 AM
тАО05-19-2006 03:31 AM
IPL error: bad LIF image
hello, i am not so familiar with computer jargon so please bear with me if i don't give a clarified explanation of my problem. i tried booting a hp D class 9000 from the primary boot and it gave me the error "IPL error: bad LIF magic". how can i solve the problem
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-19-2006 05:42 AM
тАО05-19-2006 05:42 AM
Re: IPL error: bad LIF image
Hi,
"IPL error: bad LIF magic" indicated the bootlif ( lif header ) is either missing or corrupted.
Try booting from alternate disk using alternate boot option.
To rebuild the LIF header i.e. bootlif, you need to boot using Core OS CD , use recovery option and then select option "rebuild only bootlif".
"IPL error: bad LIF magic" indicated the bootlif ( lif header ) is either missing or corrupted.
Try booting from alternate disk using alternate boot option.
To rebuild the LIF header i.e. bootlif, you need to boot using Core OS CD , use recovery option and then select option "rebuild only bootlif".
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-19-2006 04:20 PM
тАО05-19-2006 04:20 PM
Re: IPL error: bad LIF image
1. Boot from the path of the CORE (INSTALL) media and do not interact with ISL.
bo;
then respond with "no" to interact with ISL
2. Select [ Run a Recovery Shell ]
Use the and/or arrow keys to navigate through the following menus,
and use the key to select an item. If the menu items are not
clear, select the "Help" item for more information.
3. Would you like to start up networking at this time? NO
4. The HP-UX CORE MEDIA RECOVERY MENU will be displayed:
s. Search for a file
b. Reboot
l. Load a file
r. Recover an unbootable HP-UX system
x. Exit to shell
c. Instructions on chrooting to a lvm /(root).
Select one of the above: r <-----
5. The HP-UX Recovery MENU will be displayed:
a. Rebuild the bootlif (ISL, HPUX, and the AUTO file) and install
all files required to boot and recover HP-UX on a target
root file system.
b. Do not rebuild the bootlif but install files required to boot
and recover HP-UX on the root file system.
c. Rebuild only the bootlif.
d. Replace only the kernel on the root file system.
m. Return to 'CORE Media Main Menu'.
x. Exit to the shell.
Use this menu to select the level of recovery desired.
Selection: c <-----
6. The BOOTLIF PATH VERIFICATION MENU will be displayed:
This menu must be used to determine the path to the bootlif (ISL, HPUX
and the AUTO file).
When the information is correct, select 'a'.
INFORMATION to verify:
Path to the bootlif is 10/0.6.0
Select one of the following:
a. The above information is correct.
b. WRONG!! The path to bootlif is incorrect.
m. Return to the 'HP-UX Recovery MENU.'
x. Exit to the shell.
Selection: a <-- If CORRECT
If the address is INCORRECT then select "b" and
follow the instructions to enter the correct
hardware path of the boot disk.
7. The BOOT STRING VERIFICATION MENU will be displayed:
This menu must be used to verify the system's boot string.
When the information is correct, select 'a'.
INFORMATION to verify:
The system's boot string should be:
'hpux -lm (10/0.6.0)/stand/vmunix'
Select one of the following:
a. The above information is correct.
b. WRONG!! Prompt the user for the system's boot string.
m. Return to the 'HP-UX Recovery MENU.'
x. Exit to the shell.
NOTE: For an LVM '/'(ROOT) the '-lm' option MUST be specified
(example: 'hpux -lm (2.3.4)/stand/vmunix' )
Selection: a <-----
8. You will see the bootlif installing.
9. The RECOVERY COMPLETION MENU will be displayed:
Use this menu after the recovery process has installed all requested
files on your system.
Select one of the following:
a. REBOOT the customer's system and continue with recovery.
b. Return to the Support Media's Main Menu.
Selection: a <-----
10. The system will autoboot into maintenance mode. Here you should verify
the BDRA.
11. vgchange -a y /dev/vg00 (activate the root volume group)
12. lvlnboot -v /dev/vg00 --> This should display something like what is shown
below. This sample has a mirror boot disk.
Boot Definitions for Volume Group /dev/vg00:
Physical Volumes belonging in Root Volume Group:
/dev/dsk/c0t6d0 (10/0.6.0) -- Boot Disk <--- Primary boot disk
/dev/dsk/c0t5d0 (10/0.5.0) -- Boot Disk <--- Mirror boot disk
Boot: lvol1 on: /dev/dsk/c0t6d0
Boot: lvol1 on: /dev/dsk/c0t5d0 <---------- Mirror boot disk
Root: lvol3 on: /dev/dsk/c0t6d0
Root: lvol3 on: /dev/dsk/c0t5d0 <---------- Mirror boot disk
Swap: lvol2 on: /dev/dsk/c0t6d0
Swap: lvol2 on: /dev/dsk/c0t5d0 <---------- Mirror boot disk
Dump: lvol2 on: /dev/dsk/c0t6d0, 0
After booting the system the BOOT, ROOT, SWAP,and DUMP volume information
should be correct. If something is missing use the below commands to add.
For example:
BOOT: "lvlnboot -b /dev/vg00/lvol1"
When '/stand' is ONLY on a separate logical volume.
If your not sure check /etc/fstab for a seperate lvol
for /stand.
Otherwise BOOT and ROOT are considered identical.
ROOT: "lvlnboot -r /dev/vg00/lvol3"
Or lvol1 if their is NOT a seperate lvol for /stand
SWAP: "lvlnboot -s /dev/vg00/lvol2"
DUMP: "lvlnboot -d /dev/vg00/lvol2"
13: If you had to make any changes then verify the information is correct with:
"lvlnboot -v /dev/vg00"
14: enter "lvlnboot -R /dev/vg00"
15: Then the boot string should be changed back:
"mkboot -a "hpux (;0)/stand/vmunix" /dev/rdsk/c0t6d0" <-- Primary disk
"mkboot -a "hpux -lq (;0)/stand/vmunix" /dev/rdsk/c0t5d0" <-- Mirror disk
16. Reboot the system
with "reboot"
bo
then respond with "no" to interact with ISL
2. Select [ Run a Recovery Shell ]
Use the
and use the
clear, select the "Help" item for more information.
3. Would you like to start up networking at this time? NO
4. The HP-UX CORE MEDIA RECOVERY MENU will be displayed:
s. Search for a file
b. Reboot
l. Load a file
r. Recover an unbootable HP-UX system
x. Exit to shell
c. Instructions on chrooting to a lvm /(root).
Select one of the above: r <-----
5. The HP-UX Recovery MENU will be displayed:
a. Rebuild the bootlif (ISL, HPUX, and the AUTO file) and install
all files required to boot and recover HP-UX on a target
root file system.
b. Do not rebuild the bootlif but install files required to boot
and recover HP-UX on the root file system.
c. Rebuild only the bootlif.
d. Replace only the kernel on the root file system.
m. Return to 'CORE Media Main Menu'.
x. Exit to the shell.
Use this menu to select the level of recovery desired.
Selection: c <-----
6. The BOOTLIF PATH VERIFICATION MENU will be displayed:
This menu must be used to determine the path to the bootlif (ISL, HPUX
and the AUTO file).
When the information is correct, select 'a'.
INFORMATION to verify:
Path to the bootlif is 10/0.6.0
Select one of the following:
a. The above information is correct.
b. WRONG!! The path to bootlif is incorrect.
m. Return to the 'HP-UX Recovery MENU.'
x. Exit to the shell.
Selection: a <-- If CORRECT
If the address is INCORRECT then select "b" and
follow the instructions to enter the correct
hardware path of the boot disk.
7. The BOOT STRING VERIFICATION MENU will be displayed:
This menu must be used to verify the system's boot string.
When the information is correct, select 'a'.
INFORMATION to verify:
The system's boot string should be:
'hpux -lm (10/0.6.0)/stand/vmunix'
Select one of the following:
a. The above information is correct.
b. WRONG!! Prompt the user for the system's boot string.
m. Return to the 'HP-UX Recovery MENU.'
x. Exit to the shell.
NOTE: For an LVM '/'(ROOT) the '-lm' option MUST be specified
(example: 'hpux -lm (2.3.4)/stand/vmunix' )
Selection: a <-----
8. You will see the bootlif installing.
9. The RECOVERY COMPLETION MENU will be displayed:
Use this menu after the recovery process has installed all requested
files on your system.
Select one of the following:
a. REBOOT the customer's system and continue with recovery.
b. Return to the Support Media's Main Menu.
Selection: a <-----
10. The system will autoboot into maintenance mode. Here you should verify
the BDRA.
11. vgchange -a y /dev/vg00 (activate the root volume group)
12. lvlnboot -v /dev/vg00 --> This should display something like what is shown
below. This sample has a mirror boot disk.
Boot Definitions for Volume Group /dev/vg00:
Physical Volumes belonging in Root Volume Group:
/dev/dsk/c0t6d0 (10/0.6.0) -- Boot Disk <--- Primary boot disk
/dev/dsk/c0t5d0 (10/0.5.0) -- Boot Disk <--- Mirror boot disk
Boot: lvol1 on: /dev/dsk/c0t6d0
Boot: lvol1 on: /dev/dsk/c0t5d0 <---------- Mirror boot disk
Root: lvol3 on: /dev/dsk/c0t6d0
Root: lvol3 on: /dev/dsk/c0t5d0 <---------- Mirror boot disk
Swap: lvol2 on: /dev/dsk/c0t6d0
Swap: lvol2 on: /dev/dsk/c0t5d0 <---------- Mirror boot disk
Dump: lvol2 on: /dev/dsk/c0t6d0, 0
After booting the system the BOOT, ROOT, SWAP,and DUMP volume information
should be correct. If something is missing use the below commands to add.
For example:
BOOT: "lvlnboot -b /dev/vg00/lvol1"
When '/stand' is ONLY on a separate logical volume.
If your not sure check /etc/fstab for a seperate lvol
for /stand.
Otherwise BOOT and ROOT are considered identical.
ROOT: "lvlnboot -r /dev/vg00/lvol3"
Or lvol1 if their is NOT a seperate lvol for /stand
SWAP: "lvlnboot -s /dev/vg00/lvol2"
DUMP: "lvlnboot -d /dev/vg00/lvol2"
13: If you had to make any changes then verify the information is correct with:
"lvlnboot -v /dev/vg00"
14: enter "lvlnboot -R /dev/vg00"
15: Then the boot string should be changed back:
"mkboot -a "hpux (;0)/stand/vmunix" /dev/rdsk/c0t6d0" <-- Primary disk
"mkboot -a "hpux -lq (;0)/stand/vmunix" /dev/rdsk/c0t5d0" <-- Mirror disk
16. Reboot the system
with "reboot"
Time has a wonderful way of weeding out the trivial
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-19-2006 10:50 PM
тАО05-19-2006 10:50 PM
Re: IPL error: bad LIF image
Hello,
Please use the above procedure for recovering the corrupted LIF.
you can run the below command
SEA IPL
at PDC/BCH promt to search for devices with LIF/Boot area... ie bootable disks.
ensure that the disk which you have tried to boot apears in this.
Regards,
Siva.
Nothing is Impossible !
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Learn About
News and Events
Support
© Copyright 2025 Hewlett Packard Enterprise Development LP