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

Product Information

The EFI boot rom may be described as "UEFI" or "BSD" but it appears on the next line after the bios boot rom). In this scenario, you would have a chassis with a SAS backplane that you drives all slide into and then you use one of these reverse cables to connect the backplane directly to the motherboard without the use of an HBA/RAID card. The card wont be damaged - theyre designed to run hot and in the end the kernel will panic and the system shut down.

If you're not needing SAS3 or NVMe speeds for SSDs though, the old SAS2x08 chipsets are still more than adequate for any platter-based drives and most SSDs and play nice with EFI (as far as I'm aware anyway) - as long as those things keep on trucking and suit your use case, there's no reason not to use them. Perhaps this is another dumb question, but once it is working, those drives should just show up in windows correct? I cover the difference between them below, but for the moment what matters is that if you're using the card with ZFS, as FreeNAS does, you will almost certainly need to have the manufacturer's IT version firmware (for HBAs) not the IR version (for RAID) during the crossflash process. I did have to hunt down the p20 sas2flsh DOS file as I didn't find it in the download but that was pretty easy here https://www. However the important thing is checking there aren't any hidden LSI controllers, before we do any erasing or flashing.In other words, can you use the LSI P5 flasher to jump in a single step from (say) Dell P7 IT to LSI P20 IT, or do you have to go via the LSI P7 IT? I'd like to put in a 12TB drive as my parity drive (UnRaid), and move the 8TB drive i'm currently using into the pool.

These are about the only cards I wouldn't bother reflashing to LSI, although it would almost certainly be OK, because I trust their native firmware to be done well and up to date, hence no need. The process is a little obscure but Bryan’s instructions are thorough; I’ve flashed 5 HBAs to IT mode this way. It will give an understanding of the actual crossflash process, and why the "recipe" below is as it is. If those do not work for you (and in my case they did not), it might be that your M/B requires an older version, either the X64 or IA32 version.To do the other cards, open the script in Notepad or a text editor, it's got maybe 4 lines that start "! Obligatory disclaimer: As best I can tell this is accurate and will do what's needed to crossflash these cards. IF THE OUTPUT FROM sas2flash -listall SHOWS MORE LSI CONTROLLERS THAN YOU EXPECT, *** DO NOT IGNORE IT! Make sure you don't accidentally flash an SSD or motherboard (or other hidden) LSI 2008 controller before continuing. I suppose I could setup another machine but why waste the electricity if I can do it all in the same local machine?

But as far as I know, that only affects SAS-3 and the upcoming SAS-4, and perhaps SATA Express/SATA-4 drives. fs0: fs1: etc - select a device (Typing fs0: selects the device shown next to fs0: in map as the current device/folder. Can I simply attach the orphaned SFF-8087 cable to that available port on the LSI to get the remaining 4 drives connected or will it not work because it's expecting an expander since there's an expander on the other port?But the same principles do generally apply to the more recent LSI/Avago/Broadcom HBA cards and variants, such as the 9300/9311 (SAS3008/3108 chipsets) and newer 94xx. After reading posts from this and other forums, I feel like it's not necessary to flash the mtpsas2.