SAS9211-8I 8PORT Int 6GB Sata+sas Pcie 2.0

Product Information

The first thing that went through my mind when I got to that part of the tutorial I linked above was pretty much just "WTF?

All of my experience with HBAs has been limited to server type installations normally running FreeNAS or UnRaid. After what I have noticed and read about Mellanox ConnectX-2 cards being too old and not well supported despite being recommended by the community in general, I wonder if there is a similar situation for HBAs.We check before going further, how many LSI controllers the flasher detects, and that it's the same as the number of LSI controllers you expect it to find, so that nothing gets wrongly flashed if there is a hidden controller anywhere. Example: potentially some SAS-3/12 Gbit hard drives may not work with a SAS-2/6 Gbit card like the 9211. But the cards often needs crossflashing for several reasons: They need to be switched over to IT not IR firmware versions ("IT" firmware means it's an HBA firmware which ZFS likes, while "IR" is a hardware RAID firmware which is strongly discouraged by most people for ZFS - the card can run either of these but often comes with the IR version loaded by default).

But if you do have hardware or firmware RAID/caching in use however, STOP RIGHT HERE and check what's safest for your data before you disconnect drives or unplug controller cards.

New: A brand-new, unused, unopened and undamaged item in original retail packaging (where packaging . If the issue's still not solved and it's not the cable, and other troubleshooting fails, then SBR might be a candidate (see link below), or ask for help in the forums.

You will have multiple prompts requiring a yes to initiate a flash, there won't be any 'oops' that you haven't said yes to a couple of times.Add up the total bandwidth of all disks attached to the HBA, and compare it to the total PCIe bandwidth to the motherboard (lanes in use x bandwidth per lane) for PCIe 2 or 3, and for whatever number of lanes the card+slot have (or the lowest if they differ), to see if you'll hit a serious risk of a bottleneck. exe, backup the existing SBR data (although you probably won't ever need it) and then erase the card and all NVRAM data, including writing empty SBR data to the card. Give it one last reboot to MSDOS/EFI for certainty and check with "sas2flash -c CARD_ID -list" that everything now looks as you expect. In either case the solution is the same - go back to step 2, erase again, and double check the firmware you tried to flash really is IT and is one of the earlier firmware versions up to say 2009-2013 so there's no doubt it can be flashed using the early flashers such as P5 (this isn't usually an issue but I'm mentioning it "just in case" and in case future updates break compatibility).