Having trouble kickstarting Red Hat Linux 9 over the network

I am in the process of kickstarting Red Hat Linux 9 on a series of PCs.  I boot each PC with a boot disk and then insert a network driver disk when requested to perform installation over the network from our install server.  This works fine on almost all the machines, but a few have the following problem: the installation crashes with a fatal error at the point when either the ncurses package is being installed, the aspell package is being installed, or a dictionary package for aspell is being installed.  Could someone please suggest how to fix this?  Just today, I went through about 10 failed attempts to kickstart a single machine, so ANY suggestions are really appreciated.
aleksandrzingorenkoAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

shivsaCommented:
could u post the exact error possible.
0
jlevieCommented:
Since the install server works on most of the machines I'd suspect some sort of network problem on the systems that fail. It might be that the failing machines aren't correctly negotiating the link mode (one end in HDX, the other in FDX). Such a network link will mostly work, but it will usually fail on large transfers.

What NIC's are in the machines that fail? What Hub/Switch is being used?
0
aleksandrzingorenkoAuthor Commented:
I don't remeber everything in the error box, but I do remeber that the title on top is "Error Installing Package" and the box contains the following words: "This could be due to media failure, lack of disk space, and/or hardware problems.  This is a fatal error and your installation will be aborted.  Please verify your media, then try your install again.  Press the OK button to reboot your system."

As for the NICs, the machines that fail have the same ones as the machines that work.  We use NETGEAR hubs and switches by Foundry Networks, if that is of any help.
0
aleksandrzingorenkoAuthor Commented:
Oh, and another thing, how do I check that the link mode is correctly negotiated and fix it if it is currently incorrect?
0
jlevieCommented:
The fix for a mis-negotiated link, if that's what this problem is, is to force one or both ends of the link to a sane mode. With managed switches this can usually be done on a per-port basis, but sometimes it is necessary yo set both the switch and the node's mode. I don't know how you'd force the link mode during kickstart or network install. With the OS running once cna use mii-diag or a card specific diag tool for the job.

I've had this problem when Jumpstarting Suns and solved it there by interposing a 10Mbps hub in between the Sun and the rest of the network for the install. Once the OS is up I can force the Sun's NIC to the correct mode and remove the hub.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Linux

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.