madburg

After all the requests for linux versions, i thought after posting the Linux packages, someone would have thrown a party and invited me 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 ). 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!

Unless you renamed the preclear_disk1.12beta.sh to preclear_disk.sh, then you would run it as "/boot/preclear_disk1.12beta.sh /dev/XXX", otherwise if you have say 1.11 or lower still next to it, you would not be running 1.12, but an older version.

I have posted the final linux packages for the SAS1068E, SAS2004, SAS2008, SAS2116 chipset controllers in the OP.

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

Posted first linux version: LSI SAS1068E Controllers(P20)Linux.zip on the OP. Need someone to help me out, need some bash code that checks state of Array (stopped/started), I would like to add that code into each (stage) script to verify the array is not running, exit if found running. Or a pointer to a script that pulls that info already (a unMenu script, etc...) that I could look at as a reference, to speed things up. I will finish the rest of the packages and up and this QA one after I have this code, so no one has an accident. NOTE: Currently it does not check if the unRAID array is started, it WILL reset the card during the flash and you WILL have data corruption and/or unRAID crash, so PLEASE stop your array first.

Added note and screenshot of recommended LSI BIOs setting for all LSI cards with IT mode flash and is being used under unRAID.

Nope, SORRY I got my posts wrong, it was KKM's, and thats why i thought they were Linux steps and thats why I did not want to create linux packages, then I re-read your post agan PeterB and saw it was doable. KKM's steps are a bit wild and seems he renamed the BIN file (2108.bin ) so without knowing the source of that file, I dont want to touch it (i did not alter any of the LSI files, I just made simple batch files to follow with a readme file and dropped pdf's for easy reading for all, as its all over the place on lsi's site and download). My understanding from KKM's post is that you are clearing/wiping the bios complete off of the M1015, then reprograming the nvram to the sas2008 firmware and bios, then since you wiped the bios originally you need to put back the sas address of the card (at the very least) Not my cup off tea. My suggestion is sell the card to someone looking for a great RAID controller and buy a less expensive LSI card which you can switch between IT/IR modes. I can understand if you somehow got one for free or for a very cheap price, then you can try KKM's instructions at your own risk.

the sas2flash is a utility coded by LSI that can talk to a LSI SAS card (certain models, for other cards there is a sasflash) this is how you can read what FW/BIOS your card already has, backup it FW/BIOS to files, and with the correct commandline you can point it to FW/BIOs files to upgrade/downgrade/restore your card. I included the sas2flash reference files in the packages so anyone can see everything available via the utility. Many of the cards have a IT and IR Firmware, you can only run one at a time. Some of the cards I already listed by default are raid cards, an example is the LSI SAS9201-16i is not a raid card, just a simple HBA, so ONLY IT firmware is available for it. I explained why it is recommend to flash to IT mode on cards that are by default in IR mode. Lastly, i included both modes in the package, should anyone want to revet back to IR mode for other purposes. The goal for these cards under unRAID is to flash to IT mode and there have been fixes for greater than 2.2TB support as well as bug fixes. Flashing to IR mode will not make your card a mega raid card that is a line of card LSI makes with more advanced riad capabilities. What you can do it seems from PeterB's post is you can overwrite the MEGA firmware and bios to a standard IT/IR mode (yes IR is raid , but does not have as much options as there mega line). It is not a 9210-8i model now, it has been flash to IT mode with the SAS2008 chipset firmware, it worked because the chipset is a LSI sas2008 chipset. If you ever wanted to bring it back to a mega card, you would need to use the mega package I have posted. As you can see from the post mega is not supported under unRAID. But you can wipe the mega fw/bios and put down the sas2008 IT mode fw/bios on it, there by no longer a mega card. Hoping you now understand to answer the first part of you question now, so I dont repeat. But so you are clear it is not a 9210-8i is a card with 9211-8i chipset, it is a mega card (M1015) with a sas2008 chipset, flashed with the sas2008 IT mode firmware/BIOS now. If you flash your M1015 which now has the sas2008 IT mode firmware to the sas2008 IR mode firmware it will be a simple raid card, not as advanced as it could be when it was flashed with the mega firmware.

Sorry! I'll have a go at loading P10 firmware in a little while, then put together an archive with all the Linux versions of sas2flash that I can find. Hummm, interesting as I am learning more and more each day, I re-read your post on page 3 here and I have all the Linux sas flashs, seems I would be able to make these packages after all, I will whip up shell scripts to do the same steps as i am doing for the windows packages, one would just have to un zip the contents in a temp dir on the flash and invoke each shell script. Should have it done by tomorrow.

