Thank you for contacting Intel® technical support. I will be more than happy to help you.
I understand that you are having issues with corrupt data in your RAID array.
Since Intel® RST shows that the RAID 5 array is "Normal," then there is no issues with the RAID volume. Since Windows® is telling you that the data is corrupt, I would recommend you to run a Startup Repair with the Windows® 7 installation disc. You can find instructions in the next link: https://www.lifewire.com/how-to-perform-a-startup-repair-in-windows-7-2626170
Please be aware that the content on that site is not controlled by Intel®. This information is offered for your convenience and should not be viewed as an endorsement by Intel® for the merchants or services offered there.
In the event that the Startup Repair tool does not work, you should be able to access and retrieve the data from a working operating system. You can either take the drives and connect them to a computer with a Windows®, or add an extra drive to your computer and install Windows® in it, and this way you can access the drives and copy your data to another location.
Wellll... still working on it.
I don't HAVE an extra huge drive to offload everything to, so I'm using a bunch of 320 GB drives I happened to have lying around. The only problem is that I'm out of SATA connections, so I'm attempting backups (using Recuva from piriform) over a USB-to-SATA interface -- it's taking a LONG time to move 3 TB over USB!
To further complicate things, I'm getting intermittent errors from one of the drives -- one day all three show up as "good", but the array needs to be rebuilt, the next, it shows one of the drives as "missing" and the array "degraded". Then in the Intel UI, they all show as good, but rebuilding. As I'm making my backups, it may run for a few hours and then hang up. At that point, I have to reboot, and Windows wants to run CHKDSK on the array (I don't want it to write to the array, so I'm stopping that, and letting Recuva scour the drive instead). That whole reboot-and-pick-up-where-it-left-off cycle is also stealing a lot of time. It also seems to reset the "rebuilding the array" progress to zero. It hasn't stayed up long enough to think it has rebuilt the whole array YET.
I'm trying to get everything copied off of the array first. Then, I plan to take the drives, one at a time, and run drive diagnostics from the manufacturer. I knew I had one bad drive and replaced it. It seems quite coincidental that a second drive has failed days after replacing one of the others, but I can't rule it out.
Bottom line -- still making backups of what I can salvage, and then to gather more clues. This ran flawlessly for 4 years (until that doggone first drive failed) -- I just have to find the root cause of the problem at hand.