RAID Issues on Mac Pro

I had been having problems with a RAID set "randomly" disappearing as a drive on my Mac Pro. Turns out it appears to be linked to having Parallels running. I can have the Mac up fine for hours/days, but if I leave a Parallels VM with XP up for an hour or so, I will end up with something like the following in /var/log/system.log:

AppleRAID::completeRAIDRequest - error 0xe0030005 detected for set "MaxRaid" (54E3C579-8932-425E-8772-799DFDCD0756), member FA2E0F40-F928-431B-BAA1-06C1723551FF, set byte offset = 9786540032.
Nov 23 08:09:17 BigAl kernel[0]: disk3: 0xe0030005 (UNDEFINED).Nov 23 08:09:17 BigAl kernel[0]: disk3: device is offline.
Nov 23 08:09:17 BigAl kernel[0]: disk3: device is offline.

Unfortunately this screws up a lot of stuff besides just the VM, as I have other shared storage on this drive set, and the only way I have found to get it back is to reboot the Mac.

Anyone else seen anything like this?

Thanks for any suggestions you might have,
Sam

PS The RAID set is 2 Maxtor 500GB drives setup with RAID-0 if it matters.
PPS Yes, I know RAID-0 = easy to lose data, blah, blah, blah.

 

I have been running build 1970 on my Mac Pro 3 GHz with 8 GB RAM for the last couple of months without any issues, but that all ended today. My setup is a follows; Boot drive is a single 150 Raptor, and my user volume (netinfo mapping) is a 4 drive raptor stripe. The virtual hdd is in the defualt ~/Library/Parallels/ folder.

This morning, by backup software crashed while writing the virtual hdd file (winXP.hdd) to a backup volume, and took down the entire RAID - I had to re-create the raid to repair it, nothing could fix it (DW4). When I tried to launch the virtual XP machine, I got the error that the hdd was corrupted, and couldn't be launched. Since I lost the RAID and the backup file is corrupt, I have lost my XP machine.

There seems to be quite a few posts regarding problems that people who use a raid have with parallels. I wonder if Parallels has done any testing with respect to this issue. Note that this is the second time that this exact scenario happened. AND IT HAPPENED EXACTLY 35 DAYS AFTER CREATING THE VIRTUAL HDD BOTH TIMES. Is there anything that gets triggered every 35 days? I'm wary to recreate the virtual instance out of fear that I'll lose my raid again in 35 days and have to waste a whole day repairing it.

 

I also observed this weird situation.
I let my Mac Pro fall asleep with Parallels running (a winXP image from the RAID), when I woke the Mac, one disk of the RAID was marked 'failed' in Disk Utility. After reboot the disk was back online. Since then, every time I start a virtual machine in Parallels the RAID set fails (and gets dismounted).

The system log mentioned:

"May 14 15:11:29 Mac-Pro kernel[0]: AppleRAID::completeRAIDRequest - error 0xe0030005 detected for set "snelleschijt" (26282F1E-C6E7-4C47-8479-F75F01EE6927), member 902A3749-41CC-49F3-A2DE-E00DB6B925D4, set byte offset = 206444752896.
May 14 15:11:29 Mac-Pro kernel[0]: disk3: 0xe0030005 (UNDEFINED).
May 14 15:11:30 Mac-Pro kernel[0]: AppleRAID::recover() member 902A3749-41CC-49F3-A2DE-E00DB6B925D4 from set "snelleschijt" (26282F1E-C6E7-4C47-8479-F75F01EE6927) has been marked offline.
May 14 15:11:30 Mac-Pro kernel[0]: AppleRAID::restartSet - restarting set "snelleschijt" (26282F1E-C6E7-4C47-8479-F75F01EE6927)."

Any ideas how to resolve this issue?
Is my disk broken? Or is it a software issue?
Thanks in advance for any help.