That is to be expected as it takes time for RAID BIOS to initialize an array even if one is defined because it has to look at the drive structure and determine whether or not the array is functional and healthy in order to initialize the array. You will notice if you disconnect a drive from a RAID array that a Windows machine in Disk Management console will recognize the disk as not being initialized. This is because once the disk is paired in a RAID array, the logical disk information is stored in the machines RAID BIOS, and in the MBR for your drive. Essentially you are taking two physical hard disks and making one logical hard disk out of the two. The drives are effectively linked at the logical layer allowing them to work well together, but unless they are initialized and formatted, they will no longer work independantly of each other. The benefits, of course, with RAID 0 are performance. However, you will have no data redundancy as RAID 0 is sometimes referred to as dummy RAID or pseudo-RAID. RAID being a redundant array of independant disks suggests that RAID 0 would have this functionality, but none exists in RAID 0. You sacrifice performance for redundancy, which is acceptable provided - as you do - you have another data drive for storage or are working with data in an environment where redundancy is not a concern. I myself set up RAID arrays on a daily basis - whether RAID 5 for a server - or RAID 0 or 1 for consumer machines. I like your taste in SSDs. I myself have an array in RAID 0 with two GSkill Pheonix Pro series SSDs and I love it.