Success! I've finally got my troubled 6.9.2 setup upgraded to 6.11.5. In the end it took the latest mobo BIOS, UnRaid booting Legacy, and a new NVidia GT1030. The BIOS update allowed me to get away from ACS override since my video card and audio are now in their own IOMMU groups. I now have two UnRaid servers running GT1030s and can run the Windows VM on either JIC. Any good ideas on how to best use one to back up the other datawise?
The mobo is MSI Carbon Pro AC with with a Ryzen 2700X. By the way, the reason for the GT1030 is its the cheapest video card I can find that does 4K. Down side is it can't be used in Plex for HW decodes.
Regarding vfio binding in System Devices; it doesn't seem to matter if I bind the video card or not. Should I just bind everything available so I can use them safely in VMs or only what I know I need or doesn't it matter since if I can bind them they are not used by UnRaid?
I would also suggest that when we do a manual flash backup it would be nice to have a pop up option to change the file name to describe the conditions. That would be useful for trouble shooting and make it easy to restore milestone backups. JMTC.
Also for problems like this UEFI vs EFI booting is critical. EFI is "legacy" UEFI is new and looks better with smaller text in my case. UEFI = "EFI" directory name in the flash, "EFI-" is legacy. My luck has been with legacy.
I used a MAC and virtual PC to create boot flashes and the most reliable method for me was to not use the flash creator but instead format the flash FAT32 on the PC, unzip the back up, copy to the flash, and run the respective boot script from the base flash directory. Sometimes UnRaid backs up as a directory and sometime a zip file so PAY ATTENTION. Look at that flash drive and even try to understand the file structure. That will go a long way to resolving mysterious boot issues. Remember EFI vs EFI-.
If you have a random power down issue, you might have the Dynamix S3 Sleep plugin install and sleep enabled. TURN IT OFF in the settings if updating your mobo BIOS. It could be that the old BIOS did not support S3 sleep and the new one does!
I didn't have to specify a "Graphic ROM BIOS" in my VM though I was ready to do that after downloading from techpowerup.com and clearing the header per the SpaceInvaderOne video. So what does that callout do exactly? Does the specified Graphic ROM BIOS supersede the BIOS in the card or does it provide some secondary source of some information to UnRaid?
Also double check you have HVM and IOMMU enabled in the BIOS and shown here ESPECIALLY if you updated your BIOS. It might have changed! Get this from the info icon at the top of the screen. HVM goes by many names, for my BIOS it was SVN and it moved after the BIOS update.
I found the solution: Settings -> Sleep Settings were enabled. It was "sleeping" shortly after I booted UnRaid. This happened after upgrading to 6.11.5. I may have been booting in UEFI rather than legacy without realizing it and the feature just didn't work in legacy.
