boot kernel issue with raid controller and scsi cdrom
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
boot kernel issue with raid controller and scsi cdrom
I have a dell poweredge 2300 server and I am trying to install slack 9. When I boot using the raid.s kernel the raid controller is recognized but not the cdrom. When I use the adaptec.s scsi controller, the cdrom is detected but the raid controller is not set up.
There are a couple of possible approaches to this problem.
It would be, of course, possible to compile a different kernel for installation that included support for both of the SCSI cards/chipsets you need for the server and use it for a Slack boot floppy along with the Slack root disk and the CD or even to burn a new install CD including that kernel. This approach is not likely to be the simplest for you however.
What you should keep in mind is that this is a problem with installation and is not that likely to continue to be a problem after installation. We can start by asking the question, which driver do you need more for the installation? It would seem that you need the CDROM to read the install disk and the RAID array to have the system hard drives available. However, it would be possible to use another device on the system to serve either function. The next factor that enters in is what you want the end result to be. You want the computer, I would imagine, to boot from the RAID array, so that makes the driver for it the more important one. Then you just have to ask yourself what alternatives are there to installing the system from the CDROM that is on the server. It is possible to do a network install or to copy the installation files to a partition on the hard drive array using another OS. You should never, however, overlook the simplest approach. In your case this may be to hook up an IDE CDROM just long enough to get the system installed on the machine. Once the system is installed, you can most likely load the CDROM driver as a module during boot rather than having it built into the kernel. After this, there will be some configuration adjustments to point everything to the correct CDROM, but they will be minor. If you wish, or if it is necessary, you may wish to compile your own kernel for this machine once the operating system is up and running.
I found this thread which outlines a similar problem on a Proliant. I have actually had the same problem on Proliant machine, I chose the easy way: plug in an IDE CD-ROM (if that's an option for you, off course). I know a Proliant is not the same as a Poweredge, but I don't think the situation is very different.
you are both right. I need to see if I even have an IDE controller on this machine, I don't think I do. I think the partition idea is the best since I already have win 2k installed. I will just copy the needed files to a fat32 partition and when I am done make that my /home mount after reformating. Thanks for the replies.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.