Striker Extreme, 3ware Raid, Vista boot problems

[killerhertz]

Hello,

I recently installed 32-b Vista Ultimate on my new 680i box. I dropped some good cash on an 8port 3ware 9650 RAID card, but the BIOS and Vista aren't playing so nice it seems. I have (3) WD1500 in RAID5 for the OS and (2) 7200.11 in RAID1 for data. When I boot, after the 3ware controller info displays, I get the following error:

DISK BOOT FAILURE, INSERT SYSTEM DISK AND PRESS ENTER

If I have my Vista DVD in, it boots fine. I tried playing around with the boot order in the BIOS, but it didn't help. I updated the BIOS to the latest available from ASUS as well.

Any ideas?
Thanks.

FYI, here's my current configuration

Intel Core 2 Duo E6600 Conroe 2.4GHz 4M shared L2 Cache LGA 775 Processor - Retail x 1
Zalman CNPS7700-CU 120mm 2 Ball Cooling Fan - Retail x 1
Asus Striker Extreme LGA 775 NVIDIA nForce 680i SLI ATX The Ultimate Gaming Motherboard - Retail x 1
G.SKILL 2GB (2 x 1GB) 240-Pin DDR2 SDRAM Unbuffered DDR2 800 (PC2 6400) x 2
EVGA 640-P2-N821-AR GeForce 8800GTS 640MB 320-bit GDDR3 PCI Express x16 HDCP - Retail x 1
Seagate Barracuda 7200.11 ST3500320AS 500GB 7200 RPM SATA 3.0Gb/s Hard Drive - OEM x 2
Western Digital Digital Raptor X WD1500AHFD 150GB 10,000 RPM 16MB Cache Serial ATA150 Hard Drive - OEM x 3
3ware 9650SE-8LPML PCI Express SATA II Controller Card - Retail x 1
Lite-On Black 20X DVD+R 8X DVD+RW 8X DVD+R DL 20X - Retail x 1
Lian-Li PC-V600B Black Aluminum ATX Mid Tower Computer Case - Retail x 1
Corsair HX Series CMPSU-520HX 520W Power Supply Retail x 1
CyberPower Enterprise CP1500AVRT 1500VA 900Watt UPS - Retail x 1

[kuraegomon]

Just in case someone else looks at this, this problem is caused by the Asus Striker Extreme - it flips the boot order of the RAID arrays that is reported by the 3Ware 9650SE. If you enter the 9650 configuration utlity at boot-up, and switch the RAID volume order there, instead of in the BIOS, you can resolve this problem.

Good luck installing linux though - I still haven't found the correct incantation to get GRUB to handle this scenario correctly.