skwisgaarz

No need to apologise, thanks for the speedy responses, will keep an eye on it.

Yea nah nothing like that. Super weird.

So, I noticed in my plug in errors that docker patch had errored for some reason. Deleted that and installed the latest docker patch and the driver installed successfully. Sorry to make you chase this up, I should have noticed that error.

I have a static IP. Running that rate limit command shows 52 remaining under resources. Gotta be honest I don't fully understand your last paragraph. Do you mean wait until the reset number from the command lines up with the unix time and try to install the plug in asap after that?

Also, again not sure if this is relevant but I tried pinging github.com from the terminal and I get a response.

I'm just running an asus router, no firewalls or adblocking on my network. In the past I've been able to download the drivers fine with the same network set up. I ran that command but the terminal does nothing. Not sure if this is relevant but I clicked on the url in the command on a device on the same network and I get the attached api error.

I thought I would have an active internet connection on launch. I Rebooted but it was showing as a plugin error so I deleted it from that page and rebooted then tried installed the plug in again, but got this error when trying to install it

Separate to that actually though. I just updated from Unraid 6.12.4 to 6.12.8 and I got this driver download error. It said in the OS update dialog that I should hold off rebooting until this is sorted.

Ah that's a shame. Thanks for the quick response though.

Hi all, I'm wondering if there's any way (without a VM) to set the fan curve on an Nvidia GPU in unraid? I'd like to increase the temp at which the fans kick in, at this point it seems to try to keep the GPU under 50 degrees but it could happily run hotter than that and the fan noise is noticeable with where my server has to sit unfortunately.

Sorted this by changing the pw in the qbit config file back to the default then logging in and changing the pw again.

Got a real weird one... Sorted all my radarr/sonarr authorisation issues last night, but now the login information that works for arr to authorise with qbit won't let me log in to the qbit gui. I've triple checked the user/password in the arr download client settings is the same as what I'm using for the qbit web gui log in. I've also downgraded qbit in case it was something weird with the new version, still no luck. Anyone know if there's a way to bypass the qbit web gui login/have any idea what is going on here??

I know there's been some chat on this but since the newest Qbit update Sonarr/Radarr won't authenticate with Qbit, user/pw is 100% correct (and not the default since the newest update). Apparently whitelisting the specific IP works, but just wondering if there's any solution that doesn't involve permanently whitelisting IP addresses?

So I recently moved from Chrome to Firefox and my array read and writes looked super weird, it's not in xB/s anymore, not sure if it's total bytes or something, haven't done the math, but the numbers don't go to 0 when the drives aren't in use so it doesn't seem to be a measure of speed. I went back to chrome to check it wasn't some unraid setting and it still looks fine. Took a screenshot of both chrome and firefox at roughly the same time, attached. It's clearly not an issue with unraid, but I was hoping someone knew what was going on. I did some googling but can't find anything else about this issue.

Sorry had to sleep. Changed nothing and reset the server this morning and it seems to be working and stable now so Issue resolved for now. Will close the github issue. Thanks for your help here.

Lol, yea i'm an idiot. Unfortunately fixing all that still hasn't resolved the issue though. Not ruling out my own stupidity here still obviously...

Posted there, thanks for your help mate.

Yea honestly i'm not even sure how to look in to fixing this if vexorian isn't sure what's going on with the docker. This post was just a long shot if someone familiar with the plugin had any ideas on docker-gpu communication. Will probs just have to wait as you say. Appreciate the response.

I've been speaking with vexorian on reddit who made a few test nvidia dockers for me, since the issue was apparently known in the past and fixed by them in the windows release, but not pushed as a docker yet, but even with those updated nvidia tagged repositories i'm still getting the 'Cannot load libcuda.so.1' error in dizque when I try to nvenc transcode (even though gpu transcoding is definitely working in plex so the nvidia plugin seems to be working fine), just can't get dizque to access my gpu for some reason.

Hey @ich777. Got your driver installed and plex HW transcoding working perfectly, thanks for putting this together. I'm having issues with another docker using nvenv transcoding though. I've got dizquetv going and set up right but when it tries to run a transcode using h264_nvenc it gives the error 'Cannot load libcuda.so.1'. Vexorian's not sure but they do seem to think it's some issue with the docker accessing the gpu. Any ideas?

Mine was 100% faulty ram just to clarify. Replaced ram and all errors disappeared.

So i'm trying to run a memtest, first I tried selecting the memtest boot option in the flash drive setting through unraid, that would just make the system go in to a reboot cycle. It would output the boot select option to the display and try to automatically run the memtest after 5 seconds as it should but then would just reboot straight away. Was able to boot back in to the OS as standard from this boot selection screen. Then tried creating a memtest bootable usb using the latest memtest download from http://www.memtest.org/#downiso. When I tried to boot from the UEFI option the system would just go straight back in to the bios. Tried the previous version of memtest (from 2013) and it would do the same thing. Then tried a different usb, same thing. I've been having all sorts of issues with my system that I think originate from my cache drive dying and copying the cache files over the the new drive (possible something corrupt in these files). But realistically this shouldn't affect my system's ability to run a memtest if i'm trying to run it direct from a bootable usb drive created using the official memtest boot drive creator, right? My system is an ASRock B450 Pro 4, Ryzen 1600, 16 gb Corsair Vengeance DDR4 ram.

Thanks for the quick reply. A reboot fixed it, not sure why, not a good sign really...

Anyone had any issues with the latest Jackett update? I'm getting the attached error. I can run other docker updates no problem, it's just Jackett so far.

I've come across this exact error, do you recall what fixed it?