HP-UX Reference (11i v2 03/08) - 1M System Administration Commands A-M (vol 3)

ManualsBrandsHP ManualsSoftwareHP-UX Reference Manuals

421

422

423

424

425

426

427

428

429

430

lvlnboot(1M) lvlnboot(1M)

Specify that the logical volume, boot, will be used as the boot volume.

lvlnboot -b /dev/vglvmroot/boot

Specify that the logical volume, swap, will be used as the primary swap.

lvlnboot -s /dev/vglvmroot/swap

Specify that the logical volume, dump, will be used as the dump volume.

lvlnboot -d /dev/vglvmroot/dump

Display the results of the previous operations.

lvlnboot -v /dev/vglvmroot

The following example shows conﬁguration of multiple dump volumes.

Specify that logical volumes

/dev/vg00/swap1

, /dev/vg00/dump2

, and /dev/vg00/dump3

should be used as the dump logical volumes and that

/dev/vg00/swap1

should also be used as pri-

mary swap. Assume that the volume group and the logical volumes have been created and the logical

volumes are contiguous.

lvlnboot -s /dev/vg00/swap1

lvlnboot -d /dev/vg00/swap1

lvlnboot -d /dev/vg00/dump2

lvlnboot -d /dev/vg00/dump3

WARNINGS

Dump Volume Warnings

At the HP-UX 11.00 release and forward, the lvlnboot command will support any size dump device

depending upon the IODC ﬁrmware addressability of the system. If the conﬁgured dump logical volume

is out of the range of what the ﬁrmware can address, the lvlnboot command will return an error mes-

sage such as "Unable to conﬁgure dump logical volume. Dump logical volume size beyond the IODC max

address."

Separate Root/Boot Warnings

Whenever mkboot(1M) is used to restore the LIF area of a damaged root physical volume, the

-b boot_lv

option of

lvlnboot must be performed afterwards to record the boot volume information inside the new

LIF (see lif(4)). Subsequent lvlnboot commands such as lvlnboot -R are dependent on the boot_lv

information inside the LIF.

If the

-v option does not locate the boot volume boot_lv, and the -r root_lv has not yet been performed,

then performing the -r root_lv option will enable the boot volume to be located. The lvlnboot com-

mand derives the location of boot volume from the location of the root volume.

Separate Root/Boot Maintenance-Mode Warnings

When creating additional root volumes with separate root/boot, a normal boot must be performed on each

new root volume so that /stand/rootconf, which is required for maintenance-mode boots (see hpux(1M)),

gets created for each new root volume.

Mirrored root_lv volumes should start at the same offset on each physical volume so that the location

stored in /stand/rootconf works for maintenance-mode boots off of any mirror.

FILES

/stand/rootconf Contains the location of the root volume. Used during maintenance-mode boots

(see hpux(1M)) to locate the root volume for volume groups with separate boot

and root volumes.