So even once you've flashed from Dell IR to Dell IT firmware (or whatever brand it is), you still can't jump directly to LSI latest IT firmware using a recent flasher, because the recent flashers just won't let you. 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).

Even when erased, the card will still "remember" it's an IR card, so we deal with that next, by flashing your manufacturer's IT version firmware onto it, if not already IT.Failed to validate MfgPage2" which really means "Crossflash attempt blocked because your card isn't bought from LSI so we're going to be annoying" (the Vendor IDs in NVRAM and new firmware don't match) - this is why we're using a pre-P7 flasher for the crossflashing step, as the earlier flashers were as reliable but allowed crossflashing. You just gave me and someone else who is far less lazy an idea for a guide thread (so the answer is no). I'd be surprised if that were true - it's relatively rare to see hardware support removed from the linux kernel, especially for comparatively modern hardware. ZIP FILE / DOWNLOADS: All the files mentioned in this page, ready to unzip and copy to your bootable USB stick.

Make sure you don't accidentally flash an SSD or motherboard (or other hidden) LSI 2008 controller before continuing. The process is a little obscure but Bryan’s instructions are thorough; I’ve flashed 5 HBAs to IT mode this way. The short answer is that usually it shouldn't be any worry, and you cannot "brick" these cards (render them unusable), but there are precautions you can take if concerned - and there are a few very definite warning signs to watch out for.On an EFI board the USB stick will show up as 2 options: "USB (NAME)" and "UEFI USB (NAME)" - choose the first for MSDOS and the second for EFI. Foward Breakout cables are used to go from a HBA/RAID card and connect one of the ports on your LSI 9211-8i to 4 x sata drives.

black thanks, so having No Image for the x86-BIOS won't be an issue or cause the SAS2008 controller to brick when I restart/power off? 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? Once your storage device is set up to boot and look for an operating system or shell, the LSI-related files in the attachment should be copied over to it, and also the MSDOS related files if it can't find MSDOS.wendell I bought a new LSI card and it still isn’t working with my PC(previously posted about my problems here: LSI SAS 9207-8i and windows 10). 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. I'm also going to assume you 've read carefully online and haven't found information you need, or you've tried following some guides and "it just hasn't worked". The firmware most people will want to get working is LSI/Avago/Broadcom IT software (currently version P20).

Side Note: regardless of the type of cable you may or may not have, double check that everything is plugged in right. All of my experience with HBAs has been limited to server type installations normally running FreeNAS or UnRaid.LSI's P5 flasher will program the manufacturer's early version IT over IR regardless of the make of card you have.