|
Dell Poweredge 2400 + Suse 9.0 (or: Why doesn't it remember the driver module!)
After the spending the past few weeks feeling my way through setting up Linux on a test machine in the office, I got set the task of setting up an old server, a Dell Poweredge 2400 / 533 to run as a webserver. On the test machine this was a piece of pie. We'd chosen Suse for a distro primarily because we use Novell backend, and with Novell owning Suse we figured we might get better support in the future.
So.. I stick my nice Suse disk in the drive and start the install process, only to discover it can't see the RAID controller. If you hit an abort it takes you to the old YaST1 interface, from which you can specify a custom controller to load. I quickly discovered aacraid.o is the module / driver I need to access the SCSI RAID.
So there I am, happily installing the software after spending 10 minutes customising the install to ensure it only loaded what I really needed. As is the norm with Suse, once it had finished the first disk it wanted to boot the installed system ready to continue on with the next disks. It rebooted.... and fell over. Can't read the SCSI RAID. Yup, even though I'd specifically asked it to load that module, it doesn't add it to the initrd that it installs. Smart. Stuffed server. After digging around I discovered that you need to do an update disk, so I created one. Now either I'm stupid or I stuffed it up because that made about zip all difference (I learnt from my mistakes this time.. just did the bare minimum graphical install to save time).
Has anyone had any success in installing Suse 9.0 onto a Dell server, and tackled similar issues?
For the record, RH9 installed fine.
Last edited by Garp; 04-02-2004 at 02:48 AM.
|
.
