I just encountered something weird when setting up my RAID5:

I set up my RAID5 in the WebBios using the default settings (except for forcing to always use Write Back).
At the end of the wizzard WebBios asks me if I want to do a fast initialization, so I choose yes.
Then almost immediately I come to a screen where I can again choose to initialize and also do other things (such as a consistency check).
Since I just choose to fast initialize already, I just exited WebBios and booted into Windows.

When I open Disk Management in Windows, it asks which type of partition I want for the RAID5.
I choose GPT and create on big NTFS partition with a custom Stripe size of 64K (same as configured in WebBios)

Then I went to LSI MSM and tried to do a consistency check.
This gave a warning that the disk wasn't initialized yet??

So I thought: perhaps it is still busy in the background... So I left my PC running for 24hours...
Then I tried again, it still sais the disk isn't initialized??

So I try to initialize and it warns I will loose all data. To make it a bit easier for MSM, I then removed the partition and did an fast initialize.
After the initialize, I rebooted (else Disk Manager was flipping), I again created a GPT partition type with NTFS partition (again 64k stripe).

Then I retried to do a consistency check, but it warns the disk isn't initialized??

So I again remove the partition, do a fast initialize and tried to do a consistency check before created a partition.
This time it started, but immediately found inconsistent parities.

So I stopped and decided to a full initialize (not fast), which is running now...

Can anyone explain me what I'm doing wrong? What is the correct way to do it?
I want to be able to do consistency checks while keeping the partitions of course

And I know I can do a consistency check on a "non-initialized" disk, but I still prefer my initialized disk to be recognized as initialized as well