I've seen this a lot, when the drive firmware is mismatched. Can you pause the initialization, and check the drive parameters?
Specifically, what do you mean by "check the drive parameters?"
Do you mean the physical disk drive firmware, or something else?
Exactly, the physical disk drive firmware.
What parameters should I be checking and what tools do I use to check those drive parameters?
RAID Web Console 2 - does it show the disk drive firmware?
When I click on a physical drive(s) I can see various details such as
capacity: 1.818 TB
Product ID: WDCWD2002FYPS0
Revision Level: 04.0
Which is the same for all 5 drives.
For some reason the Background Initialize is not running anymore. I guess it finally finished after enough weeks??? Sadly there is sparse information in the logs to explain anything other than the Background Initialize completed. It is really frustrating that there is no progress information other than it started and stopped. There are clearly bugs in the RAID support because the BGI for virtual disk 0 did show progress, but the BGI for virtual disk 1 did not.
I can also tell the Background Initialize is not running anymore because my system boots fasters, and Windows and various applications are behaving better (without all the frustrating pauses and freezes).
Sadly, Windows behaves extremely badly when the underlying disk or network systems are having problems. I am pretty sure there is no-one left at Microsoft who understands how the Windows kernel works anymore, and I am pretty sure there never was anyone at Microsoft who understood much about operating systems design, especially in the areas of performance.
For now things seem to be OK, but I'm pretty sure next time there is another hickup in the RAID system I will have to go through another few weeks of intense frustration yet again.
I really hope the new Ramsdale products come out soon, and that you can boot Windows from them. Booting from a RAID 5 system, especially IESRT II, is a really, really bad idea.