HP-UX Reference (11i v1 05/09) - 1M System Administration Commands A-M (vol 3)

l
lvlnboot(1M) lvlnboot(1M)
Either the separate root or the separate boot volume can be configured first.
The command updates the Boot Data Reserved Area of each bootable physical
volume (see pvcreate(1M)) to enable the volume group to be used to locate the
root file system. root_lv is also used as the root volume during a maintenance-
mode boot (see hpux(1M)).
The physical volumes containing root_lv must have been created using the
pvcreate -B option (see pvcreate(1M)), indicating that that physical volume
is to be used as a bootable physical volume. Also, the
mkboot command (see
mkboot(1M)) must have been run on the physical volume to create the LIF area
at the top of the physical volume (see lif(4)).
-R Recover any missing links to all of the logical volumes specified in the Boot Data
Reserved Area and update the Boot Data Reserved Area of each bootable physi-
cal volume in the volume group (see pvcreate(1M)).
-s swap_lv Define swap_lv to be the primary swap volume the next time the system is
booted on the volume group. swap_lv must be a contiguous logical volume, and a
root logical volume must have been previously defined with this command.
The command updates the Boot Data Reserved Area of each bootable physical
volume in the volume group (see pvcreate(1M)). Any existing swap area previ-
ously defined must be removed via lvrmboot(1M).
-c During normal boots (vs. maintenance-mode boots, see hpux(1M)), this command
is automatically executed by
/sbin/ioinitrc
(see inittab(4)).
Since this command is performed during boot, it does not need to be performed
manually unless
/stand/rootconf
is missing in a separate root/boot
configuration (or alternatively, performing a normal reboot will recreate this
file).
This command updates the
/stand/rootconf
file with the location of the
root volume in the currently booted volume group.
The
/stand/rootconf
file is used during maintenance-mode boots to locate
the root volume for volume groups with separate boot and root volumes.
During maintenance-mode boots, since the root volume group is not activated,
lvlnboot -c does not update /stand/rootconf
. For separate root/boot
configurations, maintenance-mode boot will fail if
/stand/rootconf does not
already exist with the correct location of the root volume. See WARNINGS.
When a new volume group with separate boot and root volumes is created, the
first boot must be a normal boot (versus. a maintenance-mode boot), so that
/stand/rootconf gets created.
This option does not allow updating
/stand/rootconf
for any volume group
other than the one that is booted.
-v Print verbose messages. With no other arguments present, print information on
root, boot, swap, and dump logical volumes. If a combined root-boot volume is
configured, no information for the boot volume is displayed.
EXTERNAL INFLUENCES
Environment Variables
LANG determines the language in which messages are displayed.
If LANG is not specified or is null, it defaults to "C" (see lang(5)).
If any internationalization variable contains an invalid setting, all internationalization variables default to
"C" (see environ(5)).
EXAMPLES
The following examples show configuration of a combined root-boot volume.
Create a root volume group, vglvmroot , containing root, swap, and dump logical volumes. Assume
that an appropriate directory called /dev/vglvmroot and a corresponding group file already
exist (see lvm(7)).
Section 1M−−454 Hewlett-Packard Company − 2 − HP-UX 11i Version 1: September 2005