HP-UX Virtual Partitions Release Notes A.05.08

Symptoms
The virtual partitions will not boot after a reboot. One or more of the following errors may
appear in the vPars Monitor event log:
iodc_perror: dev_open/Boot device init (0x42)
iodc_perror: reinit_bootdev/Read ENTRY IO (0x44)
iodc_perror: dev_reopen/Read ENTRY IO (0x47)
iodc_perror: iodc_io_init/init module and device(0x4b)
Could not read IODC firmware for HPA <hpa>
Unknown filesystem for path <hardware path>
Workaround
Manually boot the virtual partitions with the vparboot or vparload command.
• Software Configuration Error During HP-UX Install on Virtual Partitions
Related Defect ID and Patch Number
JAGag27323
Applicable On
vPars A.05.xx
Description
During the installation of HP-UX on a virtual partition, an error may occur during the
configuration of the iCOD software product. When the virtual partition reboots following the
configuration phase, the software will be configured correctly, so there is no loss of functionality.
Symptoms
An error message will appear in the install log:
ERROR: The "configure" script for "iCOD.ICOD-RUN" failed
Workaround
After the installation completes, the software is configured correctly, no further action is required.
To avoid this error for future installs, update the server firmware to the latest supported version.
See the HP-UX Virtual Partitions Ordering and Configuration Guide for details.
• On PA-RISC Servers, Booting a Fibre Channel Tape Device May Cause
the Target Virtual Partition to Hang
Related Defect ID and Patch Number
JAGaf09885
Applicable On
◦ vPars A.05.xx on PA-RISC
◦ vPars A.04.03 on PA-RISC
Description
If you attempt to boot a virtual partition using a Fibre Channel tape device that has been
configured using the :TAPE attribute, the target virtual partition may hang.
Symptoms
On PA-RISC servers, if you attempt to execute the command
# vparboot -p target_vpar -B TAPE
10 vPars A.05.08 Release Notes