Posts by austinalex23

Quote from chris_kmn

ok so there is a known issue with the 5.9 kernel and nvidia driver. you have to roll back to the 5.8 kernel.

You can do this in the OMV extras "Kernel" tab. Change it to 5.8 and reboot. you should also hit the button "hold current kernel" that you don't update it the next time.

Thank you 1000000 times for letting me know this page exists. The amount of times my server has rebooted to a newer kernel and my Nvidia runtime containers didn't start until I reinstalled the driver........

Quote from tama777

I think this is a network or client side error and not a hardware transcoding bug because it works on the Android app.

Yeah I'm not sure what's going on. Transcode streams don't work at all in Firefox on my laptop or desktop. It kinda works in Edge. Doesn't work on the Plex application, kinda works in the Plex media player application (which I just figured out is different than the Plex application I have been using). Still works pretty perfectly on my Roku TV and phone. Weird stuff.

Can say that after first trying to get HW transcodes to work over a month ago that last night it actually happened for the first time!

Transcoded streams break on the Windows application and browser but it works fine on the Android and Roku apps but that's not going to ruin my good mood.

Quote from tama777

If you fix it so there's no space?

Code

ldconfig = "/sbin/ldconfig"

Alright now it works! I'll get Plex set up and see how it goes. Thanks again for the help.

Quote from tama777

What is the contents of /etc/nvidia-container-runtime/config.toml, please copy and paste here.

disable-require = false
#swarm-resource = "DOCKER_RESOURCE_GPU"

[nvidia-container-cli]
#root = "/run/nvidia/driver"
#path = "/usr/bin/nvidia-container-cli"
environment = []
#debug = "/var/log/nvidia-container-toolkit.log"
#ldcache = "/etc/ld.so.cache"
load-kmods = true
#no-cgroups = false
#user = "root:video"
ldconfig = "/ sbin / ldconfig"

[nvidia-container-runtime]
#debug = "/var/log/nvidia-container-runtime.log"

Quote from tama777

My Openmediavault System is OMV5.3.9-1 with Linux 5.4.0-0.bpo.-amd64 kernel and NVIDIA GeForce GTX1660. Plex hardware transcoding works for me based on the following (If Plex doesn't hardware transcode, check this video) :

Step 1: Install the NVIDIA driver based on the second option (How to install NVIDIA driver by using the official nvidia.com package step by step instructions).

_{(If you are installing another bpo kernel, you will need to reinstall the Nvidia driver compilation prerequisite: apt -y install linux-headers-$(uname -r) )}

Step 2: Install the Curl command-line utility:

Code

sudo apt install curl

Step 3: Installing the NVIDIA Container Toolkit:

Code

# Add the package repositories
distribution=$(. /etc/os-release;echo $ID$VERSION_ID)
curl -s -L https://nvidia.github.io/nvidia-docker/gpgkey | sudo apt-key add -
curl -s -L https://nvidia.github.io/nvidia-docker/$distribution/nvidia-docker.list | sudo tee /etc/apt/sources.list.d/nvidia-docker.list

sudo apt-get update && sudo apt-get install -y nvidia-container-toolkit
sudo systemctl restart docker

Step 4: Installing nvidia-container-runtime:

Code

sudo apt-get install nvidia-container-runtime

Step 5: Edit /etc/nvidia-container-runtime/config.toml eg. nano and replace "@ / sbin / ldconfig" with "/ sbin / ldconfig", then save the file. (Thanks to lyon667!)

Step 6: If you want NVIDIA to be the default Docker runtime, modify the contents of /etc/docker/daemon.json to:

Code

{
  "runtimes": {
    "nvidia": {
      "path": "/usr/bin/nvidia-container-runtime",
      "runtimeArgs": []
    }
  },
  "default-runtime": "nvidia"
}

Step 7:

Code

sudo systemctl restart docker

Step 8: Install linuxserver/plex

For example, it looks like this to me:

Code

docker create \
  --name=Plex \
  --net=host \
  -e PUID=1000 \
  -e PGID=100 \
  -e VERSION=public \
  -e NVIDIA_VISIBLE_DEVICES=GPU-s96kfsd-3sdf0-g98f-7164-cd76d697872e \
  -e NVIDIA_DRIVER_CAPABILITIES=compute,video,utility \
  -v /srv/dev-disk-by-label-XXXXX/Movies:/Movies \
  -v /srv/dev-disk-by-label-XXXXX/AppData/Plex:/config \
  --restart unless-stopped \
linuxserver/plex

Display More

Maybe it helps.

cuda.jpgPlex.jpg

Display More

After following all these steps I get the following error after running the test command for the Nvidia cuda container:

NVIDIA-SMI couldn't find libnvidia-ml.so library in your system. Please make sure that the NVIDIA Display Driver is properly installed and present in your system.
Please also try adding directory that contains libnvidia-ml.so to your system PATH.

Unfortunately this is the same error I got when I first started out trying to get this stuff to work.

FWIW, here is my nvidia-smi output. I have the same driver version as you, which is the latest. Previously I tried a 390 legacy driver but it complained that it was out of date when I ran the cuda container command.

Fri Mar 27 17:03:59 2020
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 440.64       Driver Version: 440.64       CUDA Version: 10.2     |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|===============================+======================+======================|
|   0  GeForce GTX 105...  Off  | 00000000:09:00.0 Off |                  N/A |
| 30%   30C    P0    N/A /  75W |      0MiB /  4038MiB |      3%      Default |
+-------------------------------+----------------------+----------------------+

+-----------------------------------------------------------------------------+
| Processes:                                                       GPU Memory |
|  GPU       PID   Type   Process name                             Usage      |
|=============================================================================|
|  No running processes found                                                 |
+-----------------------------------------------------------------------------+

Tama, thank you for the info. I'm going to be reinstalling OMV and giving it another go.

Quote from Methy

Hello,

just to be sure, do you have a plex license?

https://support.plex.tv/articles/115002178853-using-hardware-accelerated-streaming/

Yes I do have the Plex Pass. My problem is that the Nvidia driver never completely installs correctly so that docker can use the GPU.

Quote from smellylettuce

I was having the same issue (OMV 4). The metapackage doesn't seem to recognize the kernel version during the install process and just installs the latest version.

I got around this by going directly to nvidia's site and downloading the driver package there: https://www.nvidia.com/Downloa…Results.aspx/142567/en-us (the driver here isn't listed on the driver search, though a rudimentary google search managed to locate it) Looks like the OP may have been trying to install an incompatible version. I also did a purge of nvidia stuff prior to installation

