Topic: 3ware upgrading drivers

[Max]

We have built a lot of e-smith/SME systems using 3ware's 6000 series hardware raid card. They seem to have a very good product but lately we seeing a lot of RAID arrays becom degraded. I talked to 3ware tech support and they said we were running a very old version of firmware and drivers, and that we should upgrade. Herein lies the problem:

The only hand out upgraded object files (3w-xxxx.o) for redhat 6.2, 7.1 and 7.2
and SME is redhat 7.1 but with the kernel from 7.0 if I am not mistaken. I am trying to build a straight redhat 7.0 machine so I can recompile the driver (as per 3ware's suggestion) but I am wondering if there is an easier way or if someone has already done this. I have done some web searches and I am not finding anything.

Help?

-Max

[Darrell May]

They also provide the 2.2 and 2.4 source files.  Use the 2.2 source files to build the driver you need.

1) Download and install everything found here:

http://myezserver.com/downloads/mitel/contrib/dev-tools/

2) Download from 3ware their file named rh62_7x.zip.  Unzip  and look in the /src/2.2/3w-xxxx.tgz

3) Follow the instructions in compile.txt

Regards,

Darrell

[Tom Keiser]

A very nice gentleman on the devinfo list named Brad Hards was kind enough to compile the 7000-series driver for me, and you are more than welcome to a copy of that. It works beautifully. However, I do not have the 6000-series driver for 5.1.2. And yes, the driver included with SME *WILL NOT* work properly with the new firmware or 3dm web-page utility.

[Max]

Thanks very much for the link. I downloaded and installed all those rpms on a fresh sme 5.1.2 install. the driver then compiled with no problems.

BUT, I am still not up and running. I had to deviate from the directions a little but I dont think I did anything that would break it. Here is what I did:
1) copied the new 3w-xxxx.o into /lib/modules/2.2.19-7.0.8/scsi
2) cd /boot
3) made a backup of initrd-2.2.19-7.0.8.img (how does this help? since I hosed the system?)
4) mv initrd-2.2.19-7.0.8.img to initrd.img.gz and then gunzip'ed it
5) mount -o loop initrd.img /mnt/cdrom (here is where I deviated because it said I couldnt mount to tmp because it didnt exist)
6) cd /mnt/cdrom/lib
7) copy the new 3w-xxxx.o into lib, replacing the old one
sync;sync;sync
9) cd /boot then unmount /mnt/cdrom
10) gzip -9 initrd.img
11) mv initrd.img initrd-2.2.19-7.0.8.img
12) lilo (this step complained, maybe that is my problem?)
13) reboot and boot halts on RAMDISK: compressed image found at block 0

any ideas? I am going to try figuring out the lilo thing

[Max]

OK it was indeed lilo complaining.
I did it again and this time lilo did not complain and it booted up just fine, but with some warnings about not finding other modules:

Apr 23 14:46:23 multiserver rc.sysinit: Remounting root filesystem in read-write mode:  succeeded
Apr 23 14:46:26 multiserver depmod: depmod:
Apr 23 14:46:26 multiserver depmod: *** Unresolved symbols in /lib/modules/2.2.19-7.0.8/misc/ipsec.o
Apr 23 14:46:26 multiserver rc.sysinit: Finding module dependencies:  succeeded
Apr 23 14:46:26 multiserver depmod: depmod: *** Unresolved symbols in /lib/modules/2.2.19-7.0.8/scsi/megaide.o
Apr 23 14:46:27 multiserver fsck: /boot: clean, 30/4016 files, 3709/16033 blocks

are these a problem?
the only thing I did differently was instead of sync;sync;sync, I ran them on seperate lines... I am going to try again and see if that truly is the key that makes it work or not.
Any ideas on the boot message errors?

[Max]

OK it was indeed lilo complaining.
I did it again and this time lilo did not complain and it booted up just fine, but with some warnings about not finding other modules:

Apr 23 14:46:23 multiserver rc.sysinit: Remounting root filesystem in read-write mode:  succeeded
Apr 23 14:46:26 multiserver depmod: depmod:
Apr 23 14:46:26 multiserver depmod: *** Unresolved symbols in /lib/modules/2.2.19-7.0.8/misc/ipsec.o
Apr 23 14:46:26 multiserver rc.sysinit: Finding module dependencies:  succeeded
Apr 23 14:46:26 multiserver depmod: depmod: *** Unresolved symbols in /lib/modules/2.2.19-7.0.8/scsi/megaide.o
Apr 23 14:46:27 multiserver fsck: /boot: clean, 30/4016 files, 3709/16033 blocks

are these a problem?
the only thing I did differently was instead of sync;sync;sync, I ran them on seperate lines... I am going to try again and see if that truly is the key that makes it work or not.
Any ideas on the boot message errors?