New updated from LSI were posted for most cards (P10), no update for the SAS 1068E chipset. Add a new package for SAS2004 chipset as a few people PM'ed requests on these as well. I have update the OP (please re-read) and posted the new firmware packages. I added an additional step to each, so please "After you expand the zip file, please read the file "__ReadMeFirst.txt" before doing anything!". Sorry guys no Linux package version, the LSI site is a mess and I am still learning (not enought to pull it off, if even possible. Bring you card to work and use your bosses PC , go to your neighbors home and hijake there PC , do what you need to, to flash your card. Booting up a windows OS will take the longest in the update process.) I would recommend updating your card(s) with this latest update. BIOS P10 (7.19.00.00) Notes: SCG Engineering Release Notice GCA Release Version 7.19.00.00 - SAS2BIOS_PH10 (SCGCQ00195755) (SCGCQ00195755) - GCA Release Version 7.19.00.00 - SAS2BIOS_PH10 Change Summary ( Defects=15 Enhancements=6) SCGCQ00183922 (DFCT) - View Volume screen needs more than one ESC key press to exit screen if user has entered Manage HS screen at least once. SCGCQ00184126 (DFCT) - CU selection to choose a tape to put into $DR (Disaster Recovery) does not set $DR mode. SCGCQ00186462 (DFCT) - SAS2BIOS: Adapter Properties screen shows Package Version Field SCGCQ00187617 (DFCT) - BIOS will attempt to scan for devices if adapter is not in LSI mode SCGCQ00187715 (DFCT) - Verify command in BIOS CU continues for a drive that is pulled out. SCGCQ00188722 (DFCT) - BIOS: Config page error is seen when changing enclosures in Controller BIOS. SCGCQ00189197 (DFCT) - Server appears to hang during "Initializing..."! SCGCQ00189775 (DFCT) - SAS2BIOS/CU is not checking valid bit in fixed format sense data SCGCQ00193110 (DFCT) - BIOS hangs or asserts NMI and reboots while parsing the SMBIOS entries of some servers SCGCQ00193121 (DFCT) - Tape Device is displayed as a missing row in Create volume screen of Bios CU. SCGCQ00193310 (DFCT) - BIOS CU "Format" and "Verify" fails with some HDDs SCGCQ00174000 (CSET) - SHEX fix not supported for all B0 Mustang/TBolt parts SCGCQ00188149 (CSET) - Windows 2008 fails to install to disk attached hybrid EFI/legacy system SCGCQ00188702 (CSET) - SAS2 HBA is not releasing allocated memory when done with it. SCGCQ00192605 (CSET) - Missing SATA drive of a SATA Volume is displayed as 'Missing drive' under SAS volume and vice versa. SCGCQ00174966 (ENHREQ) - Provide Manufacturing page 240 information to HBA FW through config page write SCGCQ00175682 (CSET) - SAS2BIOS - Add Phy Number to Device Properties screen of SAS2BIOS Configuration Utility SCGCQ00176889 (ENHREQ) - SAS2BIOS: Add full descriptor support for Request Sense data (>2 TB support) SCGCQ00187157 (ENHREQ) - Additional adapter support for IO Space Write Errata (TBolt/Mustang B0) SCGCQ00187419 (ENHREQ) - SAS2BIOS - Supply additional PCI information for IOC Page 1 SCGCQ00183688 (CSET) - Remove Warhawk references from baseline BIOS ] FIRMWARE P10 (10.00.00200) Notes: SCG Engineering Release Notice Phase10 Point Release Version 10.00.02.00 - SAS2FW_Phase10 (SCGCQ00202418) Change Summary ( Defects=1) SCGCQ00200602 (DFCT) - Fault 0x100 prevents code from running at SOD Phase10 Point Release Version 10.00.01.00 - SAS2FW_Phase10 (SCGCQ00201729) Change Summary ( Defects=2) SCGCQ00192977 (CSET) - SMPs are issued by FW in target only mode during discovery. SCGCQ00201234 (CSET) - SATA commands take too long when unit attention set or SATA init is needed Phase10 GCA Release Version 10.00.00.00 - SAS2FW_Phase10 (SCGCQ00198003) Defects=0, Enhancements=0 (Version Change Only)

Added to OP a confirmation from a member that they successfully flashed a Intel SASUC8I card using the LSI SAS1068E firmware.

Did anyone try to install this LSI BIOS on a BR10i? I cannot find where it says it supports 3T drives. Did I miss it? BUT ... Look here on IBM's site: According to THIS VERSION HISTORY, the BR10i version 2.72 (and newer) support large drives. Enhancement - Support 2TB LUNS and greater Download here ... http://www-947.ibm.com/support/entry/portal/docdisplay?lndocid=MIGR-5077837 My posted LSI FW/Bios is newer than what IBM has posted in that article: •BIOS Version: 6.30.00.00 •Firmware Version: 1.30.10.00 bjp999, I forgot you had a BR10i and 3TB drives, I sold my card to a friend of mine, were you able to test if the FW:1.32.00.00, BIOS 6.34.00.00 / 20-DEC-10 did not see all 3TB? I am not seeing anything newer available for the 1068E, still looking, what a mess they made of the site.

IR or IT mode? recommend IT mode. I will post you results to the OP.

Hope you're wrong. I am going to try 2.74 and see. BIOS is dated June 2011. It should support 3T drives. bjp999, I forgot you had a BR10i and 3TB drives, I sold my card to a friend of mine, were you able to test if the FW:1.32.00.00, BIOS 6.34.00.00 / 20-DEC-10 did not see all 3TB? Your welcome JM2005. Glad it helped. I will be adding the lastest firmware soon for all cards to the OP and maybe even a linux version to do right from unRAID.

