My goal is to be able to install to the drive array on the 3Ware controller card. 3Ware does provide a RH WS 3 driver that I've tried to use; however, the RH Enterprise 3 WS driver doesn't work since that kernel is older than the CentOS-3.1 install kernel.
I'm trying to create a centOS-3.1 installation driver disk for the 3ware 9500S card; however, I'm not having much luck. I've compiled the drivers on a stock centOS 3.1 install and created a modules.cgz file (using find . -depth | cpio -o -H newc | gzip -c > ../modules.cgz) with the newly-compiled driver modules. Here are the contents of the modules.cgz file I created: 2.4.21-9.0.1.EL.c0BOOT/i386/3w-9xxx.o 2.4.21-9.0.1.EL.c0hugemem/i386/3w-9xxx.o 2.4.21-9.0.1.EL.c0/i386/3w-9xxx.o 2.4.21-9.0.1.EL.c0smp/i386/3w-9xxx.o
I've also tried the above without the 'i386' subdirectory.
The stock install kernel version is 2.4.21-9.0.1.EL.c0. That IS what I should use for the modules directory name right? I then created a driver disk with the following files: modinfo modules.cgz modules.dep pcitable rhdd-6.1 src
When I boot the install CD, I type: "linux dd". I then tell the installer that the drivers are on fd0. The installer reads the disk, but doesn't find the driver and gives me this message: "No devices of the appropriate type were found on this driver disk. Would you like to manually select the driver, continue anyway, or load another driver disk?"
Does anybody know what I'm doing wrong? Am I going about this the hard way?
Thanks in advance for any suggestions! -Sean
Looking at the 3ware driver disk here is the content
zcat modules.cgz | cpio -ivd 2.4.21-4.EL/3w-9xxx.o 2.4.21-4.ELBOOT/3w-9xxx.o 2.4.21-4.ELhugemem/3w-9xxx.o 2.4.21-4.ELsmp/3w-9xxx.o notice... no i386 directory Plus...the only i386 kernel is the BOOT kernel...please build the correct driver for i686 or athlon...depending on your system
modinfo modules.cgz modules.dep pcitable rhdd-6.1 src/ src/2.4/ src/2.4/3w-9xxx.tgz
Try using the the driver disk from 3ware replacing the modules.cgz.
DP
Sean Staats wrote:
My goal is to be able to install to the drive array on the 3Ware controller card. 3Ware does provide a RH WS 3 driver that I've tried to use; however, the RH Enterprise 3 WS driver doesn't work since that kernel is older than the CentOS-3.1 install kernel.
I'm trying to create a centOS-3.1 installation driver disk for the 3ware 9500S card; however, I'm not having much luck. I've compiled the drivers on a stock centOS 3.1 install and created a modules.cgz file (using find . -depth | cpio -o -H newc | gzip -c > ../modules.cgz) with the newly-compiled driver modules. Here are the contents of the modules.cgz file I created: 2.4.21-9.0.1.EL.c0BOOT/i386/3w-9xxx.o 2.4.21-9.0.1.EL.c0hugemem/i386/3w-9xxx.o 2.4.21-9.0.1.EL.c0/i386/3w-9xxx.o 2.4.21-9.0.1.EL.c0smp/i386/3w-9xxx.o
I've also tried the above without the 'i386' subdirectory.
The stock install kernel version is 2.4.21-9.0.1.EL.c0. That IS what I should use for the modules directory name right? I then created a driver disk with the following files: modinfo modules.cgz modules.dep pcitable rhdd-6.1 src
When I boot the install CD, I type: "linux dd". I then tell the installer that the drivers are on fd0. The installer reads the disk, but doesn't find the driver and gives me this message: "No devices of the appropriate type were found on this driver disk. Would you like to manually select the driver, continue anyway, or load another driver disk?"
Does anybody know what I'm doing wrong? Am I going about this the hard way?
Thanks in advance for any suggestions! -Sean
CentOS mailing list CentOS@caosity.org http://www.caosity.org/mailman/listinfo/centos
*What I'm trying to do: ----------------------- Install CentOS 3.1 to a RAID 5 array consisting of 4 drives attached to a 3ware 9500S-4LP which will be the boot device.
*Error I'm getting (when installer tries formatting a partition): ----------------------------------------------------------------- Code: 0f 0b 2b 01 10 b2 24 c0 58 5a eb fe 89 f6 8a 54 24 04 8d 42 Kernel panic: Fatal exception In interrupt handler - not syncing
*Hardware specs: ---------------- Supermicro SuperServer 6013P-T with 2 2.6GHz Xeon CPUS, 4GB RAM, and 4 250GB Western Digital SATA drives attached to a 3ware 9500S-4LP in RAID 5 mode.
*What I've done so far: ----------------------- I've successfully created a driver disk in that the installation utility successfully loads the 3w-9xxx driver module and continues the install process. I am then able to create partitions on the array. But once the installation utility starts formatting the first partition, the kernel panics with the following message: Code: 0f 0b 2b 01 10 b2 24 c0 58 5a eb fe 89 f6 8a 54 24 04 8d 42 Kernel panic: Fatal exception In interrupt handler - not syncing
Here are the steps I followed to try to install the OS: *Note - steps 1-6 were all done on a stock CentOS 3.1 system without a 3ware card.
1) Download the following files from 3ware.com: ws3__x86.tgz (Install disk files) 3w-9xxx.tgz (Linux 2.4 Kernel Driver Source)
2) Create installation driver disk: Format a 3.5 inch floppy(with msdos filesystem) mount /mnt/floppy tar xzf ws3__x86.tgz -C /mnt/floppy
3) Compile the 3w-9xxx driver (i686): tar xzf 3w-9xxx.tgz cd driver make -f Makefile.rh make smp -f Makefile.rh make bot -f Makefile.rh make hug -f Makefile.rh cd ..
4) Create directories and copy in compiled drivers: mkdir modules cd modules mkdir 2.4.21-9.0.1.EL.c0 cp ../driver/3w-9xxx.o 2.4.21-9.0.1.EL.c0/3w-9xxx.o mkdir 2.4.21-9.0.1.EL.c0BOOT cp ../driver/3w-9xxx.bot 2.4.21-9.0.1.EL.c0BOOT/3w-9xxx.o mkdir 2.4.21-9.0.1.EL.c0hugemem cp ../driver/3w-9xxx.hug 2.4.21-9.0.1.EL.c0hugemem/3w-9xxx.o mkdir 2.4.21-9.0.1.EL.c0smp cp ../driver/3w-9xxx.smp 2.4.21-9.0.1.EL.c0smp/3w-9xxx.o
5) Create a new modules.cgz file (replacing one on floppy): find . -depth | cpio -o -H newc | gzip -c > /mnt/floppy/modules.cgz
6) Unmount floppy disk: umount /mnt/floppy
7) Use the new driver disk when installing CentOS 3.1: At the installation linux boot prompt type 'linux dd'
Then from there, have the installation utility use the driver floppy, and continue with the installation. One can create partitions on the array, but the kernel panics when trying to format the first partition.
I've verified that Windows XP does install on the same machine. So I don't think there are any hardware incompatibilities.
Any insight and help to resolve this is greatly appreciated.
Thanks! -Sean
On Fri, 2004-07-09 at 07:42, centos-admin@caosity.org wrote:
Looking at the 3ware driver disk here is the content
zcat modules.cgz | cpio -ivd 2.4.21-4.EL/3w-9xxx.o 2.4.21-4.ELBOOT/3w-9xxx.o 2.4.21-4.ELhugemem/3w-9xxx.o 2.4.21-4.ELsmp/3w-9xxx.o notice... no i386 directory Plus...the only i386 kernel is the BOOT kernel...please build the correct driver for i686 or athlon...depending on your system
modinfo modules.cgz modules.dep pcitable rhdd-6.1 src/ src/2.4/ src/2.4/3w-9xxx.tgz
Try using the the driver disk from 3ware replacing the modules.cgz.
DP
Sean Staats wrote:
My goal is to be able to install to the drive array on the 3Ware controller card. 3Ware does provide a RH WS 3 driver that I've tried to use; however, the RH Enterprise 3 WS driver doesn't work since that kernel is older than the CentOS-3.1 install kernel.
I'm trying to create a centOS-3.1 installation driver disk for the 3ware 9500S card; however, I'm not having much luck. I've compiled the drivers on a stock centOS 3.1 install and created a modules.cgz file (using find . -depth | cpio -o -H newc | gzip -c > ../modules.cgz) with the newly-compiled driver modules. Here are the contents of the modules.cgz file I created: 2.4.21-9.0.1.EL.c0BOOT/i386/3w-9xxx.o 2.4.21-9.0.1.EL.c0hugemem/i386/3w-9xxx.o 2.4.21-9.0.1.EL.c0/i386/3w-9xxx.o 2.4.21-9.0.1.EL.c0smp/i386/3w-9xxx.o
I've also tried the above without the 'i386' subdirectory.
The stock install kernel version is 2.4.21-9.0.1.EL.c0. That IS what I should use for the modules directory name right? I then created a driver disk with the following files: modinfo modules.cgz modules.dep pcitable rhdd-6.1 src
When I boot the install CD, I type: "linux dd". I then tell the installer that the drivers are on fd0. The installer reads the disk, but doesn't find the driver and gives me this message: "No devices of the appropriate type were found on this driver disk. Would you like to manually select the driver, continue anyway, or load another driver disk?"
Does anybody know what I'm doing wrong? Am I going about this the hard way?
Thanks in advance for any suggestions! -Sean
CentOS mailing list CentOS@caosity.org http://www.caosity.org/mailman/listinfo/centos
CentOS mailing list CentOS@caosity.org http://www.caosity.org/mailman/listinfo/centos
On Fri, 16 Jul 2004, Sean Staats wrote:
*Hardware specs:
Supermicro SuperServer 6013P-T with 2 2.6GHz Xeon CPUS, 4GB RAM, and 4 250GB Western Digital SATA drives attached to a 3ware 9500S-4LP in RAID 5 mode.
If this means that the 3ware 9500S-4LP is also accessed by the 6013P-T as a SATA device:
My experience with SATA devices is that the kernel is able to access them correctly, boot from them, etc. but that the installer can't deal with it (at least not without appendding SATA device driver modules to the boot parameters) and that lilo et al. have trouble writing correct boot sectors to SATA devices.
My only success with installing CentOS, RH9, or Fedora-1 on a machine with a SATA boot disk has been by first dropping into the motherboard setup and setting the ATA/IDE to "legacy" mode so that the SATA device appears as a standard IDE, then switching back to "enhanced" mode after the install was complete.
I have to go through this again with the rescue CD every time there's a CentOS kernel upgrade, to get the boot loader installed correctly.
What is the best choice to upgrade my P133 32MB Machine (only running dhcp server, wins and fetchmail) caos-1 or centos 2 final ? I lost my link to upgrade via yum howto, could someone provide one ?
Best Regards Kuba
I wrote a how to for rh 9 to centos 3.1, you's should be similar, best of luck! Let us know how it goes and i'd be happy to help if you need a hand.
How-To: http://www.webhostingtalk.com/showthread.php?s=&threadid=276534
You could try getting yum from centos-2 and running it to see what happens. Centos-2 is like RH72 so much of it is same versions and yum will not want to upgrade, this should not be a major problem because if the packages are the same version they should have the same contents. You might have problems with RH73 because it is newer than CentOS-2 so in effect to perform an upgrade you would have to install older packages. I don't know if yum can do that.
I would recommend the best way is backup your config files and reinstall you chosen OS.
No matter what you do, make sure you backup first so if things go bad you can recover.
John.
Jakub Wojtanowski wrote:
What is the best choice to upgrade my P133 32MB Machine (only running dhcp server, wins and fetchmail) caos-1 or centos 2 final ? I lost my link to upgrade via yum howto, could someone provide one ?
Best Regards Kuba
CentOS mailing list CentOS@caosity.org http://www.caosity.org/mailman/listinfo/centos
On Wed, 14 Jul 2004, Jakub Wojtanowski wrote:
What is the best choice to upgrade my P133 32MB Machine (only running dhcp server, wins and fetchmail) caos-1 or centos 2 final ? I lost my link to upgrade via yum howto, could someone provide one ?
a host with 32M of ram will not like using yum very well; caos-1 is probably a better choice for a 586 processor
http://www.owlriver.com/tips/centos-31-ex-rhl-9/
has links to each of my writeups for several types of representative migrations and upgrades
-- Russ Herrold
On Fri, 16 Jul 2004, R P Herrold wrote:
On Wed, 14 Jul 2004, Jakub Wojtanowski wrote:
What is the best choice to upgrade my P133 32MB Machine (only running dhcp server, wins and fetchmail) caos-1 or centos 2 final ? I lost my link to upgrade via yum howto, could someone provide one ?
a host with 32M of ram will not like using yum very well; caos-1 is probably a better choice for a 586 processor
http://www.owlriver.com/tips/centos-31-ex-rhl-9/
has links to each of my writeups for several types of representative migrations and upgrades
Still you can use apt with only 32MB of RAM instead of yum. I'm not sure if cAos or CentOS support apt, but this would be a good reason in support of apt.
-- dag wieers, dag@wieers.com, http://dag.wieers.com/ -- [Any errors in spelling, tact or fact are transmission errors]
-
Bart Schaefer -
Beau Henderson -
Dag Wieers -
Denis Pilon -
Jakub Wojtanowski -
John Newbigin -
R P Herrold -
Sean Staats