We have created a Centos 9500S Floppy Boot Disk for installing Centos on a 3ware 9500S series controller that will allow installing and booting directly from this controller.
This boot disk supports only AMD XP, MP and Opterons in 32 bit mode Centos 3.4 for the up and smp versions.
We can also do a x86_64 version if required.
Any interest????
If so we will post it to our web site.
Thanks
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
http://www.integratedsolutions.org
Failure can not cope with perseverance!
----- Original Message ----- From: "Seth Bardash" seth@integratedsolutions.org Sent: Tuesday, April 26, 2005 11:47 AM Subject: [CentOS] Centos 3.4 3ware 9500S Floppy Boot Disk
We have created a Centos 9500S Floppy Boot Disk for installing Centos on a 3ware 9500S series controller that will allow installing and booting directly from this controller.
This boot disk supports only AMD XP, MP and Opterons in 32 bit mode Centos 3.4 for the up and smp versions.
We can also do a x86_64 version if required.
Any interest????
If so we will post it to our web site.
YES!! Please post it.
BTW, how about CenOS 4? have you tested it with the new version?
Chris
Centos 4.0 has the driver built in.
We recommend you install 4.0 and then build the latest (9.2) driver and firmware from source (you must set up your kernel source tree to match the running kernel).
Build it with the firmware in the driver so that at the next boot it will upgrade the firmware. See 3ware's web site on how to do this. We will be adding a page that describes this in detail in the future.
Once built, you need to copy it to the appropriate /lib/modules/kernel_version/kernel/drivers/scsi directory.
Then run mkinitrd to create a new initrd image. Name it something else that is NOT the default.
edit grub.conf and add a copy of the existing boot entry but change the initrd image entry to match the new image created above.
Reboot and test it to make sure it works fine. If it does then save the old image as file.old and name the new one the same name as the original old one. Then delete the grub.conf entry you made for testing and you will be good to go.
After you have all this running then install the latest version of 3dm2 from 3ware's site.
Best
Seth Bardash
Integrated Solutions and Systems
719-495-5866
Failure can not cope with perseverance!
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org] On Behalf Of centos.org_list@000a.com Sent: Tuesday, April 26, 2005 12:57 PM To: CentOS mailing list Subject: Re: [CentOS] Centos 3.4 3ware 9500S Floppy Boot Disk
----- Original Message ----- From: "Seth Bardash" seth@integratedsolutions.org Sent: Tuesday, April 26, 2005 11:47 AM Subject: [CentOS] Centos 3.4 3ware 9500S Floppy Boot Disk
We have created a Centos 9500S Floppy Boot Disk for installing Centos on a 3ware 9500S series controller that will allow installing and booting directly from this controller.
This boot disk supports only AMD XP, MP and Opterons in 32 bit mode Centos 3.4 for the up and smp versions.
We can also do a x86_64 version if required.
Any interest????
If so we will post it to our web site.
YES!! Please post it.
BTW, how about CenOS 4? have you tested it with the new version?
Chris
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On Tue, 26 Apr 2005 at 3:05pm, Seth Bardash wrote
Centos 4.0 has the driver built in.
We recommend you install 4.0 and then build the latest (9.2) driver and firmware from source (you must set up your kernel source tree to match the running kernel).
Build it with the firmware in the driver so that at the next boot it will upgrade the firmware. See 3ware's web site on how to do this. We will be adding a page that describes this in detail in the future.
Once built, you need to copy it to the appropriate /lib/modules/kernel_version/kernel/drivers/scsi directory.
Then run mkinitrd to create a new initrd image. Name it something else that is NOT the default.
edit grub.conf and add a copy of the existing boot entry but change the initrd image entry to match the new image created above.
Reboot and test it to make sure it works fine. If it does then save the old image as file.old and name the new one the same name as the original old one. Then delete the grub.conf entry you made for testing and you will be good to go.
After you have all this running then install the latest version of 3dm2 from 3ware's site.
All good advice, except for the fact that upgrading my daul 9500-12 system from the 9.1.5.2 codebase/stock centos-4 driver to the 9.2 codebase (including driver) utterly killed the performance. The 9500s are set up as RAID5 w/ a hot spare, and I do a software RAID0 stripe across them. These are tiobench numbers before "upgrading" (units are MB/s):
Read, 1 thread: 428.8 Read, 2 thread: 586.7 Read, 4 thread: 541.5 Read, 8 thread: 462.9
Write, 1 thread: 151.7 Write, 2 thread: 156.8 Write, 4 thread: 148.6 Write, 8 thread: 148.5
And after:
Read, 1 thread: 433.4 Read, 2 thread: 608.1 Read, 4 thread: 508.6 Read, 8 thread: 398.6
Write, 1 thread: 33.7 Write, 2 thread: 31.6 Write, 4 thread: 31.4 Write, 8 thread: 30.5
The bonnie++ results look even worse:
"Old" codeset: Read: 340.6 Write: 173.5
"New" codeset: Read: 134.5 Write: 35.6
I've got a request into 3ware for support, but no response yet.
-
centos.org_list＠000a.com -
Joshua Baker-LePain -
Seth Bardash