![]() #Amd raid 0 installation readonly or readwrite installI borrowed a friends windows computer, and wrote the Windows ISO to the same flash drive using Rufus, and the install completed successfully. I followed a supposably supported method of recompressing the file, but this seemed to have been the cause of the issue. As of 1809 - the install.wim file is too large to fit on fat32 filesystem as is - and requires recompression. In my case, the problem seemed to be with the method I compressed the Windows install.wim. The problem was not with AMD, nor the drivers. in that quite a few problems can cause it. Looks like this error is a little generic. If I re-enter the installation after this, I can see the drive is partitioned, but the following error is shown when I attempt to select the partition for installation. Sometimes immediately, sometimes after a few minutes. The raid drive shows, but after I select it and click next, this error pops up. Config driver (have tried both loading, and not loading this driver) ![]() Motherboard: Asrock Fatal1ty X399 Professional Gamingīios: 3.70 (Latest) which I believe runs AGESA 1.1.0.2ĭrives: Samsung evo 970 1TB + Samsung evo 970 plus 1TBĭriver versions: 9.3.0.38, 9.2.0.127, 9.2.0.120, 9.2.0.105, 9.00.00.088īios settings: CSM on/off, secure boot on/off, destroy and rebuilding array, both initialise and not initialise drives prior to building the array, both using write cache, and disabling write cache when building the arrayģ. ![]() I am completely out of ideas, and hoping someone from either the AMD community, or maybe the Asrock community can give some insight as to what the issue could be. I keep getting the same errors, no matter what I try. I spent all night last night trying to get Windows 10 to install on a NVMe raid 0 array configured from the bios of my Asrock Fatal1ty X399 Professional Gaming motherboard. ![]()
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |