In the same way you can boot a virtual partition into single-user
mode (see “Booting
a Virtual Partition into Single-User Mode”), you
can boot a partition using other boot options. The general syntax
is:
From MON>
MON> vparload -p <target_partition> <boot_options>
or
From shell prompt
<active_partition># vparboot -p <target_partition> -o "<boot_options>"
Two LVM-based examples, maintenance mode and overriding quorum, are
shown below. For more information on all the boot options, see the manpage hpux(1M).
Maintenance
Mode |
 |
When troubleshooting LVM, you may need to enter into maintenance mode
using the -lm option. For more information
on maintenance mode, see the book "Managing Systems and
Workgroups."
On a non-vPars server, you would boot the server into maintenance
mode by executing the following:
ISL> hpux -lm
On a vPars server, you specify the same -lm option
but as an argument to either the monitor vparload command or as a -o option to
the shell vparboot command.
For example, if the partition winona2 is
down, to boot winona2 into maintenance
mode:
From MON>
From the monitor prompt:
MON> vparload -p winona2 -o "-lm"
From shell prompt
From the running partition winona1:
winona1# vparboot -p winona2 -o "-lm"
Overriding
Quorum |
|
In
LVM, when the root disk is mirrored, the server can only activate
the root volume group, which contains the OS instance, when the
majority of the physical volumes in a root volume group are present
at boot time. This is called establishing a quorum. Sometimes, you
may want to boot an OS instance regardless of whether a quorum is
established. You can override the quorum requirement by using the
-lq option. For more information on quorums,
see the book "Managing Systems and Workgroups."
On a non-vPars server, you would boot overriding quorum using:
ISL> hpux -lq
On a vPars server, you can execute either of the following:
From MON>
From the monitor prompt, to boot winona2 overriding
the quorum requirement:
MON> vparload -p winona2 -o "-lq"
From shell prompt
From the running virtual partition winona1,
to boot winona2 overriding the quorum requirement:
winona1# vparboot -p winona2 -o "-lq"
|
| |
|
 | NOTE: Specifying the boot options from the command line only
affects the current boot. On a non-vPars server, to have a server
permanently boot with the -lq option, you
would put "hpux -lq" in the LIF AUTO file. On a vPars
server, to have a partition boot with the -lq option,
you would simulate the AUTO file usage
by entering the -lq option into the partition database.
See “Simulating
the AUTO File on a Virtual Partition”. |
|
| |
|
Changing
the LVM Boot Device Hardware Path for a Virtual Partiton |
|
Example
Below are the steps to move the root disk of a single virtual
partition.
These instructions require that the virtual partition be constrained
in
the following way:
the logical volume
used for the primary swap device must be
on the boot device;
in other words, boot and swap must be on the same disk device.
This can be verified by the following steps:
Before changing the hardware path of the boot device:
Create a mapfile for the root volume group.
Keep the mapfile inthe root (/) directory, so that it is accessible
during single user mode boot.
vgexport -p -m /mapfile.vg00 /dev/vg00
Get a list of physical volumes (PVs) in the root volume
group. Keep the PV list file in the root (/) directory, so that
it is accessible during single user mode boot.
vgexport -p -f /pvs.vg00 /dev/vg00
You may now shutdown the virtual partition and physically
move the disk.
Change
the boot device hardware path
From another virtual partition, change the
target virtual partition atrributes
vparmodify -p partition_name -a io:new_path:boot -B manual
vparmodify -p partition_name -d io:old_path
where
partition_name is the target virtual partition
new_path is the new hardware path of the disk
old_path is the old hardware path of the disk
Verify the attributes
vparstatus -v -p partition_name
Boot
into LVM maintenance mode
Boot the target virtual partition into LVM
maintenance mode. For example, at the monitor prompt:
MON> vparload -o -lm -p partition_name
LVM
maintenance mode steps
Once the partition comes up in LVM maintenance
mode, run ioscan to get the device filename of the boot device
ioscan -fnkCdisk
If the device filename (/dev/dsk/file) is new, use insf to install the special files in /dev directory.
Run vgscan to get the device filenames grouped withboot device.
vgscan
Remove the old information about root volume group.
vgexport /dev/vg00
You may have to remove /etc/lvmtab.
Prepare to import the root volume group (vg00).
mkdir /dev/vg00
mknod /dev/vg00/group c 64 0x00000
Import the root volume group (vg00). For example:
vgimport -m /mapfile.vg00 /dev/vg00 /dev/dsk/c1t1d0 /dev/dsk/c1t1d1
where the device filenames are obtained from the ioscan and vgscan above
Activate the root volume group (vg00):
vgchange -a y /dev/vg00
You may also have to cleanup and prepare LVM logical volume
to be root, boot, primary swap, or dump volume as follows:
lvrmboot -r /dev/vg00
lvlnboot -b /dev/vg00/lvol1
lvlnboot -r /dev/vg00/lvol3
lvlnboot -s /dev/vg00/lvol2
lvlnboot -d /dev/vg00/lvol2
mount
Verify that the hardware path for the boot device matches
the primary boot path.
lvlnboot -v /dev/vg00
If the hardware path has not changed to the primary
boot path, change it by running lvlnboot with the recovery (-R) option. This
step is normally not necessary.
lvlnboot -R /dev/vg00
Reboot the target virtual partition.
Printable version
