lvlnboot -v in syslog

[Coolmar]

I keep getting this in my syslog:

pr 6 08:26:10 psi3 LVM[4636]: /sbin/lvlnboot -v vg01
Apr 6 08:38:11 psi3 LVM[8282]: /sbin/lvlnboot -v
Apr 6 08:38:11 psi3 LVM[8285]: /sbin/lvlnboot -v
Apr 6 08:38:11 psi3 LVM[8288]: /sbin/lvlnboot -v vg01
Apr 6 08:38:12 psi3 LVM[8294]: lvlnboot -v
Apr 6 08:38:26 psi3 LVM[8525]: /sbin/lvlnboot -v
Apr 6 08:38:27 psi3 LVM[8528]: /sbin/lvlnboot -v
Apr 6 08:38:27 psi3 LVM[8531]: /sbin/lvlnboot -v vg01
Apr 6 08:38:27 psi3 LVM[8537]: lvlnboot -v
Apr 6 08:38:27 psi3 LVM[8548]: /sbin/lvlnboot -v
Apr 6 08:38:27 psi3 LVM[8551]: /sbin/lvlnboot -v
Apr 6 08:38:27 psi3 LVM[8554]: /sbin/lvlnboot -v vg01

Any ideas why I would get that? Also, when I reboot the system it crashes. I have to boot it into single user and then activate the volue groups manually and then init 6 and it comes up fine. So I wonder if that is related to the above error. Here is my output of lvlnboot -v (which is the right disk by the way):

Boot Definitions for Volume Group /dev/vg00:
Physical Volumes belonging in Root Volume Group:
/dev/dsk/c3t0d0 (0/0/14/1/0.201.7.0.0.0.0) -- Boot Disk
Boot: lvol1 on: /dev/dsk/c3t0d0
Root: lvol3 on: /dev/dsk/c3t0d0
Swap: lvol2 on: /dev/dsk/c3t0d0
Dump: lvol2 on: /dev/dsk/c3t0d0, 0

[Kent Ostby]

What errors are you getting when you crash on reboot?

This would be helpful to know so we can see if we are dealing with one problem or two.

[Coolmar]

It goes by too fast and there is nothing in /var/adm/crash. I can't reboot it right now either to get that info for you because people are on the system.

[Sanjay_6 · Accepted solution]

Hi Sally,

/Quote/

Messages such as:
/sbin/lvlnboot -v vg00
are logged to /var/adm/syslog/syslog.log when lvlnboot(1M) is called while in sam(1M). This occurs whenever a root user accesses:
SAM -->Disks & Filesystems -->Disk Devices

Note that these messages are informational only.

Check the samlog
SAM--> Options --> View SAM Log
to see if the access date/times correspond to the entries in syslog.

/EndQuote/

Hope this helps.

regds

[Bill Hassell]

Every time you run lvlnboot -v, it creates a syslog entry. It may be part of a system inventory script run from cron, but in your case, there are several right next to each other which isn't normal.

Something is broken if your system crashes. Check /etc/shutdown log to see the one-line reason for the crash. Also check /var/adm/crash for massive crash dump files. If not, check /etc/rc.config.d for the settings controlling crash dumps. You need to isolate hardware from software problems then drill down to the real problem.

[Andrew Rutter]

hi,

sounds like the lvm is corrupt/bad config or there is a faulty disk in the system.
what is the output of

#strings /etc/lvmtab

also check the coresponding pv for vg01 and also
#diskinfo -v /dev/rdsk/cxtxdx

and vgdisplay -v vg01

Are the vg's mirrored at all?

You need to first start by checking the disks and then working your way down the vg's, lvol's and lvm info.

Has this happened due to any change on the system? and did the system boot up ok previously.

Andy

[Torsten.]

There is nothing wrong with your system.

Everytime you run SAM - disk and file systems, SAM is collecting information and runs lvlnboot -v.
If this program is called, it gets logged in the syslog.
This is normal behaviour.

[Coolmar]

Below is the error I get when it crashes. I have also attached an ioscan and vgdisplay. I highlighted in red, what I think is the problem in the vgdisplay /dev/vg01...but I don't know how to fix it.


igelan0: INITIALIZING HP A6825-60101 PCI 1000Base-T Adapter at hardware path 0/0 /6/1/0
64 vcn
65 vcs

