Posts by austinalex23

    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........

    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.

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

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

    Code
    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.

    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)

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


    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.

    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.