HP-UX Virtual Partitions Release Notes A.05.08

where TAPE is a Fibre Channel tape device previously configured using the :TAPE attribute,
the target virtual partition may hang, remaining in the load state indefinitely. Further, the target
virtual partition does not reset when using vparreset.
Workaround
None. HP recommends that you not attempt to boot a Fibre Channel tape device.
• A Virtual Partition Remains in Load State with sx2000 Chipset
Related Defect ID and Patch Number
JAGaf88969
Applicable On
◦ vPars A.05.xx on Integrity
◦ vPars A.04.02, A.04.03 on Integrity
Description
On Integrity systems running the sx2000 chipset and Intel Itanium 2 single-core processor with
9 MB cache, a virtual partition remains in the load state for at least 30 seconds and does not
complete its boot process.
Symptoms
The console display includes the following:
Initializing IO Devices ...
LBA Cell 01 (01): Occupied PCI-X 133MHz
Scan PCI:
Rope Slot Seg Bus Dev Fun Card
..
Loading.: 1/0/1/1/0/4/0.6.0.0.0.0.0
Executing Image: "\EFI\HPUX\HPUX.EFI"
Optional Data : "\EFI\HPUX\HPUX.EFI boot /stand/vmunix"
Starting: 1/0/1/1/0/4/0.6.0.0.0.0.0
(C) Copyright 2004 Hewlett-Packard Development Company, L.P.All rights
reserved
HP-UX Boot Loader for IPF -- Revision 2.027
ESC[0mESC[37mESC[40m> System Memory = 16335 MB
loading section 0
......................................................
(complete) loading section 1 ............ (complete)
loading symbol table loading System Directory (boot.sys) to MFS .....
loading MFSFILES directory (/stand/bootfs) to MFS
..............
Workaround
You can either:
◦ Update the server firmware to the latest version. See the HP-UX Virtual Partitions Ordering
and Configuration Guide for firmware version details.
◦ If the virtual partition remains in the load state (you can use vparstatus to verify the
state), perform the following:
1. Issue a hard reset using vparreset to reset the virtual partition.
For example, if winona2 remains in the load state, to issue a hard reset:
winona1# vparreset -p winona2 -h
2. When the target partition is in the down state, attempt booting the partition using
vparboot. For example:
winona1# vparboot -p winona2
The virtual partition should recover and boot properly.
Known Problems and Workarounds 11