hocky

OK, thanks - I´ll try that out. At least I now know it´s not something obvious.

Hm, no idea? Or did I break a rule that got me on the ignore list? 🫤

Another observation: When I remove the NVidia card from device manager and then do a reboot, it gets detected correctly and the Nvidia drivers get installed and I can use it properly. But after another reboot, I get the issue described above (yellow exclamation mark in device manager and code 12 error).

Hi, I´ve got a Windows 10 VM running on my Unraid 7.0.1 server. A GTX1080 Ti is passed into the VM. In general, this works, but not all the time. Pretty often, the GPU is not correctly included into the system, leading to a Code 12 error (not enough resources available) in Windows device manager and the Nvidia driver not being loaded. GPU-Z is detecting the GPU correctly. The funny thing is, that sometimes the GPU is correctly included and fully usuable after boot-up. Any ideas where to look at? EDIT: Another interesting thing I noticed: the vm only gets a network connection when I define VNC as the primary and the GTX1080 as the secondary graphics adapter. As soon as I define the GTX1080 as the primary and I boot up the vm, it doesn´t gets a network connection. It doesn´t respond to a ping and my DHCP server is not getting any DHCP request, so I guess the network driver doesn´t even get loaded. Thanks, Hocky

These were attached to a RAID card I removed for testing. I think the RAID card is/was part of the problem. I rearranged the drives a bit and now everything´s attached to the mainboard´s SATA ports. I´ll look into tidying up the system in a couple of weeks when I´ve got more time.

Thank you - that fixed it! We´re back in business! Thanks a lot for your support. I´m happy the system is up and running again, but I´ll definitely schedule some maintenance time - it definitely needs some love. Enjoy your beer!

Seems to be the issue is a mixture of hardware and config issues. I managed now to boot up the system will all drives attached and the array´s running fine. However, the network config seems to be screwed up as I´m not able to ping the server from the outside and also not being able pinging from inside to the outside. I think there´s some routing mismatch from configurations from the past and I´m not able to change it.

OK, that works.

With all the cards removed, trying to do a standard boot gets stuck into this screen now:

Thanks for the quick responses! I removed a couple of cards (GPU, NIC, RAID) and I´m now able to boot into the console GUI. External access via putty or to the WebGUI is still not possible. Yes, not possible. Also via putty. Yeah, these two are sometimes not recongnized. But they are now. Yes, it´s the latter. Never touch a running system. As I mentioned, the server was running stable for quite some time now and I´m not chasing new features, so I left it as it is. Attached is a new diagnostics file I collected after removing non-mandatory cards. unraid-diagnostics-20250325-1111.zip

Since I was able to boot into the console, I was able to create a diagnostics file. See attached. unraid-diagnostics-20250325-1013.zip

Hi, my UNRAID server (which was happily running the last couple of years) seems to have restarted over night and now doesn´t boot anymore. It starts with the boot precedure, but then it´s stuck at the screen you can see attached. I am able to successfully boot into non-GUI safe mode, but I don´t know where to go from there. Any help appreciated. Thanks, Thorsten

Yeah, trying a different container might be worth a try.

Mh, that´s strange. Well, i´ve got 12 cores of which 5 are in use by VMs. One other docker (Ubiquiti Unifi server) is running. Overall load of the server is around or below 10% and not even half the RAM are currently utilized... Having said that, i think there must be something else...

Been, there, done that. Didn´t help. Also reduced the view-distance to 6 in the server.properties.