Operating System - HP-UX
1836460 Members
2530 Online
110101 Solutions
New Discussion

Ignite-UX recovery error on client after make_net_recovery

 
SOLVED
Go to solution
Andreas Tausch
Occasional Advisor

Ignite-UX recovery error on client after make_net_recovery

Hi there,

I just set up an Ignite-UX server (revision C.7.4.157 on HP-UX 11.11) to store the recovery archives of our HP-UX machines (created with make_net_recovery).

The creation of the recovery archive works fine. But when I try to recover my test machine I get the following error:

======= 02/13/08 04:12:18 EST HP-UX Installation Initialization. (Wed Feb 13

04:12:18 EST 2008)

@(#)Ignite-UX Revision C.6.10.97

@(#)ignite/init (opt) $Revision: 10.526 $ $Date: 2006/06/20 22:26:23 $



* Scanning system for IO devices...

* Querying disk device: 10/0/15/1.5.0 ...

* Querying disk device: 10/0/15/1.6.0 ...

* Querying graphics device: 10/6/2/0 ...

* Setting keyboard language.

* Bringing up Network (lan0)

add net default: gateway 10.35.1.10

* NFS mounting clients directory.

* Using client directory: /var/opt/ignite/clients/0x00306E485973

* Checking configuration for consistency...

ERROR: "/var/opt/ignite/clients/0x00306E485973/recovery/2008-02-13,08:56/syst

em_cfg", line 165: Illegal character: "i"

ERROR: "/var/opt/ignite/clients/0x00306E485973/recovery/2008-02-13,08:56/syst

em_cfg", line 165: syntax error

ERROR: Problems were encountered while parsing config file: "/var/opt/ignite/

clients/0x00306E485973/recovery/2008-02-13,08:56/system_cfg".

ERROR: net_cfg_prep: Problems were encountered while parsing the

configuration files. See the messages above for details. Using

instl_adm with the -T and/or -D options on the server may help isolate

the problem. (See instl_adm(1M) and instl_adm(4) man pages.)

ERROR: Cannot initialize I/O data: unable to open IO file:

/var/opt/ignite/clients/0x00306E485973/io.info.

WARNING: read_hw_info: Initialization of the IO tree failed.

ERROR: No disks found on system.

NOTE: Cannot access file:

/var/opt/ignite/clients/0x00306E485973/config: - ignoring



NOTE: The disk at HW path: 10/0/15/1.6.0 does not exist on the system and

was specified in the configuration for the system. No substitute disk

could be found, so it will be removed from the configuration.

NOTE: The volume group vg00 will be removed from the configuration since

there are no disks associated with it.

ERROR: Unable to find any disks on the system. Please check the

hardware, reboot, and restart the installation process.



The user interface failed, would you like to restart it? ([y]/n): *

Response was: n



ERROR: Cannot continue since the UI failed.

NOTE: System rebooting...

~

Any ideas?
7 REPLIES 7
Robert-Jan Goossens_1
Honored Contributor

Re: Ignite-UX recovery error on client after make_net_recovery

Hi Andreas,

I've seen this error before on Itanium systems because of a mismatch between client and server ignite versions. Your server is running version C.7.4.157 and your client C.6.10.97.

Regards,
Robert-Jan

Andreas Tausch
Occasional Advisor

Re: Ignite-UX recovery error on client after make_net_recovery

Hi Robert,

thanks for your quick reply.

I thought about the mismatch in the Ignite-UX revisions. But the problem is: the test machine is a small workstation and probably due to that not too happy about any

boot lan. install

attempts. So I have to work around that issue with a HP-UX OE install CD, which only has the lower revision.

So, unless there are any other ideas on how to solve that illegal character issue, how do I create a boot cd with an up to date Ignite-UX release?
likid0
Honored Contributor

Re: Ignite-UX recovery error on client after make_net_recovery

you can boot your small workstation into ignite restore mode with the bootsys command from the ignite server.
Windows?, no thanks
Bill Hassell
Honored Contributor

Re: Ignite-UX recovery error on client after make_net_recovery

> the test machine is a small workstation

You should have no problem restoring an image created by this workstation. But you'll have lots of problems trying to restore any image from different hardware. Ignite is limited to restoring similar families of hardware and I/O. There is no way a server image would work on a workstation, or an Itanium backup restored onto a PA-RISC system.


Bill Hassell, sysadmin
Andreas Tausch
Occasional Advisor

Re: Ignite-UX recovery error on client after make_net_recovery

Hi there,

thanks for the help.

I used an

/opt/ignite/data/scripts/examples/make_media_install -C -m

to create an iso image of a bootable cdrom with the same IGNITE-UX revision as used on the server side.

Booting the machine to be recovered with that cdrom does the trick. No more errors messages about illegal characters. Recovery worked fine.

I will close the thread now.
Andreas Tausch
Occasional Advisor

Re: Ignite-UX recovery error on client after make_net_recovery

see above