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

Product Information

Comprehensive list of known/common cards, OEM variants, and the chips used/capabilities - with thanks to ServeTheHome.

On ASRock, hit F11 at boot to enter the boot options menu (with all hard drives removed and only the SAS you are working on inserted), then select the UEFI shell and proceed with Bryan’s instructions (near the bottom of the page). The less expensive ASRock motherboards I’ve used do have an easily-accessible UEFI shell (as it seems all UEFI motherboards should). Can you un-cable manage the breakout cables (read - take it out of the velcro straps and keep them as far away from other cables and as unbent as possible)and try and isolate them from any other cable interferrence. 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?

I believe he was referencing the old card (9207) but it is still a good troubleshooting step, have you tried using both of the ports on the 9211-8i? You'd need to get a SAS2 expander, like the Intel RES2CV240 or similar, or a chassis that comes with an expander and backplane, as well as the various cables to connect the 9211 to the expander (SFF8087 to SFF8087) and then the expander to the drives. Unless you really need/want these, it's usually best not to flash a boot rom as it won't do much except slow your system boot. The command takes a single string of 16 hex digits, so do not include any hyphens, underscores, spaces or punctuation, even if the original SAS ID included them. org permalink)- Hacker's take on the crossflash process, and analysis of SBR data and fixing drives not recognised after crossflashing.

The firmware and boot rom files, and sometimes the flashers, are often wrapped up in zip or exe files which need to be unpacked and the relevant files extracted. It will give an understanding of the actual crossflash process, and why the "recipe" below is as it is. Single or Dual link to expander also work, if in dual link then actual bandwidth would be 4GB for 16 disks, every disk got 250MB minimum, so scan 10TB should less then 24hrs. If not, use the above command first of all, to get the info, if you insist on making a note beforehand But if it's a "clean start" situation with no need to preserve existing SAS topology or attached disk info, mostly you just want to be sure the SAS ID is unique in that box and you won't need to have an existing SAS ID to crossflash+prepare your card. Note: I put this in the storage subforum instead of the tutorials because it's fairly specific and the people who might find this useful are more likely to be lurking around here I'd estimate.You have to judge it for yourself, I'm not responsible at all if your card doesn't behave as expected or anything goes wrong (even if you follow this guide).