- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- LIF corrupt or not present
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
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
Community
Resources
Forums
Blogs
- 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
тАО10-13-2008 11:10 AM
тАО10-13-2008 11:10 AM
WARNING: Could not restore LIF volume.
"/opt/ignite/bin/save_config" -f "/var/opt/ignite/recovery/config.recover" "vg00" >> "/var/opt/ignite/logs/makrec.log1" 2
>&1
lvlnboot: LIF information corrupt or not present on "/dev/dsk/c0t5d0".
Use the "mkboot" command to initialize the LIF area.
/usr/sbin/vgcfgbackup "vg00" >> /var/opt/ignite/logs/makrec.log1 2>&1
vgcfgbackup: Unable to read the physical volume.: I/O error
vgcfgbackup: Invalid LVMREC on Physical Volume /dev/rdsk/c0t5d0
lvlnboot -v:
lvlnboot: LIF information corrupt or not present on "/dev/dsk/c0t5d0".
Use the "mkboot" command to initialize the LIF area.
Boot Definitions for Volume Group /dev/vg00:
Physical Volumes belonging in Root Volume Group:
/dev/dsk/c0t5d0 (8/4.5.0) -- Boot Disk
/dev/dsk/c0t8d0 (8/4.8.0)
/dev/dsk/c1t5d0 (8/12.5.0)
/dev/dsk/c1t4d0 (8/12.4.0) -- Boot Disk
Boot: lvol1 on: /dev/dsk/c0t5d0
/dev/dsk/c1t4d0
Root: lvol3 on: /dev/dsk/c0t5d0
/dev/dsk/c1t4d0
Swap: lvol2 on: /dev/dsk/c0t5d0
/dev/dsk/c1t4d0
Dump: lvol2 on: /dev/dsk/c0t5d0, 0
setboot:
Primary bootpath : 8/4.5.0
Alternate bootpath : 8/12.4.0
Autoboot is ON (enabled)
Autosearch is ON (enabled)
lifls /dev/dsk/c0t5d0
read: I/O error
read_blocks(lifvol): error on 1024 byte write
lifls: Can't list /dev/dsk/c0t5d0; not a LIF volume
lifls /dev/dsk/c1t4d0
ISL AUTO HPUX PAD LABEL
ODE MAPFILE SYSLIB CONFIGDATA SLMOD
SLDEV SLDRIVERS SLSCSI MAPPER IOTEST
PERFVER PVCU SSINFO
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-13-2008 11:15 AM
тАО10-13-2008 11:15 AM
Re: LIF corrupt or not present
Hope this helps!
Regards
Torsten.
__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.
__________________________________________________
No support by private messages. Please ask the forum!
If you feel this was helpful please click the KUDOS! thumb below!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-13-2008 11:21 AM
тАО10-13-2008 11:21 AM
Re: LIF corrupt or not present
It looks like this is the disk I am booted on that is generating this error message.
pg /stand/bootconf
# Boot Device configuration file
# This File contains information regarding the location
# of the boot LIF. It is used by the KERN-RUN fileset to
# update the boot kernel.
l /dev/dsk/c0t5d0
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-13-2008 11:27 AM
тАО10-13-2008 11:27 AM
Re: LIF corrupt or not present
# mkboot -l /dev/rdsk/c0t5d0
and check with lifls.
Hope this helps!
Regards
Torsten.
__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.
__________________________________________________
No support by private messages. Please ask the forum!
If you feel this was helpful please click the KUDOS! thumb below!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-13-2008 12:21 PM
тАО10-13-2008 12:21 PM
Re: LIF corrupt or not present
mkboot -l /dev/rdsk/c0t5d0
Could not open /dev/rdsk/c0t5d0: I/O error
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-13-2008 12:29 PM
тАО10-13-2008 12:29 PM
Re: LIF corrupt or not present
SCSI describe of /dev/rdsk/c0t5d0:
vendor: SEAGATE
product id: ST32550W
type: direct access
size: 2082636 Kbytes
bytes per sector: 512
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-13-2008 12:57 PM
тАО10-13-2008 12:57 PM
SolutionHow about this to prove it or not.
dd if=/dev/rdsk/c0t5d0 of=/dev/null
Let it read through the drive, if no IO error then back to the task at hand. If you get an IO error then you need to replace the drive.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-13-2008 04:12 PM
тАО10-13-2008 04:12 PM
Re: LIF corrupt or not present
> Could not open /dev/rdsk/c0t5d0: I/O error
Your disk at c0t5d0 is broken. You have probably been running on the mirror copy for quite a wg=hile, especially if you don't have EMS setup to notify you of disk errors and you don't look at syslog regularly.
Ignite/UX is a very useful tool to check the health of your system, especially disks and mountpoints. Ignite/UX errors mean that your system has got some problems.
Bill Hassell, sysadmin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-15-2008 05:52 AM
тАО10-15-2008 05:52 AM
Re: LIF corrupt or not present
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-15-2008 06:20 AM
тАО10-15-2008 06:20 AM
Re: LIF corrupt or not present
Hi,
Replacement procedure:
=======================
Since it is 10.20 I assume that the disks are non hot swapable.
=>Power off the server
=>Replace the faulty disk
=>Boot from alt disk
=>Interupt the boot and boot with qorum override(ISL> hpux -lq
=>vgcfgrestore -n vg00
=>vgchange -a y vg00
=>vgsync
=>lvlnboot -Rv
=>lvlnboot -b
=>lvlnboot -s
=>lvlnboot -d
=>lvlnboot -r
=>lvlnboot -v
Ganesh.