HP-UX Virtual Partitions Administrator's Guide (includes A.03.05 and A.04.05)

Following are some scenarios where you may need to perform additional actions if the EFI path to
hardware path mappings are not up to date in the vPars database::
• Creating an alternate vPars database while in vPars mode.
Problem:
If an alternate vPars database is created while in vPars mode and the Monitor is later booted
using that alternate database, then it may not be possible to boot some of the virtual partitions
of the alternate database if the EFI paths corresponding to those hardware paths are not
present in the alternate database.
Solutions:
• The virtual partitions that could not boot can be re-installed using vparboot -I:
vparboot -p partition_name -I
• The virtual partitions that could not boot can be booted using the Monitor command
vparload:
vparload -p partition_name -E disk_index
• Creating a virtual partition in vPars mode.
Problem:
If a virtual partition is created while in vPars mode, then it may not be possible to boot that
partition if the EFI path corresponding to the boot disk hardware path is not present in the
vPars database.
Solutions:
• The virtual partition can be re-installed using vparboot -I:
vparboot -p partition_name -I
• The virtual partition can be booted using the Monitor command vparload:
vparload -p partition_name -Edisk_index
• An OS is installed not using vparboot -I and the database is created as a last step.
Problem:
If an OS is installed on one disk (for example, vpar1), the database (vpdb) is created on
vpar1, an OS is installed on vpar2 in nPars mode, vparenv is executed on vpar2 to change
the mode to vPars, and the Monitor is booted from the boot disk of vpar1, then it may not
be possible to boot vpar2.
Solutions:
• Boot from vpar1's boot disk into nPars mode and execute the following set of commands
to update the vPars database and change the mode:
vpar1# vparefiutil -u [-D /stand/vpdb]
vpar1# vparenv -m vPars
• Create the database (vpdb) on the last installed virtual partition and boot the Monitor
from it.
• MirrorDisk and EFI path.
Problem:
If the idisk command is executed on a disk during mirror disk creation, the EFI path of
the disk may change. It may not be possible to then boot from the new mirrored disk using
vparboot -B.
Solutions:
• After creating the mirror disk, set the mirror disk as alternate path using setboot.
EFI Boot Disk Paths, including Disk Mirrors, and vparefiutil (Integrity only) 125