zer0zer0

Members
  • Posts

    26
  • Joined

  • Last visited

Posts posted by zer0zer0

  1. On 9/18/2021 at 4:14 PM, sergio.calheno said:

    Hey,

    First of all, thanks for the great docker!

    However I'm trying to add this whitelist but for that I need python3 inside the docker. Any idea I can get a walk through on how to do it? I've tried searching for it, but I don't get a concrete answer on how to install python3 inside a docker container (or if it's even possible). I tried entering in the console "sudo apt-get python3" but to no avail...

    Any help would be greatly appreciated.

     

    Thanks!

     

    Hmm, apt installing python3 and then running those whitelist scripts works perfectly for me...

     

    sudo apt update

    sudo apt install python3

     

     

    • Thanks 1
  2. 1 hour ago, ich777 said:

    What is failing exactly?

     

    Is the file in the download folder and Sonarr doesn't moves it to the destination?

     

    I made things as simple as possible and I'm just using /torrents as my path mapping, so I don't think that's the issue.

    Yes the file gets downloaded and I can see it sitting in the /torrents directory and it starts seeding

     

    I've also run DockerSafeNewPerms a few times, but that hasn't changed anything.

    I can get around it by using nzbToMedia scripts for the time being, but it's weird I can't get it working natively :(

  3. Anyone else having issues getting torrents to complete with Sonarr?

     

    I have paths mapped properly, and have tried qbittorrent, rtorrent, deluge, etc. without any luck :(
    Sonarr sends torrents perfectly, and the torrent clients download them perfectly

    Then the completion just doesn't happen and there's no logs

  4. 17 minutes ago, Spucoly2 said:

    There is no running processes against my GPU when running 1080 movie.

    nvid.PNG

     

    I've seen times when nvidia-smi doesn't show anything but it is actually transcoding.

    You should be sure you are forcing a transcode and then check in your Plex dashboard for the (hw) text like this...image.png.725306e94090d95d347dec3fd556c5f3.png
     

  5. 3 hours ago, ich777 said:

    This was descussed a few times here in the thread, the solution was actually to switch to the plexinc container or linuxserver container.

    You can also hook @binhex woth a short message or a post in his thread, I think he runs his container just fine with the Plugin.

     

    binhex plexpass container is working well for me :)

  6. hmmm, seems it might even be a SuperMicro X10 and/or Xeon E5 v3 specific issue.

    No issues on my E3-1265L v3 running on an AsRock Rack E3C224D2I

     

    @StevenD can run 6.9rc2 with hypervisor.cpuid.v0 = FALSE on his setup with ESXi 7, SuperMicro X9, and E5-2680v2 cpu's

     

    Thanks to @ich777, I can confirm that you can run the latest 6.9rc2 with a modified bzroot that has the 6.9.0-beta35 microcode :)

  7. 5 hours ago, ich777 said:

    Sorry I really want to help but I don't know much about ESXI. Eventually @StevenD can help, isn't there also a subforum here in the forums about virtualizing Unraid?

     

    I talked to @StevenD and dropped back to UnRAID version 6.9.0-beta35 like he's running, and this issue is resolved :)

    image.png.7b113d8059634db1f3993c4600df31c5.png

     

    • Like 3
  8. To follow up on my issues, I can boot if I choose just one cpu, so it's probably not an issue with this plugin specifically.

    It is more likely to be UnRAID itself.

     

    If I set one cpu and also hypervisor.cpuid.v0 = FALSE in the vmx file I can get it to boot and the plugin appears to be working as expected.

    @ich777- if you can think of any logs etc. to get this resolved let me know

     

    image.png.ce49059c991091dfc429df6a2f466913.png

  9. I have pretty much the exact same issue!
    If I add hypervisor.cpuid.v0 = FALSE, booting freezes right after loading bzroot.

    If I set just one cpu I can boot just fine
     

    I'm not sure it's Nvidia specific as I still get the error even without my Nvidia card passed through to the virtual machine.

    And it won't boot even without any hardware at all passed through :(


    ESXi 6.7 with the latest patches

    UnRAID 6.9.0-rc2

    Nvidia Quadro P400

     

    A plain Ubuntu 20.10 instance with hypervisor.cpuid.v0 = FALSE set works as expected. No problems at all. 

    Mine was also working great with linuxserver.io nvidia builds.

    So it’s definitely not a hardware or esxi issue. 

     


    image.png.4cf066ad4b8625c7e0ee2a90d8688bdc.png
     

  10. On 1/6/2021 at 6:17 AM, StevenD said:

    I'm running unRAID virtualized under ESXI 7 with an RTX 4000, using @ich777 plugin.  I don't recall doing anything special to get it to work.  I do have these settings:

    
    pciHole.dynStart 3072
    
    hypervisor.cpuid.v0 FALSE

     

    but I don't recall specifically setting them.

     

    That's weird that yours is working and mine isn't.

    I also just tested that it works as expected with a plain Ubuntu 20.10 instance with hypervisor.cpuid.v0 = FALSE set. No problems at all. 

    Mine was working great with linuxserver.io nvidia builds.

    So it’s definitely not a hardware or esxi issue. 

    I have the following setup:

    • ESXi 6.7 with the latest patches
    • UnRAID 6.9.0-rc2
    • Nvidia Quadro P400


    Passing through both the nvidia card and audio device. 
    Other passed through devices like sas hba, and nvme drives work perfectly. 
     

    Without any flags in the vex file I can boot the UnRAID virtual machine and can see the Nvidia card

     

    root@XXXX:~# lspci | grep NV
    03:00.0 VGA compatible controller: NVIDIA Corporation GP107GL [Quadro P400] (rev a1)
    03:00.1 Audio device: NVIDIA Corporation GP107GL High Definition Audio Controller (rev a1)

     

    But anything else has errors like

    root@XXXX:~# nvidia-smi 
    Unable to determine the device handle for GPU 0000:03:00.0: Unknown Error
     

    Nvidia Driver Settings page gives me this error

    image.png.1e9ba10aacf2d0fbbc75f12cbda8684c.png

     

    If I add the hypervisor.cpuid.v0 = FALSE variable to the vmx file it freezes after bzroot and won't boot :(

    image.png.a6a0220caefb54b412211a6af509c513.png
     

  11. 14 hours ago, ich777 said:

     

    Are you using 6.8.3 or 6.9.0RC2?

    I know very littly about ESXi7 so I really can't help here.

    Eventually this can help: Click

     

    Tried all of the different advanced variables, without any luck, so I gave up and did a bare metal UnRAID with a nested ESXi instead :D

    • Like 1
  12. Anyone have any luck getting this working with an UnRAID host running on ESXi 7 with pass through?

    Mine either freezes at boot time, or if I change some advanced variables around I can get it to boot, but get a message on the plugin page saying "unable to determine the device handle"

     

    I have tried the normal advanced settings you need for ESXi and nvidia passthrough like setting hypervisor.cpuid.v0 = “FALSE” and pciHole.start = “2048” but I'm not having much luck so far :(

  13. On 2/16/2018 at 9:12 AM, clowrym said:

     

    Here ya go!!

     

    
    root@Tower:~# cat /sys/devices/system/cpu/cpuidle/current_driver
    none
    root@Tower:~# cpufreq-info -d
    root@Tower:~# modprobe acpi-cpufreq
    modprobe: ERROR: could not insert 'acpi_cpufreq': No such device
    root@Tower:~# cpufreq-info -d
    root@Tower:~#

     

     

    Same sort of symptoms for me as well on a virtualized Unraid on ESXi7.0 running on a SuperMicro X10SRH-CF and Xeon 2680v4.

     

    Fix common problems plugin is telling me I don't have a CPU Scaling Driver Installed.
    Although I can see my CPU is not at 100% and looks pretty normal to me?

    image.thumb.png.8e358fe74266fe969343eda9ac10096f.png

  14. I'd like to request that the included and excluded disks are added to the shares overview page.

    I find it cumbersome to have to click into each share individually to see which disks have been assigned.

     

    It seems like it would be a really simple addition to either include a column or have an element you hover over or click to drop down.

    The hover or drop down might be better so it can accommodate systems with lots of disks.

     

    Please forgive me if there is some other way to get an overview showing this for all shares

     

    An quick and dirty example of how it might look:

    image.thumb.png.e65a1346b12ce2c0f73dbf5a356f7c76.png

     

    • Like 3
  15. On 11/20/2019 at 8:42 AM, limetech said:

    We have multiple-pool support coming in 6.9 release.  After that we can look at adding a UI to create vdisks that map to iscsi targets.

     

    Please do me a favor however: please move any non-Unraid discussion to another forum.

     

    Did iSCSI make it into the new 6.9 beta release, or will it hopefully make it's way into the RC? :D

    • Thanks 1
  16. So...I have Unraid running under ESXi 7.0 as well, but can't do PCI passthrough and also have Hardware Virtualization enabled so I can use VM Manager.

    If I try and enable it I get an error - "Failed - PCI passthrough devices cannot be added when Nested Hardware-Assisted Virtualization is enabled."

     

    Is there a hack to get this to work?

    Or has it always been the case that you can only choose one of the other?

    image.png.f4e2db241d1b8eef43d476ce5dc5a2cd.png
     

  17. 9 hours ago, saarg said:

    Hard for us to say anything when you haven't posted any log, docker run command or screenshot of port forwarding.

    The nginx part isn't started until the certificate is created

    All I needed to know is if it should be listening or not, and you answered that perfectly! Thank you :D

     

    I also noticed the actual container ports were stuck on port 81/444 for some reason, so I deleted and recreated it and it started up listening on 80/443, and also switched to dns validation, and things are working as expected now :)

  18. Trying to get the Letsencrypt container working with a very standard setup but it doesn't seem to be listening on any ports.

    I have the docker container configured with a bridge network, and port 81 and 444, with no conflicts.

     

    Once it's running should I then be able to hit <UNRAIDIP>:81 and <UNRAIDIP>:444 ??

    Or do a netstat inside the docker container and see it listening on those ports?

     

    My port forwards from the outside are perfect but it's definitely not listening like I would expect :(