lvlnboot -v Post: 302249367

Sponsored Content

Operating Systems HP-UX lvlnboot -v Post 302249367 by DustBunny on Tuesday 21st of October 2008 07:38:58 AM

10-21-2008

Registered User

Quote:

hi friends,

what is the meaning of "lvlnboot -v" when i make

#more syslog.log.1 | grep -i boot
Oct 5 08:30:18 hostname LVM[25190]: lvlnboot -v
Oct 6 08:30:18 hostname LVM[15749]: lvlnboot -v
Oct 7 08:30:18 hostname LVM[6288]: lvlnboot -v
Oct 8 08:30:18 hostname LVM[26977]: lvlnboot -v
Oct 9 08:30:18 hostname LVM[17459]: lvlnboot -v
Oct 10 08:30:18 hostname LVM[7793]: lvlnboot -v
Oct 11 08:30:18 hostname LVM[26220]: lvlnboot -v

is this a panic reboot...how to find machine/panic reboot information...
as far as i am concern...manual reboot is in /etc/shutdownlog

please advise..thanks

Well, I do not think that your system had a panic reboot and there's nothing to worry.

# lvlnboot -v is a command to print information on root, boot, and swap logical volumes. It also prints information about dump lv's.

#lvlnboot is a command to prepare lv's to be root, boot, swap or dump.

==> #man lvlnboot would give you more information!

If you need to know how this works, just type in "# lvlnboot -v" and you'll know it.

Second.

There are 2 cases.
1) Panic reboot (Which happens automatically)
2) Manual TOC (We do it when the system hungs and do not respond)

As system administrator, we would know if the system had a panic reboot or a manual TOC.

If you want to analyze it anyway (After a panic or TOC), you can go ahead and run a tools on to it to collect a output to analyze.

Like,
crashinfo (Latest)
q4 (Kinda old, though good)

Its actually run on "/var/adm/crash"

When you collect the output from the tool, and analyze it along with shutdownlog.log, rc.log, oldshutdownlog.log, ts99, etc.. you can find information on why the system went panic. May be a HPMC, hardware or software (It depends on servers and issues anyways)

Once you find the reason for the crash, you can fix it to make sure that the server does not reboot the second time because of the same problem. Smilie

However, analyzing it properly gives you those information! So, now in your case, I do not see any clue for system being panic since lvlnboot does not mean that the system went panic!

Hope this gives atleast some information.. Smilie

-DB

DustBunny

View Public Profile for DustBunny

Find all posts by DustBunny

LEARN ABOUT HPUX

vxdestroy_lvmroot

vxdestroy_lvmroot(1M)													     vxdestroy_lvmroot(1M)

NAME

       vxdestroy_lvmroot - remove LVM root disk and associated LVM volume group

SYNOPSIS

       vxdestroy_lvmroot [-v] [-b] lvm_root_disk

DESCRIPTION

       The  vxdestroy_lvmroot  command	tears  down  and removes the LVM volume group associated with the specified physical disk. This is done by
       removing the volumes in the volume group and then removing the volume group.

OPTIONS

       -b	 Invokes the setboot command to change the primary boot disk to the VxVM root disk from which the system was booted (if  the  pri-
		 mary  boot  disk is not already set to this disk).  The alternate boot device remains unchanged.  If the -v option is also speci-
		 fied, the settings of the primary and alternate boot devices are displayed.

       -v	 Outputs verbose messages including a timestamp that indicates major operations being performed.

ARGUMENTS

       lvm_root_disk
	    Specifies the device name of the LVM root disk that is to be destroyed, along with its entire volume group.

EXAMPLES

       This example shows the vxdestroy_lvmroot command invoked in its simpliest form:

       /etc/vx/bin/vxdestroy_lvmroot c5t1d0

       # /etc/vx/bin/vxdestroy_lvmroot -v -b c3t0d0
       Are you sure about destroying c3t0d0 (imported on VG /dev/vg02) ? YES
       vxdestroy_lvmroot 06:02: Tearing down /dev/vg02 on device c3t0d0
       vxdestroy_lvmroot 06:02:
	 Unmounting and removing any volumes associated with /dev/vg02
       vxdestroy_lvmroot 06:02: removing logical volume /dev/vg02/lvol1
       vxdestroy_lvmroot 06:02: removing logical volume /dev/vg02/lvol2
       vxdestroy_lvmroot 06:02: removing logical volume /dev/vg02/lvol3
       vxdestroy_lvmroot 06:02: removing logical volume /dev/vg02/lvol4
       vxdestroy_lvmroot 06:02: removing logical volume /dev/vg02/lvol5
       vxdestroy_lvmroot 06:02: removing logical volume /dev/vg02/lvol6
       vxdestroy_lvmroot 06:02: removing logical volume /dev/vg02/lvol7
       vxdestroy_lvmroot 06:02: removing logical volume /dev/vg02/lvol8
       vxdestroy_lvmroot 06:02: Removing Volume Group /dev/vg02
       vxdestroy_lvmroot 06:02: Removing device files in /dev/vg02
       vxdestroy_lvmroot 06:02: Removing LVM Physical Volume c3t0d0
       vxdestroy_lvmroot 06:02: Removing LVM Physical Volume c1t1d3
       vxdestroy_lvmroot 06:02: Removing LVM Physical Volume c1t1d4
       vxdestroy_lvmroot 06:02: Removing LVM Physical Volume c1t1d5
       vxdestroy_lvmroot 06:03: Current setboot values:
       vxdestroy_lvmroot 06:03: Primary:       0/0/6/0/0.0.0
       vxdestroy_lvmroot 06:03: Alternate:     0/0/1/0/0.1.0
       vxdestroy_lvmroot 06:03:
	 Making disk c0t1d0 (0/0/1/0/0.1.0) the primary boot disk
       vxdestroy_lvmroot 06:03:
	 Removal of device c3t0d0, volume group /dev/vg02 was successful

SEE ALSO

       cpio(1), dd(1), fsck(1M), setboot(1M) vxbootsetup(1M) vxcp_lvmroot(1M) vxres_lvmroot(1M)

VxVM 5.0.31.1							    24 Mar 2008 					     vxdestroy_lvmroot(1M)