October 19, 20196 yr 9 hours ago, Jhp612 said: Will the Rc1 build work for rc3? If you follow the Unraid upgrade path, you will lose Nvidia support, as you will revert to stock Unraid (no extra drivers). The way to keep it working is to upgrade via the plugin. And they may not necessarily be supplying all RC versions. Long story short, no. If it's available from the plugin, yes. Otherwise sit tight.
October 19, 20196 yr Just uploading v6.8.0rc3 Took a while as any time there is new OOT drivers added I need to work out how to add them.
October 19, 20196 yr 4 minutes ago, CHBMB said: Just uploading v6.8.0rc3 Took a while as any time there is new OOT drivers added I need to work out how to add them. As always THANK YOU
October 19, 20196 yr 6 hours ago, dgreig said: Are you guys planning on releasing new versions for other 6.8 rc series or just waiting until 6.8 goes final? thanks so much for releasing rc1 as the 6.8 series has been a long time coming and still getting to use my P2000 is a fantastic bonus. cheers! I'll try and make builds for each rc series, home/work/family gets in the way sometimes, and if there are changes to the build in terms of out of tree drivers or other issues then it can take longer. To make the builds takes about an hour, so I left it running when I went to bed last night after making so many silly errors before as I needed to sleep. Woke up this morning and checked that it's working as expected so uploaded it.
October 19, 20196 yr Anyone else getting this via the plugin when checking for new builds? Warning: file_get_contents(https://lsio.ams3.digitaloceanspaces.com/?prefix=unraid-nvidia/): failed to open stream: HTTP request failed! HTTP/1.1 503 Service Unavailable in /usr/local/emhttp/plugins/Unraid-Nvidia/include/exec.php on line 45 Warning: Invalid argument supplied for foreach() in /usr/local/emhttp/plugins/Unraid-Nvidia/include/exec.php on line 47 Warning: array_keys() expects parameter 1 to be array, null given in /usr/local/emhttp/plugins/Unraid-Nvidia/include/exec.php on line 51 Warning: Invalid argument supplied for foreach() in /usr/local/emhttp/plugins/Unraid-Nvidia/include/exec.php on line 51 Warning: Invalid argument supplied for foreach() in /usr/local/emhttp/plugins/Unraid-Nvidia/include/exec.php on line 70 Warning: array_multisort(): Argument #3 is expected to be an array or a sort flag in /usr/local/emhttp/plugins/Unraid-Nvidia/include/exec.php on line 73 Warning: Invalid argument supplied for foreach() in /usr/local/emhttp/plugins/Unraid-Nvidia/include/exec.php on line 91 Warning: Invalid argument supplied for foreach() in /usr/local/emhttp/plugins/Unraid-Nvidia/include/exec.php on line 103
October 19, 20196 yr Anyone else getting this via the plugin when checking for new builds? Warning: file_get_contents(https://lsio.ams3.digitaloceanspaces.com/?prefix=unraid-nvidia/): failed to open stream: HTTP request failed! HTTP/1.1 503 Service Unavailable in /usr/local/emhttp/plugins/Unraid-Nvidia/include/exec.php on line 45 Warning: Invalid argument supplied for foreach() in /usr/local/emhttp/plugins/Unraid-Nvidia/include/exec.php on line 47 Warning: array_keys() expects parameter 1 to be array, null given in /usr/local/emhttp/plugins/Unraid-Nvidia/include/exec.php on line 51 Warning: Invalid argument supplied for foreach() in /usr/local/emhttp/plugins/Unraid-Nvidia/include/exec.php on line 51 Warning: Invalid argument supplied for foreach() in /usr/local/emhttp/plugins/Unraid-Nvidia/include/exec.php on line 70 Warning: array_multisort(): Argument #3 is expected to be an array or a sort flag in /usr/local/emhttp/plugins/Unraid-Nvidia/include/exec.php on line 73 Warning: Invalid argument supplied for foreach() in /usr/local/emhttp/plugins/Unraid-Nvidia/include/exec.php on line 91 Warning: Invalid argument supplied for foreach() in /usr/local/emhttp/plugins/Unraid-Nvidia/include/exec.php on line 103 Yeah, Digital Ocean has an issue at the minute with it's spaces, and that's where our builds are.Sent from my Mi A1 using Tapatalk
October 19, 20196 yr Quote Investigating Our Engineering team is investigating an issue with Object Storage and Spaces performance in AMS3 region. During this time, you may experience issues with accessing Spaces. We apologize for the inconvenience and will share an update once we have more information. Posted about 1 hour ago. Oct 19, 2019 - 10:56 UTC
October 19, 20196 yr Can keep a track on things here https://status.digitalocean.com/incidents/sb6p4w9ksqlg?u=d1yxkjzvvdxr
October 20, 20196 yr On 10/18/2019 at 12:32 PM, Pducharme said: Someone already told me this simple Rule : GPU can be shared among Dockers (at the same time) GPU dedicated to a VM is only available to that VM until that VM is powered down Applying that rule to your question, I would say that no, it won't fallback on quicksync on the docker. If you turn off the VM, then maybe I guess ? (can't test since i'm running a Ryzen 9 3900x on my Unraid, so no quicksync). @Pducharme Sorry If I was not terrible clear, on the Intel System, it has both a Discrete GPU (Plugged in card) and QuickSynce, part of the graphics integrated into the CPU. I have the NVIDIA set at the card the Dockers and the one VM to use, I know that if I have the VM running, the dockers can not use it, but will they fall back to the Quicksync Graphics integrated into the CPU, so just software?
October 20, 20196 yr 2 hours ago, wesman said: @Pducharme Sorry If I was not terrible clear, on the Intel System, it has both a Discrete GPU (Plugged in card) and QuickSynce, part of the graphics integrated into the CPU. I have the NVIDIA set at the card the Dockers and the one VM to use, I know that if I have the VM running, the dockers can not use it, but will they fall back to the Quicksync Graphics integrated into the CPU, so just software? I believe this could happen with Emby as you can select multiple transcoders but plex just uses either one or the other. From our testing of VM's using GPU's that are assigned to containers, we found it locked up it up.
October 20, 20196 yr 1 hour ago, j0nnymoe said: I believe this could happen with Emby as you can select multiple transcoders but plex just uses either one or the other. From our testing of VM's using GPU's that are assigned to containers, we found it locked up it up. Yeah the one scenario was, if a gpu is being actively used for transcoding when you start a VM with that gpu passed through, unraid gets locked up. If you start the VM when there is no active transcode, the gpu will no longer be available to the container so it will fall back to something else, no crashes. Whether it falls back to igpu or software, I don't know the answer. I never tried it. But it's really a plex question.
October 21, 20196 yr Has anyone wrote a bash script to enable these commands after array has started? nvidia-smi --persistence-mode=1 fuser -v /dev/nvidia* It allows the cards to go into p8 when not in use. (Save power mode) I ain't very good at bash scripts.
October 21, 20196 yr 4 hours ago, Dazog said: Has anyone wrote a bash script to enable these commands after array has started? nvidia-smi --persistence-mode=1 fuser -v /dev/nvidia* It allows the cards to go into p8 when not in use. (Save power mode) I ain't very good at bash scripts. Use the user scripts plugin.
October 22, 20196 yr Can anyone running Nvidia 6.8 rc3 confirm that 6.8 is actually being installed? And that it is not installing 6.7.3 rc4?
October 22, 20196 yr Not sure if this is technical enough, but it does have the full HTML login screen which does not exist in <6.8. Kernel version I have is 5.3.6.
October 22, 20196 yr 7 hours ago, sittingmongoose said: Can anyone running Nvidia 6.8 rc3 confirm that 6.8 is actually being installed? And that it is not installing 6.7.3 rc4? Yes.
October 25, 20196 yr On 10/20/2019 at 7:39 PM, Dazog said: Has anyone wrote a bash script to enable these commands after array has started? nvidia-smi --persistence-mode=1 fuser -v /dev/nvidia* It allows the cards to go into p8 when not in use. (Save power mode) I ain't very good at bash scripts. You could probably put that in the go file.
October 25, 20196 yr You could probably put that in the go file.Interesting, I have problem with the P state on my Nvidia card too. Can you pls explain where this go file is, would like to test if it can help me solve this temporary while waiting for a bug fix.
October 25, 20196 yr @Sic79 - The go file is in /boot/config/go. It is run on every boot. Very handy for making sure things get run when you reboot the box.
October 25, 20196 yr 2 minutes ago, Sic79 said: Interesting, I have problem with the P state on my Nvidia card too. Can you pls explain where this go file is, would like to test if it can help me solve this temporary while waiting for a bug fix. The go file is a file which is run when the server is booted. It exists at `/boot/config/go`
October 25, 20196 yr I'm having some difficulty getting this working. I have installed a P2000 card, and installed the plugin, downloaded and installed the Nvidia Unraid Build. When I do a fresh reboot, I can go to the settings->Unraid Nvidia page and I see the GPU listed there. But after a few minutes, if I go back there, its gone and all the GPU entries are blank. I am not passing the P2000 to any VM. I have added it to only my plex docker. diag attached if it helps. Edit * Nevermind, I am an idiot. stupid mistake. all seems to be working now. and Thanks for the awesome work. Edited October 26, 20196 yr by mattekure reuploaded new diag.
October 26, 20196 yr The go file is a file which is run when the server is booted. It exists at `/boot/config/go` Thanks
October 26, 20196 yr I just tried to install v6.8.0/rc4 and now UnRaid won't even try to boot. It comes out of POST and just sits there. Hints on how to recover my previous working working version? thanks,
Archived
This topic is now archived and is closed to further replies.