Ignite-UX (IUX) Document for Frequently Asked Questions (FAQ) (762793-001, March 2014) (Edition: 3)

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 might result in success.
If retrying does not resolve the problem, you can workaround the problem for recovering a system
by doing the following:
• 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 is that, the disk devices attached to that ext_bus will be assigned a different instance
number and have a different device file name than before.
NOTE: The problem might persist even after disabling just one line. You can either try and disable
the next entry at every instance, or disable all hw_instance_num lines if required.
• When using a tape recovery you cannot disable just one hw_instance_num value as you
can with a network recovery. For tape:
◦ From the first UI screen, select Advanced Options.
◦ From Advanced Options, select the Edit (vi) config file.
◦ From vi editor, add the following line:
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.
Why do I see errors about io.info version 0.5 not being understood and how do
I workaround it?
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, the following errors might occur:
ERROR: 0x40041e30: IOTree::parse_io_info_line: io.info
version is 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 workaround this issue, 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.
16 Known problems