rook

The issue came down to me not passing the audio hardware of the graphics card to the VM. After doing this, everything worked as intended.

Unraid 6.12.8 GTX970, only GPU in the system. I have it allocated to a Windows 11 VM; my Unreal Engine build box. GPU is NOT allocated in any way to any other VMs or Dockers. (I have one other VM (Debian no GUI, and two tiny dockers with no GUI) Windows 11 VM options has Graphics Card set to the card. The other VM has VNC. Open Terminal, run "nvidia-smi", returns normally. Spin up the Windows 11 VM. Everything works fine on Unraid side and VM side. CPU usage is flat when expected, heavy when expected. Shut down Windows. VM fully stops. CPUs in Unraid dashboard start to get busy. Seems like probing the system for the GPU. It is now missing. Open Terminal, run "nvidia-smi" it returns "No devices were found". Cpu usage across one, two, or three cores go to 100% for a few seconds, falls flat, then one, two, or three cores go to 100% for a few seconds. This appears to be the probing. This goes on infinitely until I reboot. Here is what gets posted to the log just after shutting down Windows 11 and VM stops: Mar 24 23:17:54 mymachinename kernel: br0: port 3(vnet1) entered disabled state Mar 24 23:17:54 mymachinename kernel: device vnet1 left promiscuous mode Mar 24 23:17:54 mymachinename kernel: br0: port 3(vnet1) entered disabled state Mar 24 23:17:54 mymachinename kernel: vfio-pci 0000:2d:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=none Mar 24 23:17:54 mymachinename kernel: nvidia 0000:2d:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=none:owns=none ****** this is where it repeats over and over Mar 24 23:18:01 mymachinename kernel: NVRM: GPU 0000:2d:00.0: RmInitAdapter failed! (0x11:0x45:2706) Mar 24 23:18:01 mymachinename kernel: NVRM: GPU 0000:2d:00.0: rm_init_adapter failed, device minor number 0 Mar 24 23:18:06 mymachinename kernel: NVRM: GPU 0000:2d:00.0: RmInitAdapter failed! (0x11:0x45:2706) Mar 24 23:18:06 mymachinename kernel: NVRM: GPU 0000:2d:00.0: rm_init_adapter failed, device minor number 0 Mar 24 23:18:11 mymachinename kernel: NVRM: GPU 0000:2d:00.0: RmInitAdapter failed! (0x11:0x45:2706) Mar 24 23:18:11 mymachinename kernel: NVRM: GPU 0000:2d:00.0: rm_init_adapter failed, device minor number 0 Mar 24 23:18:16 mymachinename kernel: NVRM: GPU 0000:2d:00.0: RmInitAdapter failed! (0x11:0x45:2706) Mar 24 23:18:16 mymachinename kernel: NVRM: GPU 0000:2d:00.0: rm_init_adapter failed, device minor number 0 Mar 24 23:18:21 mymachinename kernel: NVRM: GPU 0000:2d:00.0: RmInitAdapter failed! (0x11:0x45:2706) Mar 24 23:18:21 mymachinename kernel: NVRM: GPU 0000:2d:00.0: rm_init_adapter failed, device minor number 0 Mar 24 23:18:26 mymachinename kernel: NVRM: GPU 0000:2d:00.0: RmInitAdapter failed! (0x11:0x45:2706) I am very competent. Just tell me what you need from me, I shall do/supply it.

Thank you. Please mark this as closed.

I am not a wikipedia fan, but this page lists it with citations of whre they got that information from. Wikipedia SMART Does that help? I have a ticket in with Teamgroup, the manufacturer of my SSDs, but they are stonewalling, suggesting these SSD's are consumer grade and not guaranteed for RAID setup.

@trurl I have attached the diagnostic zip. diagnostics-20240310-2107.zip

Hello, New unraid user here; 6.12.8. Every reboot within Unraid causes an increase in this SMART attribute by 22 (all filesystem drives) and 18 (all parity drives). All Brand New Equipment: ASRock Rack X570D4U AMD R7 5700x 4x 32GB Kingston ECC Server memory (QVL for board) 4x Teamgroup QX 4TB ssd drives (2 filesystem 2 parity array) Seasonic Focus Platinum PX-750 powersupply Not new equipment: Nvidia GTX 970 (for unreal compiling/building) Filesystem is set to XFS. In Unraid, controller type is set to default. I ran both the quick and extended tests within Unraid on one of the drives (the one with the really large value). Nothing was reported for any drive. The really large value I am sure is something I did, but I am not worried about that. I am worried about about the inability of the SSD's to program after each reboot. Nothing is on the filesystem, this is freshly set up as of last night. I can supply whatever logs you want, just ask. I have supplied the four drives' smart logs. TEAM_T2534TB_Disk1(Filesystem)_20240310-1626.txt TEAM_T2534TB_Disk2(Filesystem)_20240310-1626.txt TEAM_T2534TB_Parity1_20240310-1628.txt TEAM_T2534TB_Parity2_20240310-1626.txt