LSI Controller FW updates IR/IT modes


Recommended Posts

You can determine the state of the array with this command ...

 

/root/mdcmd status|strings|grep "mdState"

 

I was exporting to a file first, like yours better, in either senario, i get the following when executing via file:

root@Tower:/boot/lsi# 1_ListAllAdaptors

: ambiguous redirect line 1: 1

./1_ListAllAdaptors: line 16: syntax error: unexpected end of file

When I run each line manually in a commandline it works?

/root/mdcmd status|strings|grep "mdState=STOPPED" >/dev/null 2>&1

if [ $? != 1 ]; then

echo "Array found STARTED, stop array before proceeding"

exit

fi

Link to comment

After all the requests for linux versions, i thought after posting the Linux packages, someone would have thrown a party and invited me  ;D

 

New addition, updated OP on the LSI MegaRAID controllers:

 

Convert your LSI MegaRAID controller card with LSI SAS2008 chipset to a Plain SAS2008 controller card (IT or IR mode), will look and feel like a LSI SAS9211-8i, and will be ready to use with unRAID

 

This is a DOS only package (I have provided everything nessasary to quickly create a DOS bootable USB key). Please read the __READMEFIRST.TXT after unzipping.

 

A friend of mine and follow unRAID'er purchased several IBM M1015's and pushed me to do it, so now that I actually got one in my hands, the research began. Re-read KKM's post and went digging for answers. Each card Manufacture applies a unique SBR value to their card so you cannot cross flash, but by applying a SBR to your card that matches the firmware you would like to load on it fakes it for a lack of better words. I collected every SBR I could find out on the web. Not sure if KKM made his "empty.bin" sbr or found it, in either case it seems to be the slickest to use, as it just zero's it out all together not having to try and have a matching SBR altogether, thanks KKM!

 

This package is only available in DOS, seems either LSI used to post the MegaRec utility or it was leaked (internally or by an OEM builder), as it seems to have only one purpose (Wiping and reprograming  ;D). I could not find any other version other than DOS, which does make sense. But the package has eveything u need (including making a a usb bootable dos stick for you), extracting the SAS address for you (as this will need to be reprogramed back to the card)

 

I used rubylaser's find for a quick USB bootable to DOS find. Its quick and dirty and gets the job done fast so I had no problem with something that would be tossed after use. Thanks rubylaser for posting!

 

Link to comment

 

3TB drives on LSI SAS1068E chipset controllers

 

History: I purchased a Hitachi 3TB 5k drive after 5.0Beta7 was release. I precleared it with version 1.12 preclear_disk.sh script (2 cycles) it passed. I added it to my unprotected array and unRAID created a GPT and formatted the drive and I had all 3TB available to me. I tested this drive on both my onboard SAS2008 and LSI SAS2116 controllers. Both cards supported not only initializing the drive but having all 3TB's available.

 

 

YotY8.jpg

 

Last night I headed over to my friends home with this 3TB 5k Drive above. We shutdown his unRAID server which was running 5.0Beta9 and has (3) IBM BR10i's Controllers (LSI 1068E chipset controllers) in it, each one of the three controllers was already flashed to the last firmware update available by LSI (P20) in IT mode ( The one offered in th OP ).

 

We slapped this 3TB drive into his Norco drive carrier and inserted it into an empty slot on his Norco 4224. Powered on the server and hit CTRL-C to enter the LSI BIO's configurator. The drive was initialized and showed a negotiated interface speed of 3.0 Gbps (Which is the max. a 1068E chipset can do).

 

So clearly NO problem with the controller initializing the 3TB hard drive.

 

 

bsdqs.jpg

 