Then I just moved it to one of my shared folders and executed it from there using 'sh'
Hope that helps, now I just have to muddle through the rest of the setup

-edit address OP initial issue

Display More

Have you been able to get everything working? I've been dying for days trying and failing and breaking and fixing things. (OMV 5, Kernel 4.19)

Quote from Kreavan

I'm adding an Nvidia Quadro p2000 card to my NAS and would like to know how I can implement that into my Plex docker for hardware transcoding. Can it be added to an existing Plex docker, or do I have to create a whole new one?

I followed the video from Techno Dad Life on creating the Plex Docker using the OMV docker creation GUI. https://www.youtube.com/watch?v=BNfk7ji4oh4

I've not had any luck finding any videos on how to include Nvidia GPU though. Can anyone please help?

Thank you!

Display More

I've been at it for 4-5 days and am having no luck. (OMV 5).

Quote from macom

This

"Hardware acceleration users for Nvidia will need to install the container runtime provided by Nvidia on their host, instructions can be found here:
https://github.com/NVIDIA/nvidia-docker"

is from here:
https://hub.docker.com/r/linuxserver/plex

Maybe it helps.

Display More

That's where I started too.

I've had a terrible time just installing Nvidia graphics drivers well enough for the docker runtime to work. I have a Reddit post looking for help, which is a sequel to a previous post (put in a handful of spots) that hasn't bore any fruit.

I've been beating my head against a wall for 2 days now.
I have installed the latest Nvidia driver (manually used wget to download the executable to the machine and ran the installer) and the nvidia-docker stuff as specified in the quickstart section on the Github page. I've done this many times over. I also installed the nvidia-container-runtime.

Trying things out with a command such as this

sudo docker run --gpus all nvidia/cuda:10.0-base nvidia-smi

Gives me this error
NVIDIA-SMI couldn't find libnvidia-ml.so library in your system. Please make sure that the NVIDIA Display Driver is properly installed and present in your system.Please also try adding directory that contains libnvidia-ml.so to your system PATH.

This error has been all over the internet and I haven't found anything that fixes it for me. I did add the "/usr/lib/x86_64-linux-gnu" directory to PATH and confirmed libnvidia-ml.so IS in the directory.
A lot of the posts I saw said that when they had this issue they couldn't run the "nvidia-smi" command, which I run without issue.
I do have the necessary NVIDIA environment variables set in my Plex container, and I set the runtime to 'nvidia' in Portainer.

Anybody know what the heck is going on? I'm losing my mind.

Quote from cabrio_leo

Do you have a space in the label name of the drives? In the past there were issues with such NTFS drives.

It is not recommended to mount drives manually by the CLI, because this mount is then not contained in the configuration database of OMV. Therefore you can´t create any shares and so on over the WebUI.

I think the problem was a space in the disk labels. Through renaming those and some combination of unmounting and removing a mount point, I was able to get 1/2 of them fully working. Still banging my head against the other one.

Edit: I've now gotten the other drive to mount properly as well.

Hello all,

I've just installed OMV5 on my system. I have a boot SSD and 4 hard drives. 2 of those drives (250GB each) were empty and have been formatted with ext4 and are working swimmingly. 2 of my drives are NTFS drives with about 1.6TB of data on each (movies and shows for plex). I know that the recommendation is to buy a new drive, move the stuff over, and reformat to ext4. I will do that in the future.

But for now, When I attempt to mount the NTFS drives through the web interface I get a long error message. I was able to mount the drives via the command line, but I can't create shared folders or interact with the present folders on the NTFS drives from the web interface. The only drives that show up in the dropdown menus are the ext4 drives.

I've edited the drive permissions so they are the same as the ext4 drives. I can read and write info to the NTFS drives from the command line. Is there any way to get the web interface to play nice with them? I've attached an image of the mount error I get.

PS: I did create an OMV5 VM last week to test out adding a Windows-created NTFS drive (created some virtual hard disks) with data to an OMV install and I didn't have any issues.