I'm trying to do a fresh install on a new server that has a 3ware 9000 controller. I followed the instructions on the 3ware manual and used a floppy with the drivers for RH WS3 (Update 2) but it doesn't work. After it asks me to load the disk it reads for a while and then it says it did not find any drivers that pertain to this system. I tried loading the 3w9xxx driver unsuccesfully, it does no recognize the drives. Has anybody succesfully installed Centos-3 on a server with a 3ware 9000 controller? How? I have another machine that does not have a raid controller (and I'm installing Centos right now) that I can use to ciompile the drivers or whatever is needed.
Thanks in advance,
Adrian Madrid
---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.
On Sat, 18 Dec 2004 02:32:42 -0500, aemadrid@hyperxmedia.com aemadrid@hyperxmedia.com wrote:
I'm trying to do a fresh install on a new server that has a 3ware 9000 controller. I followed the instructions on the 3ware manual and used a floppy with the drivers for RH WS3 (Update 2) but it doesn't work.
Is the 9000 different from the bulk of the 3Ware product card? Because 3Ware drivers have been included with the kernel for a couple years now. I've never had to look outside my distro for them. Even on good old debian stable!
Francois
I'm trying to do a fresh install on a new server that has a 3ware 9000 controller. I followed the instructions on the 3ware manual and used a floppy with the drivers for RH WS3 (Update 2) but it doesn't work.
The RHES driver disk won't work (been there, done that!).
The driver disk for the 3ware 9500 for CentOS 3.3 can be downloaded at the link below (easy registration required):
http://www.integratedsolutions.org/drivers.html
If you need the driver disk for CentOS 3.1 reply again here and I'll try and find the one I have.
Jim
Thanks for the drivers, I was finally able to install CentOS on my server! The problem is now booting into it...
After a successfull install it boots but then fails to load the driver complaining about /lib/3w-9xxx.o saying it was buil for 2.3.21-20.ELsmp and this is 2.24.21-20.EL.c0smp. On booting I also have another option (CentOS 3.3-up, which I don't know the difference from plain CentOS 3.3) and this times it complains that the driver was build for 2.4.21-20.EL and this is 2.4.21-20.EL.c0. I guess I should have mentioned this is a dual Xeon machine. Please, I need help!
Thanks,
Adrian Madrid
Quoting "clook.NET - Staff" staff@clook.net:
I'm trying to do a fresh install on a new server that has a 3ware 9000 controller. I followed the instructions on the 3ware manual and used a
floppy
with the drivers for RH WS3 (Update 2) but it doesn't work.
The RHES driver disk won't work (been there, done that!).
The driver disk for the 3ware 9500 for CentOS 3.3 can be downloaded at the link below (easy registration required):
http://www.integratedsolutions.org/drivers.html
If you need the driver disk for CentOS 3.1 reply again here and I'll try and find the one I have.
Jim
CentOS mailing list CentOS@caosity.org http://lists.caosity.org/mailman/listinfo/centos
---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.
-----Original Message----- From: centos-admin@caosity.org [mailto:centos-admin@caosity.org] On Behalf Of aemadrid@hyperxmedia.com Sent: Saturday, December 18, 2004 5:27 PM To: clook.NET - Staff Cc: CentOS@caosity.org Subject: Re: [Centos] 3ware 9000 install
Thanks for the drivers, I was finally able to install CentOS on my server! The problem is now booting into it...
After a successfull install it boots but then fails to load the driver complaining about /lib/3w-9xxx.o saying it was buil for 2.3.21-20.ELsmp and this is 2.24.21-20.EL.c0smp. On booting I also have another option (CentOS 3.3-up, which I don't know the difference from plain CentOS 3.3) and this times it complains that the driver was build for 2.4.21-20.EL and this is 2.4.21-20.EL.c0. I guess I should have mentioned this is a dual Xeon machine. Please, I need help!
Thanks,
Adrian Madrid
Quoting "clook.NET - Staff" staff@clook.net:
I'm trying to do a fresh install on a new server that has
a 3ware 9000
controller. I followed the instructions on the 3ware
manual and used a
floppy
with the drivers for RH WS3 (Update 2) but it doesn't work.
The RHES driver disk won't work (been there, done that!).
The driver disk for the 3ware 9500 for CentOS 3.3 can be
downloaded at
the link below (easy registration required):
http://www.integratedsolutions.org/drivers.html
If you need the driver disk for CentOS 3.1 reply again here and I'll try and find the one I have.
Jim
The driver install disks (floppy Image) we posted were for 32 bit CentOS 3.3 (Kernel 2.4.21-20) for 32 bit machines based on the "i686 athlon" architecture ONLY.
Your architecture can be found by running uname -a
Ours reads:
Linux pos1 2.4.21-15.0.4.ELsmp #1 SMP Wed Aug 4 13:29:51 EDT 2004 i686 athlon i386 GNU/Linux
For our whitebox web test machine named "pos1"
With that said here is how to get your dual Xeon machine working correctly:
Boot the machine using the up (uniprocessor - one processor) kernel that comes up but says the driver is built for the wrong kernel ( we used whitebox to build the driver but the kernel is the same and will work fine ). The boot process will give you a warning about a tainted driver but will work OK
Download the latest 3w-9xxx.tgz source code file from www.3ware.com
Put this in a directory somewhere and run from that directory: tar -xzvf <filename>
This will uncompress and untar the source files.
Next you need to set up the kernel source tree.
Install the kernel source from rpm if its not already there
cd /usr/src/"kernel-rev" ("kernel-rev" is the directory where the source was installed) edit the Makefile and change the line that reads: (4 th line down) EXTRAVERSION = -15.0.4.El.c0custom
To the kernel extension of your smp system:
Something like : EXTRAVERSION = -15.0.4.El.c0smp
make mrproper make oldconfig make dep make clean
The kernel source tree is now set up for your smp kernel
Go back to the driver source directory and and run "make -f Makefile.rh smp"
This will create a file "3w-9xxx.smp"
You will need to copy this into the /lib/modules/2.4.21-15.0.4.EL.c0smp/kernel/drivers/scsi directory and rename it "3w-9xxx.o"
There should be an extry in /etc/modules.conf that reads: alias scsi_hostadapter 3w-9xxx
If not add it at the beginning. If you have other SCSI adapters in the system already you will need to set this alias up correctly with a number after it - ie: alias scsi_hostadapterX where X is the correct number, no number for SCSI0.
Once this is done you will need to run mkinitrd to create a new initrd image. The command will look something like this:
mkinitrd /boot/initrd-2.4.21-15.0.4.EL.c0smp_test.img 2.4.21-15.0.4.EL.c0smp
This will put a file into /boot called "initrd-2.4.21-15.0.4.EL.c0smp_test.img"
Now edit your /boot/grub/grub.conf file and copy the whole smp entry and paste it below the existing entry. Change the title line to something like test_smp and change the initrd entry to the new initrd file name. Reboot and see if you select the test_smp entry if the machine boots properly. If it does then you can use the new initrd image in place of the old one and your all set to go.
If this is too complicated then you will need to research the above process, become familiar with it. Google is your friend. Also look at the /usr/src/kernel-rev/Documentation directory for lots of helpful information in the text files.
We don't have a dual xeon machine sitting around to do this for you or I would have just done it and put the driver into a boot disk floppy image.
We don't sell many dual xeons any more because the dual opteron systems cost less and provide much more performance.
The above procedure is in the 3ware release notes with some modifications but it is complex and requires a significant knowledge of driver building and a lot of basic linux know-how.
Read through this a few times to get familiar with it. ALWAYS make copies of any file you are going to modify or change to help recover from a bad edit.
If all else fails call us. We will walk you through it.
Best,
Seth Bardash
Integrated Solutions and Systems 1510 North Gate Road Colorado Springs, CO 80921
719-495-5866 719-495-5870 Fax 719-337-4779 Cell
Thanks for the information, it was clear and easy to follow through it. Although I wasn't able to boot using the up kernel with your drivers installed I figured I should try something different. I installed an ide drive directly into the motherboard and installed CentOS 3.3 without any special drivers. Once I was in I followed your instructions and got a booting version but, unfortunately, it still has a lot of unresolved symbols and the drivers does not load. Now it still boots because there is a _normal_ hard drive to boot from but I can't make the 3w-9xxx driver load at all. lsmod reports it's not loaded and modprobe barks about a boatload of unresolved symbols. It's 1am in the morning and I can't figure out where to run to or what else new I can try. In summary, I can boot from a normal HD, although I will have to get rid of it in the end, but no 3w-9xxx module loaded. HELP! What can I do to get rid of unresolved symbols?
Thanks again,
Adrian Madrid
Quoting Seth Bardash seth@integratedsolutions.org:
-----Original Message----- From: centos-admin@caosity.org [mailto:centos-admin@caosity.org] On Behalf Of aemadrid@hyperxmedia.com Sent: Saturday, December 18, 2004 5:27 PM To: clook.NET - Staff Cc: CentOS@caosity.org Subject: Re: [Centos] 3ware 9000 install
Thanks for the drivers, I was finally able to install CentOS on my server! The problem is now booting into it...
After a successfull install it boots but then fails to load the driver complaining about /lib/3w-9xxx.o saying it was buil for 2.3.21-20.ELsmp and this is 2.24.21-20.EL.c0smp. On booting I also have another option (CentOS 3.3-up, which I don't know the difference from plain CentOS 3.3) and this times it complains that the driver was build for 2.4.21-20.EL and this is 2.4.21-20.EL.c0. I guess I should have mentioned this is a dual Xeon machine. Please, I need help!
Thanks,
Adrian Madrid
Quoting "clook.NET - Staff" staff@clook.net:
I'm trying to do a fresh install on a new server that has
a 3ware 9000
controller. I followed the instructions on the 3ware
manual and used a
floppy
with the drivers for RH WS3 (Update 2) but it doesn't work.
The RHES driver disk won't work (been there, done that!).
The driver disk for the 3ware 9500 for CentOS 3.3 can be
downloaded at
the link below (easy registration required):
http://www.integratedsolutions.org/drivers.html
If you need the driver disk for CentOS 3.1 reply again here and I'll try and find the one I have.
Jim
The driver install disks (floppy Image) we posted were for 32 bit CentOS 3.3 (Kernel 2.4.21-20) for 32 bit machines based on the "i686 athlon" architecture ONLY.
Your architecture can be found by running uname -a
Ours reads:
Linux pos1 2.4.21-15.0.4.ELsmp #1 SMP Wed Aug 4 13:29:51 EDT 2004 i686 athlon i386 GNU/Linux
For our whitebox web test machine named "pos1"
With that said here is how to get your dual Xeon machine working correctly:
Boot the machine using the up (uniprocessor - one processor) kernel that comes up but says the driver is built for the wrong kernel ( we used whitebox to build the driver but the kernel is the same and will work fine ). The boot process will give you a warning about a tainted driver but will work OK
Download the latest 3w-9xxx.tgz source code file from www.3ware.com
Put this in a directory somewhere and run from that directory: tar -xzvf
<filename>
This will uncompress and untar the source files.
Next you need to set up the kernel source tree.
Install the kernel source from rpm if its not already there
cd /usr/src/"kernel-rev" ("kernel-rev" is the directory where the source was installed) edit the Makefile and change the line that reads: (4 th line down) EXTRAVERSION = -15.0.4.El.c0custom
To the kernel extension of your smp system: Something like : EXTRAVERSION = -15.0.4.El.c0smp
make mrproper make oldconfig make dep make clean
The kernel source tree is now set up for your smp kernel
Go back to the driver source directory and and run "make -f Makefile.rh smp"
This will create a file "3w-9xxx.smp"
You will need to copy this into the /lib/modules/2.4.21-15.0.4.EL.c0smp/kernel/drivers/scsi directory and rename it "3w-9xxx.o"
There should be an extry in /etc/modules.conf that reads: alias scsi_hostadapter 3w-9xxx
If not add it at the beginning. If you have other SCSI adapters in the system already you will need to set this alias up correctly with a number after it - ie: alias scsi_hostadapterX where X is the correct number, no number for SCSI0.
Once this is done you will need to run mkinitrd to create a new initrd image. The command will look something like this:
mkinitrd /boot/initrd-2.4.21-15.0.4.EL.c0smp_test.img 2.4.21-15.0.4.EL.c0smp
This will put a file into /boot called "initrd-2.4.21-15.0.4.EL.c0smp_test.img"
Now edit your /boot/grub/grub.conf file and copy the whole smp entry and paste it below the existing entry. Change the title line to something like test_smp and change the initrd entry to the new initrd file name. Reboot and see if you select the test_smp entry if the machine boots properly. If it does then you can use the new initrd image in place of the old one and your all set to go.
If this is too complicated then you will need to research the above process, become familiar with it. Google is your friend. Also look at the /usr/src/kernel-rev/Documentation directory for lots of helpful information in the text files.
We don't have a dual xeon machine sitting around to do this for you or I would have just done it and put the driver into a boot disk floppy image.
We don't sell many dual xeons any more because the dual opteron systems cost less and provide much more performance.
The above procedure is in the 3ware release notes with some modifications but it is complex and requires a significant knowledge of driver building and a lot of basic linux know-how.
Read through this a few times to get familiar with it. ALWAYS make copies of any file you are going to modify or change to help recover from a bad edit.
If all else fails call us. We will walk you through it.
Best,
Seth Bardash
Integrated Solutions and Systems 1510 North Gate Road Colorado Springs, CO 80921
719-495-5866 719-495-5870 Fax 719-337-4779 Cell
-- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.296 / Virus Database: 265.6.0 - Release Date: 12/17/2004
---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.
Thanks for the drivers, I was finally able to install CentOS on my server! The problem is now booting into it...
I hadn't actually used the drivers at the link provided and didn't know they were based on athlon.
I see another post has been sent with the process you need to do. Alternatively, if you have the CentOS 3.1 ISO's you can install that and use the driver disk at the link below (which I know works with this OS version)
Following the install you should be able to just do 'yum update' to take the OS to 3.3 (see the 3ware manual on the process for manually compiling the driver for future kernels).
Jim
Thnaks for the info. I don't have the 3.1 ISOs at hand so I will give the full process a try.
Thanks again,
Adrian Madrid
Quoting Jim staff@clook.net:
Thanks for the drivers, I was finally able to install CentOS on my server!
The
problem is now booting into it...
I hadn't actually used the drivers at the link provided and didn't know they were based on athlon.
I see another post has been sent with the process you need to do. Alternatively, if you have the CentOS 3.1 ISO's you can install that and use the driver disk at the link below (which I know works with this OS version)
Following the install you should be able to just do 'yum update' to take the OS to 3.3 (see the 3ware manual on the process for manually compiling the driver for future kernels).
Jim
CentOS mailing list CentOS@caosity.org http://lists.caosity.org/mailman/listinfo/centos
---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.