Drum roll here... Once the unRAID server booted up, we selected to add it as a cache drive (because his parity drive was 2TB and I wasn't giving him the drive to keep :) just to test  ;D)

 

And the result was it showed up as 2.2TB. We then shutdown the server and proceeded to test this drive on the other 2 IBM BR10i's, each time shutting down and moving the drive to a different slot which put it on a different IBM BR10i controller. Each time unRAID booted up it saw the drive as havinge 2.2TB available.

 

 

eznat.jpg

 

 

If anyone can show the same facts with all 3TB available on a 1068E chipset controller under unRAID (any re-branded, firmware, s/n of drive, etc..), please share. Until then we now have our answer. I do want to add the 1068E chipset controllers are solid, excellent performing cards, tried and true!

 

They just cannot support offering greater than 2.2TB of a 3TB Drive.

 

Link to comment
  • 2 weeks later...

New addition, updated OP on the LSI MegaRAID controllers:

 

Convert your LSI MegaRAID controller card with LSI SAS2008 chipset to a Plain SAS2008 controller card (IT or IR mode), will look and feel like a LSI SAS9211-8i, and will be ready to use with unRAID

 

This is a DOS only package (I have provided everything nessasary to quickly create a DOS bootable USB key). Please read the __READMEFIRST.TXT after unzipping.

 

Just a quick Thank You!!! to madburg for the slick M1015 flash package.  I used this on a card last night and it worked perfectly, it really can't get much simpler.  Please keep up the great work!

 

Link to comment

I have successfully flashed 2x Intel RS2WC080 controllers into IT mode using the supplied package. Worked perfectly both times and couldn't be simpler. The MegaRAID iMR drivers under Solaris with passthrough would constantly cause kernel panics (after one/two days or under heavy write load) - flashing them into IT mode and using the mpt drivers has solved the issue I was having. Thanks again for putting the effort into this.

Link to comment

Thanks for posting your results guys.

 

I have successfully flashed 2x Intel RS2WC080 controllers into IT mode using the supplied package. Worked perfectly both times and couldn't be simpler. The MegaRAID iMR drivers under Solaris with passthrough would constantly cause kernel panics (after one/two days or under heavy write load) - flashing them into IT mode and using the mpt drivers has solved the issue I was having. Thanks again for putting the effort into this.

 

Can you PM me the ".sbr" file from the Intel RS2WC080 card, I am collecting them. Thanks.

Link to comment

Has anyone connected a 3 TB SATA drive to a LSI 9211-8i and seen all 3 TB using unRAID 5?  This LSI kb article says it will not work.  The kb says it was last updated 7/25/11.  I have this controller in IT mode with the latest f/w and bios using unRAID 5 beta 10.  I hope this article is wrong.  I currently have all Seagate Green 2 TB drives.

 

http://kb.lsi.com/KnowledgebaseArticle16399.aspx

 

It says:

 

6Gb/s SATA+SAS HBAs will not detect drives with greater than 2 TB in capacity (in other words, the 6Gb/s SATA+SAS HBAs won't work with 3 TB disk drives).

 

LSI SAS 9201-16e, 16 ext ports

LSI SAS 9200-8e, 8 ext ports

LSI SAS 9212-4i4e, 4 int + 4 ext ports

LSI SAS 9201-16i, 16 int ports

LSI SAS 9211-8i, 8 int ports

LSI SAS 9211-4i, 8 int ports

 

It also discusses 3Gb/s controllers.

 

Drew

 

 

Link to comment

Hmm, I am a little confused:  ???

 

1. Is there more than one version of the M1015 ? I see people talk about M1015 with LSI9211 and 9220 ?

 

2. Is IBM ServeRAID M1015 LSI 9220-8i PCI-E SAS RAID 46M0831 the same as LSI 9240-8i raid controller ? and can I flash this to be a plane LSI SAS2008 ? so I can use it with Unraid ?

 

Example:

 

http://www.ebay.co.uk/itm/IBM-ServeRAID-M1015-LSI-9220-8i-SAS-SATA-Controller-/200636413220

 

 

 

Link to comment

Has anyone connected a 3 TB SATA drive to a LSI 9211-8i and seen all 3 TB using unRAID 5?  This LSI kb article says it will not work.  The kb says it was last updated 7/25/11.  I have this controller in IT mode with the latest f/w and bios using unRAID 5 beta 10.  I hope this article is wrong.  I currently have all Seagate Green 2 TB drives.

 

http://kb.lsi.com/KnowledgebaseArticle16399.aspx

 

It says:

 

6Gb/s SATA+SAS HBAs will not detect drives with greater than 2 TB in capacity (in other words, the 6Gb/s SATA+SAS HBAs won't work with 3 TB disk drives).

 

LSI SAS 9201-16e, 16 ext ports

LSI SAS 9200-8e, 8 ext ports

LSI SAS 9212-4i4e, 4 int + 4 ext ports

LSI SAS 9201-16i, 16 int ports

LSI SAS 9211-8i, 8 int ports

LSI SAS 9211-4i, 8 int ports

 

It also discusses 3Gb/s controllers.

 

Drew

 

 

 

The 3TB drive support is listed for each LSI chipset in the OP. Currently the only chipset that did NOT support 3TB drives are LSI 1068E chipsets.

Link to comment

Hmm, I am a little confused:  ???

 

1. Is there more than one version of the M1015 ? I see people talk about M1015 with LSI9211 and 9220 ?

 

2. Is IBM ServeRAID M1015 LSI 9220-8i PCI-E SAS RAID 46M0831 the same as LSI 9240-8i raid controller ? and can I flash this to be a plane LSI SAS2008 ? so I can use it with Unraid ?

 

Example:

 

http://www.ebay.co.uk/itm/IBM-ServeRAID-M1015-LSI-9220-8i-SAS-SATA-Controller-/200636413220

 

1. On, the IBM M1015 is a LSI MegaRAID with a SAS2008 chipsets in it.

 

2. The OP explains how to convert (wipe the bios/firmware) of a IBM M1015 and apply a LSI 2008 IT Firmware to it for varies purposes, one being to use it with unRAID.

 

To be clear, there no such thing as a 9220-8i (I know its printed on the back of the IBM M1015 but if you ask LSI they'll tell you there's no such product as the 9220-8i).

 

Link to comment

i get following error when i try to list all devices

 

Press Enter key to start, or CTRL-C to quit.


Proceeding to find LSI Controllers
Log will be AdaptersCurrentFW-Bios.txt in the current directory


FATAL: Module mptctl not found.

****************************************************************************
   LSI Corporation SAS FLASH Utility.

   SASFlash Version 1.24.00.00 (2009.11.13)

   Copyright (c) 2006-2007 LSI Corporation. All rights reserved.
****************************************************************************

       No LSI SAS adapters found! Limited Command Set Available!
       ERROR: Command Not allowed without an adapter!
       ERROR: Couldn't Create Command -l
       Exiting Program.

 

using the linux package on a BR10i

tried moving the card into a windows computer but i don't get video when i install the card in that one :(

so i need the linux package to work :(

 

with the card in IR mode like it is now i get read errors on a new disk ....

Aug  5 09:28:47 p5bplus kernel: end_request: critical target error, dev sdq, sector 278624 (Errors)

Aug  5 09:28:47 p5bplus kernel: md: disk15 read error (Errors)

Aug  5 09:28:47 p5bplus kernel: handle_stripe read error: 278560/15, count: 1 (Errors)

Aug  5 09:28:47 p5bplus kernel: md: parity incorrect: 278560 (Errors)

Aug  5 09:28:47 p5bplus kernel: md: disk15 read error (Errors)

Aug  5 09:28:47 p5bplus kernel: handle_stripe read error: 278568/15, count: 1 (Errors)

Aug  5 09:28:47 p5bplus kernel: md: parity incorrect: 278568 (Errors)

Aug  5 09:28:47 p5bplus kernel: md: disk15 read error (Errors)

Aug  5 09:28:47 p5bplus kernel: handle_stripe read error: 278576/15, count: 1 (Errors)

Aug  5 09:28:47 p5bplus kernel: md: parity incorrect: 278576 (Errors)

Aug  5 09:28:47 p5bplus kernel: md: disk15 read error (Errors)

Aug  5 09:28:47 p5bplus kernel: handle_stripe read error: 278584/15, count: 1 (Errors)

Aug  5 09:28:47 p5bplus kernel: md: parity incorrect: 278584 (Errors))

 

 

and errors like this

Aug 5 10:04:11 p5bplus kernel: mptbase: ioc0: LogInfo(0x31110b00): Originator={PL}, Code={Reset}, SubCode(0x0b00) cb_idx mptbase_reply

Aug 5 10:04:15 p5bplus kernel: mptbase: ioc0: LogInfo(0x31110b00): Originator={PL}, Code={Reset}, SubCode(0x0b00) cb_idx mptscsih_io_done (Drive related)

Aug 5 10:04:16 p5bplus kernel: mptbase: ioc0: LogInfo(0x31170000): Originator={PL}, Code={IO Device Missing Delay Retry}, SubCode(0x0000) cb_idx mptscsih_io_done (Drive related)

Aug 5 10:04:18 p5bplus last message repeated 2 times

Aug 5 10:04:18 p5bplus kernel: Device returned, unsetting inDMD

Aug 5 10:04:18 p5bplus kernel: mptbase: ioc0: LogInfo(0x31170000): Originator={PL}, Code={IO Device Missing Delay Retry}, SubCode(0x0000) cb_idx mptscsih_io_done (Drive related)

 

 

 

 

Link to comment

been trying to troubleshoot this a bit

 

root@p5bplus:/boot/custom/LSI/1.5Gs_3Gs_SATA_Support_Firmware# ls -la /dev/mptctl
crw-r--r-- 1 root root 10, 220 2011-08-05 17:58 /dev/mptctl
root@p5bplus:/boot/custom/LSI/1.5Gs_3Gs_SATA_Support_Firmware# modprobe mptctl
FATAL: Module mptctl not found.
root@p5bplus:/boot/custom/LSI/1.5Gs_3Gs_SATA_Support_Firmware# open /dev/mptctl
-bash: open: command not found
root@p5bplus:/boot/custom/LSI/1.5Gs_3Gs_SATA_Support_Firmware# lsmod
Module                  Size  Used by
md_mod                 45787  0
tun                    10278  2
xor                    12961  1 md_mod
pata_jmicron            1428  0
mptsas                 30656  0
mptscsih               14729  1 mptsas
mptbase                50123  2 mptsas,mptscsih
atl1                   23599  0
scsi_transport_sas     16613  1 mptsas
ahci                   16845  0
asus_atk0110            6497  0
hwmon                    949  1 asus_atk0110
jmicron                 1093  0
libahci                13300  1 ahci
i2c_i801                5679  0
i2c_core               12519  1 i2c_i801

 

DMESG finds the LSI controller

 

Fusion MPT base driver 3.04.17
Copyright (c) 1999-2008 LSI Corporation
Fusion MPT SAS Host driver 3.04.17
mptsas 0000:01:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
mptbase: ioc0: Initiating bringup
---------
ioc0: LSISAS1068E B3: Capabilities={Initiator}
mptsas 0000:01:00.0: setting latency timer to 64
---------------
scsi9 : ioc0: LSISAS1068E B3, FwRev=011b5800h, Ports=1, MaxQ=277, IRQ=16
mptsas: ioc0: attaching sata device: fw_channel 0, fw_id 1, phy 4, sas_addr 0x7a7f39239eaaa08f
scsi 9:0:0:0: Direct-Access     ATA      WDC WD7500AACS-0 1B01 PQ: 0 ANSI: 5
sd 9:0:0:0: [sdi] 1465149168 512-byte logical blocks: (750 GB/698 GiB)
mptsas: ioc0: attaching sata device: fw_channel 0, fw_id 2, phy 5, sas_addr 0x39793747bba09882
scsi 9:0:1:0: Direct-Access     ATA      WDC WD10EARS-00Y 0A80 PQ: 0 ANSI: 5
sd 9:0:1:0: [sdj] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)
sd 9:0:0:0: [sdi] Write Protect is off
sd 9:0:0:0: [sdi] Mode Sense: 73 00 00 08
sd 9:0:0:0: [sdi] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 9:0:1:0: [sdj] Write Protect is off
sd 9:0:1:0: [sdj] Mode Sense: 73 00 00 08
sd 9:0:1:0: [sdj] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sdi: sdi1
sd 9:0:0:0: [sdi] Attached SCSI disk
sdj: sdj1
sd 9:0:1:0: [sdj] Attached SCSI disk

 

 

 

 

but no idea what to do next  :(

Link to comment

Hmm, I am a little confused:  ???

 

1. Is there more than one version of the M1015 ? I see people talk about M1015 with LSI9211 and 9220 ?

 

2. Is IBM ServeRAID M1015 LSI 9220-8i PCI-E SAS RAID 46M0831 the same as LSI 9240-8i raid controller ? and can I flash this to be a plane LSI SAS2008 ? so I can use it with Unraid ?

 

Example:

 

http://www.ebay.co.uk/itm/IBM-ServeRAID-M1015-LSI-9220-8i-SAS-SATA-Controller-/200636413220

 

1. On, the IBM M1015 is a LSI MegaRAID with a SAS2008 chipsets in it.

 

2. The OP explains how to convert (wipe the bios/firmware) of a IBM M1015 and apply a LSI 2008 IT Firmware to it for varies purposes, one being to use it with unRAID.

 

To be clear, there no such thing as a 9220-8i (I know its printed on the back of the IBM M1015 but if you ask LSI they'll tell you there's no such product as the 9220-8i).

 

 

Thanks for clearing that up.

Link to comment

Hmm, I am a little confused:  ???

 

1. Is there more than one version of the M1015 ? I see people talk about M1015 with LSI9211 and 9220 ?

 

2. Is IBM ServeRAID M1015 LSI 9220-8i PCI-E SAS RAID 46M0831 the same as LSI 9240-8i raid controller ? and can I flash this to be a plane LSI SAS2008 ? so I can use it with Unraid ?

 

Example:

 

http://www.ebay.co.uk/itm/IBM-ServeRAID-M1015-LSI-9220-8i-SAS-SATA-Controller-/200636413220

 

1. On, the IBM M1015 is a LSI MegaRAID with a SAS2008 chipsets in it.

 

2. The OP explains how to convert (wipe the bios/firmware) of a IBM M1015 and apply a LSI 2008 IT Firmware to it for varies purposes, one being to use it with unRAID.

 

To be clear, there no such thing as a 9220-8i (I know its printed on the back of the IBM M1015 but if you ask LSI they'll tell you there's no such product as the 9220-8i).

 

 

Thanks for clearing that up.

 

...the corresponding HBA product with the same hardware layout is in fact the LSI 9210-8i: http://www.lsi.com/downloads/Public/Internal/LSI%20SAS%209210-8i/LSISAS9210-8i_product_brief.pdf

This product has not been seen on the market officially (yet?).

Luckily for us, the Firmware for the 9211-8i is compatible with it.

Link to comment

New addition, updated OP on the LSI MegaRAID controllers:

 

Convert your LSI MegaRAID controller card with LSI SAS2008 chipset to a Plain SAS2008 controller card (IT or IR mode), will look and feel like a LSI SAS9211-8i, and will be ready to use with unRAID

 

This is a DOS only package (I have provided everything nessasary to quickly create a DOS bootable USB key). Please read the __READMEFIRST.TXT after unzipping.

 

Just a quick Thank You!!! to madburg for the slick M1015 flash package.  I used this on a card last night and it worked perfectly, it really can't get much simpler.  Please keep up the great work!

 

 

Add me to the list ;D THANK YOU madburg!! I just flashed 2 M1015s with no problems.

The package makes it so simple... even I can do it 8)

 

Thanks again...

SBRM1015.zip

Link to comment

Tried flashing my Fujitsu D2607 to IT-mode, but failed.

 

This is the output when doing a "sas2flsh -o -f 2108it.bin -b mptsas2.rom".

LSI Corporation SAS2 Flash Utility
Version 9.00.00.00 (2011.02.17) 
Copyright (c) 2008-2011 LSI Corporation. All rights reserved 

Advanced Mode Set

Adapter Selected is a LSI SAS: SAS2008(B1)   

Executing Operation: Flash Firmware Image

	Firmware Image has a Valid Checksum. 

	Firmware Image compatible with Controller. 

	Valid NVDATA Image found. 

	NVDATA Device ID and Chip Revision match verified.
	Valid Initialization Image verified.
	Valid BootLoader Image verified.

	Chip is in RESET state. Attempting Host Boot...
	Firmware Host Boot Successful !
	Writing Current MfgPage2 Settings to NVRam
	Failed to validate MfgPage2 !
Due to error remaining commands will not be executed.
Unable to Process Commands.
Exiting SAS2Flash.

 

No problem flashing it back.

 

Attached the SBR file from the D2607.

d2607.zip

Link to comment

Now you can also add me to the list of people who have flashed the M1015 card to SAS2008(P10) !  :)

I had no problem with flashing, but my MEGA.SBR file was empty when I checked the USB drive after the flashing was done ?

I did not se any error when I used the utility. I will check this the next time I flash a M1015 card.

 

Is there any reason that that I should have had the MEGA.SBR ? other than for this forum ?

Do you want the ADAPTERS.TXT instead or is it irrelevant ?

 

Now my old parity disk is running preclear on the new controller with a speed of 113 MB/S on an WD 2 TB Green harddrive.

 

As other people have said, I can not see the smart info on mymenu in unmenu for the disk on the new controller, but Unraid Version 5.0 beta 9 have no problem reading the smart info.

 

Link to comment

As other people have said, I can not see the smart info on mymenu in unmenu for the disk on the new controller

 

Just a few simple patches to the script files will fix this.

 

Can you give me a hint of where ?. I have found out that I need to remove the -d ATA option from one file, but where ?

Link to comment

In myMain, you can add the custom drive attribute "smartopt" and set it to "-A" on each drive connected to the controller.

 

Does this really remove the -d ATA option which unMENU adds to each smartctl command?  It is this which causes problems with many add-on controllers.

 

I'm still not clear why it was felt to be a good idea to force smartctl to attempt to treat every drive as an ATA device.  Although this appears not to upset some SATA controllers, others refuse to 'play' when they're treated as a legacy ATA device.

 

I have hand-edited every file in unMENU, where necessary, to remove the '-d ATA'.

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.