Leaderboard

Just edit the VM and apply the changes to the video card (subject to IOMMU grouping, etc -> didn't look at that part of the diagnostics) As far as avoiding the issue, the BIOS is assigning the numbers. ACS override might avoid it, but you only enable that if you have to due to how the IOMMU groupings are.

Somewhere in the XML you're probably referencing a device (0000:03:00.1) that no longer exists. If you were passing through a video card, it may have changed from 0000:03:00.x to 0000:04:00.x when the hardware configuration changed. 03:00.0 Serial Attached SCSI controller [0107]: LSI Logic / Symbios Logic SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] [1000:0072] (rev 03) Subsystem: LSI Logic / Symbios Logic SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] [1000:3020] Kernel driver in use: mpt3sas Kernel modules: mpt3sas 04:00.0 VGA compatible controller [0300]: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) Subsystem: ASUSTeK Computer Inc. Device [1043:85eb] 04:00.1 Audio device [0403]: NVIDIA Corporation GP102 HDMI Audio Controller [10de:10ef] (rev a1) Subsystem: ASUSTeK Computer Inc. Device [1043:85eb]

I had this same issue. I got a raspberry pi zero and used that as my secondary domain controller. Then once I connect to the domain and the VM starts the primary comes up and it seems ok. Rebooting unraid its a toss up if it remember the domain connection or not. PITA but its all I could do to get it working. Maybe there are some better ideas out there.

@shEiD @johnnie.black @itimpi Oh how we love to be comforted! While it is true that the mathematics show you are protected from two failures, drives don't study mathematics. And they don't die like light bulbs. In the throes of death they can do nasty things, and those nasty things can pollute parity. And if it pollutes one parity, it pollutes both parties. So even saying single parity protects against one failure is not always so, but let's say it protects against 98% of them. Now the chances of a second failure are astronomically smaller than a single failure. And it does not protect in the 2% that even a single failure isn't protected, and that 2% may dwarf the percentage of failures dual parity is going to rescue. I did an analysis a while back - the chances of dual parity being needed in a 20 disk array is about the same as the risk of a house fire. And that was with some very pessimistic failure rate estimates. Now RAID5 is different. First, RAID5 is much faster to kick a drive that does not respond in a tight time tolerance than unRaid (which only kicks a disk in a write failure). And second, if RAID5 kicks a second drive, ALL THE DATA in the entire array is lost. With no recovery possible expect backups. And it takes the array offline - a major issue for commercial enterprises that depend on these arrays to support their businesses. With unRaid the exposure is less, only affecting the two disks that "failed", and still leaving open other disk recovery methods that are very effective in practice. And typically our media servers going down is not a huge economic event. Bottom line - you need backups. Dual parity is not a substitute. Don't be sucked into the myth that you are fully protected from any two disk failures. Or that you can use the arguments for RAID6 over RAID5 to decide if dual parity is warranted in your array. A single disk backup of the size of a dual parity disk might provide far more value than using it for dual parity! And dual parity only starts to make sense with arrays containing disk counts in the high teens or twenties. (@ssdindex)

I pretty much gave up on my 1700X/X370 Pro system. Screen randomly goes black and total hard lock, even at default speed. Overclocked it does it. Default settings it does it. Does it with one 980Ti, does it with two 980Ti. When it 'black screens' I have to pull the mains power for a few minutes before it'll reboot. Power button or Reset button do nothing. The Ryzen system is sitting on a shelf waiting for me to get more time to figure out the issue, meanwhile I'm back to an i7-7700K with the snot overclocked out of it - and it's stable. I'm hoping LT can get it sorted with unRAID and then I'll figure out the issues with whatever is causing my lockups, and hopefully use the Ryzen for my unRAID. Edit 23/7 - see below updates, system stable now

Yup, default fans with 2 120mm extra fans for exhaust on the top. Xeon X3360. All other specs are in my signature..