We help IT Professionals succeed at work.

Looking desperately for MYLEX extremeRAID 5000 Firmware (latest & greatest for SW-Kit v5.20). Any idea where to get (Avago can't help) ?

Hi, I am searching for the latest & greatest BIOS/Firmware Update for my MYLEX extremeRAID 5000 PCI-X Controller card.
I already looked everywhere, like lsilogic.com, IBM-Website & FTP, also http://www.avagotech.com , without any success.
Is there some user out there, who has the same PCI card and can email me the latest Firmware (FW) for SW-Kit v5.20.

I have all drivers and manuals for this card. I am also interested in a HW Reference Manual, explaining the Jumpers.
The IBM FRU Part# for the PCI Controller is 08P4283 (is also printed on the extremeRAID 5000 PCB).

Thanks !
Watch Question

Top Expert 2010

I wrote some of the configurators for the controllers.  (Sorry, do not have the firmware). I can tell you that if you are using the IBM part then only firmware formerly available from IBM will work.  There are a few bits that get set in the controller and firmware file to establish some compatibility (with other OEM-labeled controllers).

So even if you had firmware from the Avago site, that does not mean that there isn't some code embedded in the firmware image that would break the only-one-instance rule.

If I were you, i would consider backing up that machine and turning it into a virtual machine that runs under windows . Then you really wouldn't have issues with sense info.
Markus KalteneggerAdvanced Services Delivery Consultant (FC & SAN products)


Hello, first of all, thanks for your fast reply. Sorry that I could respond yesterday, I've been a busy bee here concerning an ongoing customer CritSit here in Germany. Currently, I could play around with this MYLEX card, I am at the stage to prepare myself to use it in the upcoming months. Maybe it will go into my older INTEL Sitka/Cabrillo SC450NX Server. Still don't know if Windows 2000 or 2003, let's see.

The only thing I found so far is this:
Mylex eXtremeRAID 2000 Optimized device driver version 7.05-01 and firmware update version 7.00-01

IBM eServer xSeries 440 and xSeries 445


File details
Version: 7.05-01, 7.00-1
Release Date: 2003-09-30

File link    -    File size - File description

26k3243.txt       7,643       README for the Mylex eXtremeRAID 2000 Optimized Device Driver version 7.05-01

26k3243.exe       98,679      Mylex eXtremeRAID 2000 Optimized Device Driver version 7.05-01

26k3244.txt       6,352       README for the Mylex eXtremeRAID 2000 Adapter Firmware Update disk 1 of 3 version 7.00-01

26k3244.exe       681,073     Mylex eXtremeRAID 2000 Adapter Firmware Update disk 1 of 3 version 7.00-01

26k3245.txt       6,376       README for the Mylex eXtremeRAID 2000 Adapter Firmware Update disk 2 of 3 version 7.00-01

26k3245.exe       671,708     Mylex eXtremeRAID 2000 Adapter Firmware Update disk 2 of 3 version 7.00-01

26k3246.txt       6,374       README for the Mylex eXtremeRAID 2000 Adapter Firmware Update disk 3 of 3 version 7.00-01

26k3246.exe       675,834     Mylex eXtremeRAID 2000 Adapter Firmware Update disk 3 of 3 version 7.00-01

This is surely *NOT* for the MYLEX extremeRAID 5000, the 2000 model is completely different. I also searched the IBM FTP Server ( ftp://public.dhe.ibm.com ), so far without success.

From Avago (who took all LSI & LSILOGIC assets together with Mylex) I got some final information, that they lost all binaries for the MYLEX extremeRAID 5000 for some reason. Due to the split, because some parts of MYLEX also went directly to Xyratex (and maybe other companies as well). Their BU (business unit) was more or less responsible for the web-content & Download archives are unfortunately not maintained for such an old product (back to Year 2001-2003).

The only thing I know about the 5000 Firmware: It was available in two (2) different flavors: a BBS-version and a non-BBS version (BBS stands for Boot-Block-Specification and it depends on the Server/PC BIOS, if its supports BBS or not.). Means, I look for both of these (ideally).

Maybe the "gap" between an older Firmware and the OS-drivers out of MYLEX's SW-Kit v5.20 is not so big, that this would prevent the PCI-X card from working (even if the actual Firmware I not om top ofg the latest firmware available) - let's see after my tests (in the upcoming weeks/months). Unfortunately I am very busy with customer projects & other private projects. So my time is often limited.

What I did not understand is the "only-one-instance" rule. What is it all about ?

I am still hoping that some other MYLEX extremeRAID 5000 user (I don't know how often IBM/Mylex have sold these cards) will read my request and helps me out.

Thanks in advance & Best regards
Top Expert 2010
That firmware is not going to work.  Here is the deal, even if you had the correct firmware image, there are a few dozen bytes embedded in the firmware file that have to be set to match the specific OEM make/model strings; a set of feature codes that turn some things on and off that don't work on all systems/enclosures; and set DMA/interrupt/addressing info.

I still have a copy of that program (I am still under NDA because I have one with both Avago and Xyratex), because this is one of the things I used to do ..  but I have no idea what the settings are supposed to be for your card.

Bottom line,  you're just going to have to source a working card with the right firmware and OEM customization.  (No you can't extract the firmware from a working card).

What is the real problem?    Is the card dead and your data is offline?   If THAT is the problem, I could dig up my old code that decodes the metadata and reconstruct the array, but that is the type of thing people used to pay me  thousands of dollars to do because it is non-trivial.

But if you can find a card with the SAME firmware or one that is not a major revision upgrade, then you can plug the disks into it and the controller will "learn" the config.  (But there are caveats, and you need to make backup. Furthermore, as the disks are probably quite old, it is important to do diagnostics to assess health prior to attempting this.  Otherwise you could end up with broken config and if you defined multiple LUNs it could break one and do a rebuild with the wrong drives).

So I will end it here.  You're just going to have to find a card with the right firmware (like if what you had was running 5.2 you can go to 5.99999 fine on replacement, but you can NOT go to any firmware >= 6.0.  You also can not go to any firmware < 5.2 in your case.

If you want to discuss data recovery, then you need to pay somebody to do it.