Ignite-UX (IUX) Frequently Asked Questions (July 2013)

which was posted on 20-Mar-2006.
Note: HPVM requires this patch if you are installing a virtual
machine from an Ignite-UX server running B.11.11. Not having
this patch installed on the server will cause the network boot
to fail because of a firmware defect. No tftpd patch is
required for B.11.23 onwards as the tftpd daemon supports the
"tsize" option from first release.
=============================================================================
==
1.18
Q: How can I workaround recovery failure: 'ERROR: A conflict has been
detected while attempting to restore the prior device file names'?
A: This error is caused by the way that device special files are managed
while restoring a prior instance number assignment of the ext_bus
class devices (this instance number appears in the device file names
for disks following the 'c' character).
For VxVM, the device files must not be renamed prior to the kernel
knowing about the new instance assignments, and for LVM/whole-disk,
they must be renamed prior. So when the system has a mixture of VxVM
and LVM/whole-disk there is a chance that device files used by one or
the other need to be exchanged resulting in a conflict.
In the case of fibre channel devices, the kernel can sometime assign
different instances for the ext_bus devices each time the system
boots Ignite-UX. So in these cases, if you get the error, simply
rebooting and retrying may result in success.
If retrying does not resolve the problem, you can workaround the
problem for recovering a system by doing:
- When using an Ignite server to do a network recovery, on the
ignite server, do:
- Edit the "system_cfg" file under the correct directory for the
recovery you are doing: For example:
/var/opt/ignite/clients/{client}/recovery/latest/system_cfg
- Comment out (using the # char) the "hw_instance_num" keyword
for the ext_bus device referenced by hardware path in the error
message.
- The result of doing this is that disk devices attached to that
ext_bus will be assigned a different instance number and have a
different device file name than before.
- It is possible to still run into the problem with just the one
line disabled. You can either keep trying and disabling the
next entry, or disable all hw_instance_num lines if desired.
- When using a tape recovery you cannot disable just the one
hw_instance_num value as you can with a network recovery. For tape:
- From the first UI screen, select the "Advanced Options" menu.