http://www.evga.com/support/faq/?f=58913

Skip down to step 2, its identical.

ctrl I is correct, try again. 

Did you try with another keyboard ?

@DarthSion:  You appear to have missed the point that,  that screen never shows up.  It's completely Missing.

 It goes straight on to where either a floppy disk, Operating System or CDROM would normally start booting.

@caguerrero: Do you actually have an SR-2?

Can anyone else that has an SR-2 actually verify they see that screen during post?

@fitseries3:   Yes indeed, but I did just figure something out.

I set ESATA Controller (BackPanel) to Disabled and now the Intel Matrix Storage Manager screen is appearing just fine..    What the heck?

Fit, you didn't have to disable your ESATA controller did you?

Anyhow, raises another question.. if my ESATA controller is messing with the Intel Matrix controller, then what happens to a raid setup if I have to re-enable it or set bios to default to flash the bios. 

Hmm, but should it be required to have it disabled in order for the Intel Matrix controller to work?

CorDox
@caguerrero: Do you actually have an SR-2?

Can anyone else that has an SR-2 actually verify they see that screen during post?

no i dont have an sr-2 i just felt like guessing

I had the same problem when I first booted the machine with the default BIOS version.  I updated to the 044 version and all seems fine.
I'll have to check to make sure eSata is enabled in the BIOS

I had the same problem and fixed it. But I am not sure which thing fixed it:

A: Updated bios
B: Formatted my RAIDed drives
C: Installed chipset drivers

For those (such as myself) who do not have the ability to upgrade the BIOS, the Intel RAID manager can still be activated.

1. Go into the BIOS and disable the SATA3 bus.

2. Reboot and use Ctrl-I to activate the Intel Matrix Storage Manager. Do your business in it.

3. Go into BIOS after leaving the Storage Manager and enable SATA3.

4. Reboot.

I've been using this to deal with the SATA2 RAID on a Linux system that boots from a SATA3 SSD. The changes made in the Storage Manager (including rebuilding a RAID array) take effect on the reboot.

semper_non_sequitur

For those (such as myself) who do not have the ability to upgrade the BIOS, the Intel RAID manager can still be activated.

1. Go into the BIOS and disable the SATA3 bus.

2. Reboot and use Ctrl-I to activate the Intel Matrix Storage Manager. Do your business in it.

3. Go into BIOS after leaving the Storage Manager and enable SATA3.

4. Reboot.

I've been using this to deal with the SATA2 RAID on a Linux system that boots from a SATA3 SSD. The changes made in the Storage Manager (including rebuilding a RAID array) take effect on the reboot.

Why cant you update the bios? I know there is no flashing util in Linux but you can make a USB drive boot FreeDOS (What I did) to flash the board.

>Why cant you update the bios?
> I know there is no flashing util in Linux but you can make a USB drive boot
> FreeDOS (What I did) to flash the board.

Ah, I'd forgotten all about FreeDOS.

I haven't used any DOS or Windows stuff since the late 90s,  and I no longer have any copies lying around. I'll d/l FreeDOS and give it a shot when I get a chance.

I still don't understand why all manufacturers haven't moved to using bootable ISO images for flashing. It seems like the most foolproof method, and the OS could be FreeDOS, NetBSD, Linux, or whatever has the least restrictive distribution policy.

Actually, I've worked with enough EE guys to answer that question -- most of them seem to have trouble dealing with any kernel more complex than CPM  ;)

Oooopppppssssss!  Somehow didn't see the 25 messages above me?????  I swear they weren't there.  I'll leave this all the same--looks like several other people solved it before me--wish I'd found this two days ago (I did look--just not far enough).
 
Hi, CorDox.  Don't know if you solved this or not.  I had the same problem for the last two days and did find a solution. 
 
You've probably already resolved this, but thought I would post this in case others had the problem.  
 
I did several things and finally could CTRL-I into the Intel Matrix Storage Manager ROM.
 
    0.  Reset the CMOS, turned on RAID for SATA
    1.  Disabled quick boot.
    2.  Disbled the splash screen.
    3.  Disabled the eSATA ports
    4.  Disabled the SATA 3 controller.
 
In this configuration, press CTRL-I right after the memory count-down completes and as you see AHCI on the screen rapidly several times.  This now reliably gets me into the RAID setup.
 
I suspect that disabling the other two SATA controllers (Step 3 and Step 4) is what let me get in, but I'm not going to go back and verify at the moment--on with installing the OS! 
 
good luck, tommy

 
So, I made some slight progress but nothing useful.  I was unaware of the BIOS selection switch on the MB.  EVGA tech support recommended I try flipping back to an older BIOS, which I did and VIOLA', I got the Intel RAID post and the CTRL-I option got me into the Intel RAID configuration screen.
 
Unfortunately, the 3T drives I have showed up at 700G.  In spite of this, I created an array just to see what would happen.  After booting back into the OS, the array was no where to be seen and both drives continued to be presented as 2, separate 3T drives.  Not useful.
 
Exiting back out, I checked the config and the RAID array still showed in the Intel ROM utility.  Oddly, the Intel software utility did not show the array and did show the drives as proper size.
 
I'm accepting defeat on this one and will be RMA'ing the board.   It's really odd and seems that this should be fixable.  Everything looks to be there.  The control does POST under certain conditions.  The drives all show up correctly at all times.  The configuration on the controller is retained through power cycles.  It just seems like it's this close to working... but I can't find that last little switch.  I'm really dreading disassembling this rig.  It's water cooled and is really going to be a pain in the arse to break down and to put back together.
 
I do appreciate EVGA's customer support's help with me on this issue.
 
Thank you!

KDodd
I know this is an old thread, but it's at the top of Google search.
 
The reason why CTRL + I doesn't show up is because you have to enable Caps Lock. Otherwise you're trying to access by typing Crtl + i.
Yes, It's that simple.
I see this a lot.

is that just a thing with the sr2 board, my x58 from evga and Foxconn, H97 from gigabyte and two different asus boards have never required me to hit the caps lock.