Linux Install Problem on Server

Hi all, thanks for this site

My problem is in installing Fedora FC10 onto a Intel SC450NX MP Server. This machine holds 6 36 Gig Seagate SCSI Hard Drives, 4 XEON III Processors and 4 gigs of memory.

I am having the exact same problem with two of these machines. Two other are running fine as online servers. These are meant to replace those whenever I get them to work. I've owned these since new, and were last used online with older Fedora versions and am attempting a clean install.

The problem I get is that after what appears to be a perfect install of the simplest default system, no raid, minimal config, the system stalls on reboot.

I read somewhere that this stall point is right when it goes to load the grub, but I'm not positive about that.

The drives are formatted with the choice of 'delete all existing partitions and use all space' (pardon my paraphrasing).

Previously I have installed and used ALL of this equipment, this is just a fresh install on a previously fine but old Fedora.

I'm thinking its some funky left over from previous install on the hard drives that isn't being cleaned up during reinstall:
Seagate ST336704LCV

But I'm really stumped. Any advice is greatly appreciated. Any command line advice needs details if possible as Linux is a second language to me Thanks!

Included are links to hardware and screenshot of where it stops booting

Intel Page with tech spec pdf links

Attached Thumbnails

   

almost looks like it doesn't like your RAID card. If you check the vendor website for drivers or try CentOS (like RHEL and Fedora)
Other things to check is crtl+F1 thought F6 should show you different aspects of the install look for more clues and get back to us...

There is no Raid Card, just SCSI support built in w/Symbios drivers that worked with Fedoras 1-9, but not with FC10. There is no RAID functionality in the bios. The system requires a hardware raid card with its own drivers (not present) or software raid (not trying to do that).

I actually started out doing a software raid config and when I saw this problem I thought it was a raid issue so I switched to the simplest generic install w/o raid and it still happens.

It isn't likely a driver gone bad on the system, as it would have to have gone bad on two identical systems at same time, possible but unlikely.

I read elsewhere that FC10 has a bug to this effect but no actual help as to getting past it.