Same issues as decribed previously in attempting to RAID 0 two Seagate 3TB Barracuda drives (which had previously been formatted remotely via an eSATA connection). The eventual work-around, under guidance of AppleCare, was to remove the drives from the MacPro where they did not appear on the SATA bus, reformat through a USB external connected to a MacBook Pro (where they they curiously renamed as 850GB ST300 ... ), and then reinstalled them in the MacPro where they finally appeared with their proper names 3TB ST300 ... and all the proper erase, format, RAID, etc buttons in Disk Utility. From there I was able to RAID them without any further issues.
Note that the drives were originally formatted remotely via an eSATA connection through the normal dialogue interface ( ... this drive is unreadable ... initialize ...) on the MacPro, under 10.8.4 and seemed to function normally. I never examined them through Disk Utility, so it is likely that the drives were not properly connected to the SATA bus all along.
Note that remotely connecting them via eSATA showed the drives exactly as when they were in the computer.
Note that the reformatting was possible via USB on a different machine. It would likely have been possible via USB on the MacPro also.
Finally, the helpful AppleCare support person, believes this might be an "internal SATA bus" connection issue being caused by a software issue with Disk Utility. He is going to punt this to Enginneering.