Host is virtual System Console slave
WARNING: ROOT device 0x1f030000 is a non-LVM partition, disallowed on LVM disk.
WARNING: ROOT device 0x1f030000 has been deconfigured (set to 0xffffffff).


-----------------------------------------------------
| |
| SYSTEM HALTING during LVM Configuration |
| |
Non-lvm root on LVM disk
| |
-----------------------------------------------------


linkstamp: Mon Jan 16 12:36:03 CST 2006
_release_version: @(#) $Revisi on: vmunix: vw: -proj selectors: CUPI80_BL2000_1108 -c 'Vw for CUPI80_BL20 00_1108 build' -- cupi80_bl2000_1108 'CUPI80_BL2000_1108' Wed Nov 8 19:24:56 P ST 2000 $
panic: LVM: Configuration failure

PC-Offset Stack Trace (read across, top of stack is 1st):
0x0c1f21d8 0x0c5076fc 0x0c50724c
0x0c5075c0 0x0c33aeb8 0x0c459394
0x0c33cba0 0x0c159854 0x0c1dfe64
End Of Stack

Trap Type 15 (Data page fault):
Instruction Address (pcsq.pcoq) = 0x0.0xc45d750
Instruction (iir) = 0x531a0020 (load/store)
Target Address (isr.ior) = 0x0.0x0000000000000010
Base Register (gr24) = 0x0000000000000000
Savestate Ptr (ssp) = 0xfb42c00.0x400003ffffff0f68
Savestate Return Pointer (ss_rp) = 0x0000000000000000

System Panic:

linkstamp: Mon Jan 16 12:36:03 CST 2006
_release_version: @(#) $Revisi on: vmunix: vw: -proj selectors: CUPI80_BL2000_1108 -c 'Vw for CUPI80_BL20 00_1108 build' -- cupi80_bl2000_1108 'CUPI80_BL2000_1108' Wed Nov 8 19:24:56 P ST 2000 $
panic: Data page fault

*** A system crash has occurred. (See the above messages for details.)
*** The system is now preparing to dump physical memory to disk, for use
*** in debugging the crash.

ERROR: Your system crashed before I/O and dump configuration was complete.
A crash dump cannot be taken under these circumstances without
special configuration. Contact your HP support representative.

[psi_4]
[MON] psi_3 has halted.

[Coolmar]

Sorry, I forgot to attach the document...so I will just paste it here:

vgdisplay -v /dev/vg01
Information in "/etc/lvmtab" differs from that in "/etc/lvmpvg".
Physical volume "/dev/dsk/c0t0d0" does not belong
to volume group "/dev/vg00".


psi3:/etc# string /etc/lvmpvg
sh: string: not found.
psi3:/etc# strings /etc/lvmpvg
VG /dev/vg00
PVG vg01
/dev/dsk/c0t0d0 **<- there is no c0t0d0


psi3:/etc# strings /etc/lvmtab
/dev/vg00
/dev/dsk/c3t0d0
/dev/vg01
/dev/dsk/c3t0d1
/dev/dsk/c3t0d2
/dev/dsk/c3t0d3
/dev/dsk/c3t0d4
/dev/dsk/c3t0d5
/dev/dsk/c3t0d6
/dev/dsk/c3t0d7
/dev/dsk/c3t1d0
/dev/dsk/c3t1d1
/dev/dsk/c3t1d2
/dev/dsk/c3t1d3
/dev/dsk/c3t1d4
/dev/dsk/c3t1d5
/dev/dsk/c3t1d6
/dev/dsk/c3t1d7
/dev/dsk/c3t2d0
/dev/dsk/c3t2d1
/dev/dsk/c3t2d2
/dev/dsk/c3t2d3
/dev/dsk/c3t2d4
/dev/dsk/c3t2d5
/dev/dsk/c3t2d6
/dev/dsk/c3t2d7
/dev/dsk/c3t3d0
/dev/dsk/c3t3d1

[Coolmar]

I removed /etc/lvmpvg and hopefully that will clear up the problem.

[Torsten.]

looks like you don't need the /etc/lvmpvg file, because you have only 1 disk in vg00.

Remove the file.

[Coolmar]

see above