HP-UX Virtual Partitions Release Notes (A.04.03)

Known Problems and Workarounds
Virtual Partition Does Not Boot After Root Mirror is Created
Chapter 342
Virtual Partition Does Not Boot After Root Mirror is
Created
Related JAG or Patch ID Number
JAGaf54464
Applicable on
❏ vPars A.04.xx on Integrity
Description
A virtual partition does not boot from its mirror root disk because there is
no longer a valid EFI to hardware path mapping in the vPars database.
Symptoms
After creating a mirror root disk, the virtual partition fails to boot from this
disk. You may see messages similar to the following:
Load of 1/0/8/1/0.22.31.0.0.0.1 failed: Not Found
Workaround
After the mirror is created, use the vparefiutil -u command to add the
new hardware path to EFI path mapping to the vPars database.
Note that on Integrity systems running vPars, whenever the EFI path of a
boot disk changes (for example, if an OS is re-installed on the disk), the new
hardware to EFI path mapping has to be updated in the vPars database.
This can be done by running the vparefiutil -u command. For more
information on EFI and vPars, see the “EFI and Integrity Notes” section in
the document Installing and Managing HP-UX Virtual Partitions.