So I'm pretty new to Unraid, only bought a license after my 30 day trial about a week ago. I was initially testing the system on a ryzen 3600x/rx480. When I was ready to move my stuff over from my windows machine, I took the hardware with it, a ryzen 5950x/1070ti, the motherboard stayed the same from the 3600x/1070ti system.

When I was on the 3600x/rx480, I could get gpu passthrough to work on my VM, however with the 1070ti, I am unable to do passthrough. As when i select either the gpu and/or the gpu sound and i run the VM, it completely locks up UNRAID and prevents a clean shutdown or spindown of the array. dockers continue to run, I can access sections that don't include anything to do with the VM, so main is accessible, but the dashboard is not, settings accessible, but the vm settings arnt. If i enter these through remote, it cuts the connection and it can't be reestablished until the system is rebooted, the gui running off of the system is still accessible, but those section never load.

When this happens I have to then hard shutdown the system and delete the libvert image in VM settings before the array starts on next boot. If I'm not fast enough the array will start and it will lock up again, the vm doesnt even have to be on. this happens with windows 10 and ubuntu. ubuntu was never even installed on the previous system, so its completely fresh, it doesn't even get a chance to install. I have the gpu working in plex for encoding, so I know unraid is capable of using it. This also happened before setting up plex gpu usage, so I don't think its related.

Is there some proper steps to take to fix this? Preferably I would like to fix the the gpu passthrough but without causing the issue again, as I'm not confident hard shutting down the system without the array going down properly, I would rather not risk my data more than I need to.

Remember I'm new, so if its outside of the gui, or a bit more complicated, please tell me how to do it as I probably don't know how.

I'm including the diagnostics zip, I have the 'Anonymize' setting enabled, so some info may be missing.

Thanks for any help rendered



EDIT: I figured out nvenc handbrake docker.

pooplexserver-diagnostics-20240103-0206.zip

Edited January 4, 20242 yr by Vulkandr

looks like someone ran across the same issue on my original post when i couldnt figure out how to get unraid working again. So this isn't an isolated problem to just me, but may be indicative of a bigger issue. 
 

 

1 hour ago, Vulkandr said:

looks like someone ran across the same issue on my original post when i couldnt figure out how to get unraid working again. So this isn't an isolated problem to just me, but may be indicative of a bigger issue. 
 

 

Is tbe lockup when you shutdown or start vm?

10 hours ago, SimonF said:

Is tbe lockup when you shutdown or start vm?

It begins when you start a vm with gpu passthrough, it does not stop til you delete libvert before the array starts, once the array starts the problem persists even after a restart. it's not a complete lock up, it just breaks network access(including local net) as soon as you try to access any area of the ui that involves vm like the dashboard, and on the native machine when using the gui, it doesnt let you into any area that has any relevance to vm, but you can still enter areas like Main or apps page even after trying to access these areas. It also prevents a shutdown of the array, which prevents a restart. you are forced to do a hard reset to get things running again. My guess is the array gets stuck on trying to shut down the VM or the domain folder share.

I have been working through getting GPU passthrough working for a VM and found this post. I believe I know what OPs issue was because I experienced the same thing and wanted to share in case it might help someone else. I have learned that to give a VM a GPU it has to be entirely exclusive to that VM, so if the GPU is used in any docker then starting the VM will cause major unraid issues. That part is pretty well documented and I had taken care of that from the start.

 

What I didn't find until much later after I continued to have problems was that you cannot use GUI mode in unraid either, because it engages the GPU. In my case I think I have always booted to GUI mode because I keep a local monitor attached in case I lose network access to the server. After changing my boot config to no GUI mode I haven't had any more issues with GPU passthrough. Not being able to partition/share the GPU kinda sucks in a system like unraid, and it would be great if it could be improved but I don't know if that is within the control of the unraid devs.

THat's interesting... My system locks up if I try to run it with GUI mode... If I just boot with CLI it's fine... I thought this changed with an update from Unraid but it might have coincided with a bios update that changed the ability to NOT boot using the external GPU...

 

I wondered if the OP was running the NVIDIA drivers in unraid?