Since you read the post and see no reason to go to IT mode and new firmware for your card, then you should do what you feel is best, if it works and thats enough for you. Then leave it alone. You can obtain that from the LSI site, I did not have time to create 2 flavors, sorry.

Please read the OP, first page has what you need and clearly states which one is for the BR10i. Not sure what you mean by linux version.

Thanks Joe L. I just posted in the 5.0Beta7 announcement page, I assigned my 3TB precleared drive to the array it took! Log is attached there. Page 16 on the forum. Beautiful job Joe L.! Many thanks as always (getting old but u deserve it ), and for those that dont know Joe L. has added the ability to detect hd% or sd% drives with out having to worry about the -A option I got it all wrong Joe L. explaination of addition below (correct me if & were I am wrong Joe L.) as of 1.12beta of his script, its a beautiful thing.

I have no issue just adding this drive even if I have to wait 7 hours, I am in no great rush at the moment. The drive precleared successfuly so I know it does not have to be RMA'ed. Thats all that mattered at the moment, many thanks to your script. Its just I believe its a good idea to nip this in the bud while Tom gave us this first cut with 3TB support, and fixing a bunch of other stuff he meantioned in the latest beta thread. I am sure he supports your efforts as otherwise without it there would need to be a large disclosure of just how long ones array could be down while adding a large disk to an array. Not a great selling point. I figured your communication with him (more techy and same level plain) would be more key than mine just saying it don't work... I am offerring HW/SW testing as thats all I can offer for this subject. Do support your efforts in every way.

Do you think or can you confirm with Tom, maybe as the code is right now when unRAID see's a drive >2TB (or 2.2) it expects to see not only the GPT (table) but a GUID in that GPT and if it does not see a GUID in that GPT, then it believes it needs to be cleared...? I am assuming this based on reading the wiki "GPT retains the MBR entry as the first sector on the disk followed by a primary partition table header, the actual beginning of a GPT." OR Maybe Also per wiki "GPT also provides redundancy, writing the GPT header and partition table both at the beginning and at the end of the disk.". Could Tom have forgotten to meantion the second GPT to you, maybe?

Hitachi 3TB 5K drive running a "dd if=/dev/sdb count=1 2>/dev/null | od -x -A x" after short preclear test via 1.12 beta the results I sent Joe L. were: 000000 0001 0000 0000 0000 0000 0000 0000 0000 000010 0000 0000 0000 0000 0000 0000 0000 0000 * 0001c0 0002 ff00 ffff 0001 0000 ffff ffff 0000 0001d0 0000 0000 0000 0000 0000 0000 0000 0000 * 0001f0 0000 0000 0000 0000 0000 0000 0000 aa55 000200 After completing a successfuly 2 Cycle preclear via 1.12Beta (Total Elapsed Time: 66:18:08), results of "dd if=/dev/sdb count=1 2>/dev/null | od -x -A x" were: 000000 0000 0000 0000 0000 0000 0000 0000 0000 * 0001c0 0002 ff00 ffff 0001 0000 ffff ffff 0000 0001d0 0000 0000 0000 0000 0000 0000 0000 0000 * 0001f0 0000 0000 0000 0000 0000 0000 0000 aa55 000200 Not sure where this is at, from other responses, so I did not try to add this to the unRAID array yet. Holding for direction from Joe L. what I should do next. I am trying to understand who is actually generating the GPT GUID and stamping it? Is preclear doing this and unRAID is supposed to pick it up, or something completely different...

Updated main post to reflect 5.0Beta7 release and added an addition row "3TB Drive Support with this card:" so if you test on one of these particular cards with a 3TB drive (precleared or not, added to array, formatted, saw all 3TB, etc...) please post your results. I will update accordingly.

Joe L. Blessed the quick test results from the 1.12 beta i sent over to him. I have now kicked off a 2 Cycle preclear on a Hitachi 3TB green drive. Will post results once complete and added to the array.

Thanks, I guess what I meant to be more clear (just in case), I saw this: "short_test=0 # set to non-zero for short test for script testing - Leave 0 for normal test" I was under the impresstion preclear_disk would at the end write something to the disk which is the same as what unRAID does at the end of a format. So that is why when we add a precleared drive in as a data drive it ready to go quickly. So what I was wondering is if there is a way to skip the pre-read/write/post read and just have the script do that last thing you do to the drive to make unRAID believe it formatted it, i guess. In this case we are testing the 3TB GPT sig you are applying (I think). I just wanted to get that done fast and results over to you. Then if theoutcome is what you expected. Go back, remove the drive from the array and run a true FULL preclear on it. Hope this make more sense.

Is there a pretend mode or quick mode I can use? What I mean by that is something like have it read just a bit maybe write just a bit and then have it stamp (gpt, signature, etc). This way I can give u back if unRaid said it as a formatted drive already, etc... Knowing it will be pre-cleared fully at a later time, should the quick test work out.

Hey Joe L., are you working on a new release of preclear_disk for 3TB drives? If so and you need a beta tester, I just received one today.