RAID & AHCI devices on the intel sATA's? P67A-GD65 (B3)

Question

Since i stuffed a 6TB WD Green in my system to use for the bulk stuff i just have to keep, i decided i would go ahead and get the most out of the drives i already had in my system as well, and screw the tiny chance of a data loss, i can just regularly backup the raid to the big old slow drive, and live with it.
Anyway, so i have a Samsung 830 SSD (120gB) as boot / system drive, and 2x Seagate 500GB sATA drives i wanted to raid up to a stripe RAID.
The Samsung 830, and the 6TB WD Green hangs of the Intel 6gbit sATA's, and the Seagates hang of the Intel 3gbit sATA. Simply since thats the fastest combination available. However, since the system is up and running, i ran head on in to an issue. You can only switch the Intel channels to RAID as a group. You don't have to include all the drives in the RAID, which of course means drives not included will show up as what they are, single drives available to the OS. However, the AHCI bit's apparently aren't enabled then, and the system fails to boot of the current install on the SSD.
Back in 2011 Intel stated that RAID on their sATA chip's would enable AHCI, but the only reason for BSOD's on boot that i can come up with, is the lack of AHCI, while the OS expect AHCI.
Is there a workaround / fix for this? At this point i wont pull the rack out just to move the 2 drives to the Marvell chip, and live with the lower speed. Mainly since it's quite the elaborate procedure to pull the darn case out of the rack cabinet...
Edit
In the interest of being thurogh. I got a i5 2500K on the motherboard, and i think i'm running 1.9 BIOS or something. I'm not quite able to reboot right now, but it was the "last one" before they started making magic stuff which made the motherboard twitchy if you updated to a Ivy Bridge BIOS, and ran a Sandy, and vice versa.
If it makes any damn difference, i'll check the BIOS once my current batch of file transfers are done... Which is in something like 20 hours.
/Edit

Answer 1

Quote from: JLio01 on 29-April-15, 08:56:45
When you installed OS on Samsung, what SATA mode did you set?
Actually already answered. The OS install expects AHCI, since thats what i've been running for a couple of years.Quote from: Mr_B on 29-April-15, 02:18:52
Back in 2011 Intel stated that RAID on their sATA chip's would enable AHCI, but the only reason for BSOD's on boot that i can come up with, is the lack of AHCI, while the OS expect AHCI.
Quote from: JLio01 on 29-April-15, 08:56:45
default settings is IDE, did you change it to RAID mode?
When i built the system i switched it to AHCI since Windows 7 knows what that is, and how to use it. When i stuffed the 6tB drive in there, and decided to stripe the 2 500gB drives, i went and switched it to RAID mode.
On the consecutive boot i went "CTRL-I" and added the two 500 gB drives to a striped volume, leaving the Samsung SSD, and the WD 6tB drives alone. After telling the system i'm done, it reboots again, and the system behaves like expected, and starts to boot windows of the SSD, but reboots or BSOD's after a couple of seconds on the animated loading screen. Fairly typical behavior if your running a mismatched AHCI setup. Meaning, if the OS expects it, but doesn't get it, or vice versa.
I have no doubt that this would work if i reinstall, but i don't want to, for a couple of reasons. Mainly the simple fact that reinstalling means it wont use AHCI anymore. Perhaps a tiny performance loss, but it's still there. At that rate i'd rather go through the hour long process of pulling the case, and switching over the "to be RAIDED" drives to the marvell chip, and take the performance hit from the slower performance it has.
If there is anything else i can add to make it clear, feel free to ask again. Thank you for your time and effort.
I should be able to reboot and check the BIOS version in an hour or so, the transfer is starting to look almost finished.
B!
Edit
Turn out i don't need to reboot to check the BIOS. I still have the forum flasher thingy installed, and it reports the stats when launching. 1.j, or, 1.19. BIOS date, 2012-03-07. I was right as far as it's the latest right up to when they started adding Ivy Bridge support, and things went weird. Not sure if any of the later BIOS alternatives would be helpful in this situation.
/Edit