the four hard drives that make up this RAID 5 array all have the same version of and the latest that is available from Western Digital.
these drives have been used in other installations without a problem.
this array worked for quite some time without issues. if the firmware was the problem, i would think that it would have been seen from the start.
there is also a RAID 0 array on this controller which holds the system volume. this a 2TB MBR. the R5 is a GPT volume. why is the R0 array not affected?
any ideas why this occured on the R5 array?
the standard reasons of software versions not being compatible can not be the only cause! like I stated in the post that started this thread, this array worked hard for a couple of months without issues!
the thing that precipitated this situation was the ACPI driver and the system giving the BSODs because of this driver.
aside from recovering the data on the array, how can this be prevented in the future?
how can a system that has ACPI issues all of a sudden show the R5 array as "Incompatible? and why does that not affect the R0 array that is on the same controller and which holds the system volume?