Ignite-UX Frequently Asked Questions

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.
- From the "Advanced Options" menu, select "Edit (vi) config file"
- From the vi editor, add one line such as:
hw_instance_num = 0 "ioa" "sba" 0
- This will override the hw_instance_num values from the other
config files on the tape.
- The system will not attempt to restore any prior device file
naming because of this.
===============================================================================
1.19
Q: Why do I see errors about io.info version 0.5 not being understood
and how do I work around it?
A: If an Ignite-UX version C.6.8 - C.6.10 was used to create a recovery
image and then an Ignite-UX version C.7.1 - C.7.6 was used to recover
that image, you might see errors like this:
ERROR: 0x40041e30: IOTree::parse_io_info_line: io.info version is not
understood: 0.5
ERROR: Fatal error while parsing io.info file
ERROR: Cannot initialize I/O data: unable to parse
/var/opt/ignite/clients/0x00306E48CE61/io.info file.
The cause of these ERROR messages is that versions C.6.8 - C.6.10 of
Ignite-UX create a version 0.5 io.info file. When a recovery is
attempted with versions C.7.1 - C.7.6 of Ignite-UX, it is unable to
parse the old 0.5 version of the io.info file.
To work around this issue, you can do ONE of the following:
1) Run Actions -> Refresh Client from the ignite user interface.
2) Use "Boot Client" from the Actions menu to boot the client in
preparation for installing from the ignite user interface.
3) Use the client's console to boot from the Ignite-UX server.
4) Delete the io.info file in the client's directory.
===============================================================================
1.20
Q: When using the graphical interface, why do errors occur when opening