Ignite install failure - runts

[John Payne_2]

On Friday morning I ignite installed a machine, called 'client a', with my current 11i image, updated the image, and did a make_sys_image. Then I tried to install another machine, called 'client b', with the new and improved image. This install hung. After trying this several times, I gave up and had the network guys look at the switch. Client B's port had a few FCS errors and a ton of runts. I tried swapping disks (these are all rp2470's...) of client a and client b to try to install client b from client a's chassis. Same result. The ignite server is on a different switch than the 2 clients. I put the disks back and tried swapping client a and the server's network cables. Same result. Then I put the network cables back and tried swapping the server and client a's disks. Same result. (I have been trying to rule out networking HW...)

The network guys only see the runts from client b's install. (And client a's port from when client b's disks were there.) There are no errors on the server's switch, and I can't find anything complaining on the server itself.

Like I said, I had a successfull install Friday morning. After updating the image, I can no longer install anything to client b. (My old 11.0 image doesn't work, and the 11i image I installed Friday morning doesn't work.) I am hesitant to reinstall client a, since the OS is installed and happy. (We need to get some apps running on it.) I have no other machine to test on right now.

Both client a and client b are machines that have previously been ignite installed and been happy. (These are both about a year old...) They had previously been R&D machines and we wanted to reinstall for a production implementation.

Any ideas before I open an issue?

Thanks

John

[Steven E. Protter · Accepted solution]

Been there done that got the tee shirt.

Check this patch:

swlist -l product PHCO_26422

On the golden image machine.

If yoiu find it, do this:

swremove PHCO_26422

Why you might ask?

Because that patch cranks up the pax utility, used by make_sys_image to archive files bigger than 2 Gig, all the way up to 8 Gig.

Problem is that pax_iux the guy that unpacks the file still stop and hang when it tries to unpack the file.

You can verify this by pushing a command shell on the console of the client b. You can then run the command yourself and watch the process with tusc.

This problem cost me a month earlier this year on a project.

Because of how much heart ache this called me, I hope you can avoid some of it. If this is your issue, I think this is a 10 point solution.

Yeah, I'm in chutzpah mode, but this problem took me and HP Support WEEKS to figure out.

I wote a paper on this subject, which I will attach upon request.

SEP

[John Payne_2]

Stephen,

I had the Pax patch installed on the golden-image system, and removed it, but I still get the hang. (With the runts in the switch.)

Any other ideas? (And maybe it would help to look at the paper...)

Thanks

John

[John Payne_2]

Stephen,

I'm still having issues, even after removing the patch. Last night I let the install go before I left, and it took 7 hours to run. (runts and all.) The newly installed machine doesn't quite look right. (And the root password was not what I was expecting.) I shut it down as soon as I saw it this morning, and need to reinstall again.

Could you post your paper, please?

(And I'll get around to the points... ;) )

Thanks
John

[John Payne_2]

Stephen,

I'm still having issues, even after removing the patch. Last night I let the install go before I left, and it took 7 hours to run. (runts and all.) The newly installed machine doesn't quite look right. (And the root password was not what I was expecting.) I shut it down as soon as I saw it this morning, and need to reinstall again.

Could you post your paper, please?

(And I'll get around to the points... ;) )

Thanks
John

[John Payne_2]

Stephen,

I'm still having issues, even after removing the patch. Last night I let the install go before I left, and it took 7 hours to run. (runts and all.) The newly installed machine doesn't quite look right. (And the root password was not what I was expecting.) I shut it down as soon as I saw it this morning, and need to reinstall again.

Could you post your paper, please?

(And I'll get around to the points... ;) )

Thanks
John

[John Payne_2]

Stephen,

I'm still having issues, even after removing the patch. Last night I let the install go before I left, and it took 7 hours to run. (runts and all.) The newly installed machine doesn't quite look right. (And the root password was not what I was expecting.) I shut it down as soon as I saw it this morning, and need to reinstall again.

Could you post your paper, please?

(And I'll get around to the points... ;) )

Thanks
John