Recover Data from disk management striped dynamic disks

Hi everyone, sorry but it's a long one to make sure all info is there.

I have the following problem: I had a software RAID 0 array of 2 disks where I had lots of professional video work being edited. I had backups of most everything except one recent work, which is very important.

What I mean by software RAID 0, is the option to convert 2 drives in one dynamic disk, by striping, using Windows (7 in this case) disk management utility. These were two 600GB WD Velociraptor hard drives. The system was on a separate identical 600GB WD Velociraptor drive.

Now for some stupid reason, when I was restoring a System Image Backup, it decided to install it in one of the RAID drives. I'm saying "it" decided because I did nothing different than the many times I had restored system images before on the same system. I usually just did "next, next, next..." - but maybe something disconfigured in the Bios and it didn't detect the System Drive and decided to install it in one of the RAID ones - a 120GB partition was created in the 600GB drive. The rest still shows as unnalocated (RAW files from the array?).

I have tried tons of recovery softwares: EaseUS, iCare Data Recovery, R-Studio, TestDisk, DMDE, ReclaiMe... You name it, I've tried it. EaseUS was the only one that seems to see the 2 Drives as a single dynamic disk, but recovery returns a bunch of truncated video files. I don't know if this is because EaseUS is recovering files from each disk separately or if it's because of the partial formatting of one of the disks. The other softwares where I tried rebuilding the array, like DMDE or R-Studio, returned checksum errors or "WinError 55 - Network resource not available" at some point. It left me wondered if on top of everything I also had a mechanical problem in that formatted drive. Data Lifeguard Diagnostics detected several unreadable sectors... But I suspect that's "soft" bad sectors... Not actually physical damage.

For that reason, my plan was trying to undo the formatting before I tried rebuilding the array. But quite frankly... I don't even know if such an "undoing" thing is possible. This is my dilemma:

1. If I try to recover the files from each disk separately, the files will make no sense on their own (they are half-files).

2. If I try to rebuild the array before recovering the files, it returns me errors because one of the drives has been formatted and that half of the array is not complete. EaseUS sees the 2 drives as one dynamic disk but recovers truncated files.

4. I'd like to return the partially formatted drive to its original state to try and rebuild the array, but don't even know if that's possible.

5. I now created two separate images of each drive of the array hoping I manage to rebuild the array from them, in case the DMDE RAID recovering problem was due to mechanical failure. But I fear it will still return errors because I haven't "unformatted" the drive.

6. If I finally find a way of undoing the formatting, will it work with the images I created? Or does it need to be done in the actual physical drive? I'm asking this because now that I created the images, I really want to try and erase everything in these drives and see if they're healthy, to re-use them.

7. Any other advice on how to recover my data?

Thanks in advance!

Welcome to the forum. If you have run software on the drive you may have made it worse. The fact data will have been overwritten is also very bad. Going to a professional recovery is you best bet but failing that I would delete new parition then try specific parition recovery software plenty free on google. If one fails try another some do a better job than others.
Raid 0 is a waste if one disk dies you loose everything

Thank you for your reply and advice, Samuria. Yes as I explained I did try several softwares. I did recover some files but the majority were either truncated or messed up. Some videos showed as 15 minutes long but only played through 1/3 of the timeline. Other videos were mixed with different videos. some HD videos had SD videos embedded picture in Picture. I think AeseUS tried to stitch stuff that didn't belong to stuff. Also the fact that my array was full may have caused the files to be very fragmented.