Ignite install error

[Ramones]

Hi everyone

I am trying to clone a machine in a new HW with the makerecovery tape. When I start to install it I receive this error, when loading the configuration user interface:

/usr/lib/dld.sl: Can't find path for shared library: libcl.2
/usr/lib/dld.sl: No such file or directory
NOTE: run_cmd: Process: 83 (/opt/ignite/bin/itool): killed by signal: 6.
The user interface failed, would you like to restart it? ([y]/n): y

Both the two machines, the one I'm cloning and the one I intent to destroy have the same Ignite-UX version.
Does anyone knows this problem?


Thanks,
R

[Torsten.]

What models are the source and target system? What is the ignite and hp-ux version?

Maybe you have a corrupted backup ...

[Ramones]

Hi

The source model is 9000/800/N4000-44, the target is 9000/800/rp8420 (vPAR). The ignite-ux version is C.6.9.141 on both.
It is not the backup because I already made two (in two new dds tapes).


Thanks,
R

[Tim Nelson]

Cloning disparaging models MAY or MAYNOT work. You are on your own.

First you need to update the N4000 with the latest patches and enablements.

Just then, MAYBE it will work.

[Ramones]

Hi

I've managed to solve the problem.
I am booting the vPAR I am about to destroy (vp1)from another vPAR on that nPAR (vp2). vp2 had a lower version of Ignite-UX, I upgraded that version to the same one of the other two machines and it worked fine. (I hope I managed to explain myself clearly enough).
Thanks for your advices anyway.


Regards,
R

[Torsten.]

Where are the vPars - on the rp7400 or on the rp8420?

So the ignite update solved your problem?

[Ramones]

The vPARs are on the rp8420.
The update indeed solved my problem. I am cloning the machine at the moment.
I had the upgrade idea by reading this line on the vparboot man page:
"ignite_kernel can reside either on the current virtual partition (the one on which vparboot is run) or on any other networked system or virtual partition accessible from that partition. The syntax for ignite_kernel is:
[Server name or IP addr,]cold-install_kernel
"

If I was not using an ignite_kernel from another machine than the one on vp2 was being used, so release matters...


Thanks,
R