lvlnboot.1m (2010 09)

l
lvlnboot(1M) lvlnboot(1M)
During maintenance-mode boots, since the root volume group is not
activated, lvlnboot -c does not update /stand/rootconf
.
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 root volume group is created, the first boot must be a nor-
mal 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.
-d dump_lv Define dump_lv to be one of the dump volumes the next time the system
is booted on the volume group. dump_lv must be a contiguous logical
volume.
For volume group version 1.0, dump_lv cannot have bad block relocation
enabled.
The command updates the Boot Data Reserved Area of each bootable
physical volume in the volume group (see pvcreate (1M)).
The combined size of all the dump volumes should be at least 2048 bytes
larger than the total memory of the system.
Multiple dump devices can be configured, but each dump_lv must be
entered with a separate
lvlnboot command line.
This option will be obsolete in the next HP-UX release.
-r root_lv Define root_lv to be the root volume the next time the system is booted on
this volume group. root_lv must be a contiguous logical volume.
For volume group version 1.0, the root_lv cannot have bad block reloca-
tion enabled.
If root_lv is the first logical volume on the physical volume, then it is
configured as the combined root-boot volume. Otherwise, root_lv is
configured as the separate root volume in which case a separate boot
volume needs to be configured using the
lvlnboot -b option.
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) for PA-RISC systems).
The physical volumes containing root_lv must have been created using
the
pvcreate -B option (see pvcreate (1M)), indicating that that physi-
cal 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 physical 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 previously defined must be removed via lvrmboot (1M).
This option will be obsolete in the next HP-UX release.
2 Hewlett-Packard Company − 2 − HP-UX 11i Version 3: September 2010