Can I delete a two SSD Raid 0?

Question

Attempted to setup a RAID 0 using two SSD drives, using Disk Utility.
Then tried to use Carbon Copy Cloner to clone an existing bootable internal drive to the new RAID.
CCC stated that it couldn't do that because one of the drives in RAID had no Recovery Partition.
Now I cannot delete the RAiD setup to go back and reformat the individual drives to include the Recovery partition.
Other than being out of my mind, what am I doing wwrong here?
All this is on a 2012 Mac Pro running Maverick OS.

Answer 1

I don't know if this will help or not, but I did have a problem in attempting to "De-Construct" a RAID array that got broken somehow and I wanted to change the striping from mirrored (RAID 1) to RAID 0. Since this was a LaCie External Little Bisk 250GB SSD, I wrote to them and received a reply (the Disk Utility application cannot "De-Construct" a RAID array once created by that application, but it can be easily accomplished via Terminal using the Command Line:
DE-Construct a LaCie Little Bog Disk RAID Array
From LaCie Technical Support on May 29, 2014
IMPORTANT NOTE: The procedure below involves the use of the Terminal program. This program, if used incorrectly, can cause data loss, or other problems. Ensure everything is typed precisely to avoid data loss.
Ensure an up to date backup exists prior to starting this process. It is important to ensure you do not have any other removable drives attached to the computer other than the one we are working with during this process.
1. Open the program "Terminal". This is within the Utilities folder (MacHD --> Applications --> Utilities)
In the terminal window, type:
diskutil list
then press enter. Ensure this is all lower-case, as everything is case-sensitive within Terminal.
This command will return a list of all the attached drives on the computer by a unique hardware identifier. (e.g. disk1, disk1s1). At this point, you will need to determine the correct identifier for the drive we are working with.
2. If you are having problems getting the volume to dismount in Disk Utility, you can use the following command:
diskutil unmount force (identifier)
This step is not necessary if the volume for the drive we're working with is already unmounted. In that case, proceed to the next step.
3. One of the disk identifier entries may show the overall RAID set that was configured on the drives. If that is present, use the following command to remove this item:
diskutil appleraid delete (identifier)
Again, if the RAID set is not visible in the listing shown in step 1, then proceed to the next step.
4. The following command will completely eradicate any remaining header information on the individual disks. This command would need to be done for each disk in the array:
diskutil zerodisk (identifier)
Please be very careful when running this command. This will fully wipe all data from the target drive(s). This should, however, clear off the inaccurate header indication on the drive that is incorrectly telling Disk Utility the drive is "broken".
This process will start a long zero-out procedure on the drive. If you wish to test the hardware integrity of the drive mechanism, you can let this process complete to 100%. If this completes without errors, then we know the hardware of the drive mechanism is completely healthy. This will take several hours to finish on most systems.
If you do not wish to wait, then you can usually interrupt this process (Control + C will abort this) after a minute or two. The important header information is one of the first things to be erased by this process, so even if interrupted, this command should still correct the problem.
5. After everything is finished, you should be able to exit Terminal, and go back into the Disk Utility Application to re-configure the RAID array on the device.
Hope this is helpful,
Barry