x399 Fatality, 1950x, RAID problems

Does not seem anyone is really interested in this, but I have a test result.
I used the MS Media Creation Tool to create an ISO and used Rufus to write a USB stick using parameters for UEFI only and NTFS file system.  It boots and shows the RAID after installing the drivers.  A strangeness is both partitions of the USB show in the F11 - Boot Menu.  It does not matter which one is selected - both work.  The reason I tested the NTFS file system is because sometime my Install.wim file exceeds 4 GB and FAT32 would fail.  Enjoy, John.

Wednesday, I tried again to install W10 on a 3 NVMe SSD RAID0.  I had no trouble creating the RAID0.  I then booted my Rufus created USB stick with my personalized install files.  When I got to the "Where do you want to install Windows" screen, I could see the individual SSDs not the RAID0.  I had injected the ASRock RAID drivers into the Boot and Install .wim files.  On past implementations (before Ryzen), I would see the RAID as soon as I got to this screen.  I had also copied the driver files to the USB, so I tried doing a Load Driver for them (both ASrock and AMD).  I could never see the RAID0, just all the SSDs.  I installed W10 on one of the SSDs after doing a Diskpart Clean and it went fine.  My next try will be without the injected drivers in my image files.  I suspect that the injected drivers are somehow confusing SetUp.
Since I set CSM to Disabled, I only saw the UEFI version of my USB stick, after F11.
Some information on my install files (ISO).  It contains the first release of W10 1703 (Fall Creators Update, aka FCU aka RS3).  To this I added the latest cumulative update (patch level 98), drivers, and enabled/disabled Features.  This was accomplished using DISM, part of MS ADK.  Because of the added updates, the Install.wim file was over 4 GB.  Rufus thus changed the file system from FAT32 to NTFS.  This resulted in 2 partitions on the stick.  Sometime when I plug this stick into my system, I get a nasty message about errors, but sometime I can open both partitions and see the files - one large one with my data and a small one with Rufus files.  This prompted some research by me and I have much to understand yet.  It seems that MS made a change in FCU how W10 works on removable drives:

As a result, the UEFI:NTFS partition, which sits at the end of the flash drive, will be mounted automatically (along with the other partition from the drive) in Windows Creators Update, whereas this is not the case with previous versions of Windows.

For brave ones, here is the details: https://github.com/pbatard/rufus/issues/931
This is further confused by having to boot the USB in UEFI mode.  Anyone with knowledge of all this is invited to comment.  I should try again in the next few days and report the outcome - more research in the meantime.  Enjoy, John.

Well I think I've got a (mostly) resolution, John from Asrock support replied to my ticket.

It looks like I am making progress and learning things.  I was able to delete the ghost RAID0 and all the real drives under Array Management-Delete and build a two NVMe drive RAID0.  It was my intent to use all my drives (3), but the drive numbers changed when I did a delete and I suspect I deleted one twice an one not all, so only two were available.  I was able to install W10 from a USB stick created by Windows Media Creation Tool.  The only strange happening was the first re-boot hung and required a Reset.  All other re-boots worked fine and W10 seemed OK.  When I tried to use WinPE to install from a Flat (drive), I could not get Setup to see the RAID0.  After trying many things, I surrendered, deleted the RAID0 and installed W10 on one of my SSDs.  The method I used was derived from a report from AMD support (Matt).  Since I was creating only an NVMe RAID, I did not change the SATA to RAID (left AHCI).  I also disabled CSM.  Working in the BIOS was really bad.  Almost all my clicks to do something required many tries.  When I wanted to select a drive, I might need to click on it 5 times to get results.  Always something!  I have created a USB stick (using RUFUS https://rufus.akeo.ie/ ) with my Unattended install .XML file and will test it on Hyper-V soon.  Enjoy, John.

I had a similar experience to yours. RAID implementation on this platform is very poor so far. I gave up after many attempts.

Edited by daddyo - 08 Dec 2017 at 9:28am