Rick Gillyon

  • Content Count

  • Joined

  • Last visited

Posts posted by Rick Gillyon

  1. 1 minute ago, sittingmongoose said:

    Yea I did all that :/ kinda stumped.  When you say touch from shell, you mean just from unraid terminal?  Or within the docker.

    Yep, just from terminal. You have the "extra parameters" on the docker template?

  2. 11 minutes ago, sittingmongoose said:

    Has anyone gotta intel igpu working with emby on 6.9.1?  I have tried for two days but cant seem to get it to work.  Nvidia works fine though.

    Working here. How did you try to enable it?


    In 6.9.1 just run "touch /boot/config/modprobe.d/i915.conf" from shell, remove old lines for this gpu from your go file, and reboot. The usual extra parameters should be in your Emby docker config.

  3. 5 hours ago, nraygun said:

    Thanks @Rick Gillyon - that did it, but I think a little too well!

    I could swear I had my appdata and domains on the cache before I upgraded. When I set the cache to prefer on these two shares, it did move the contents to the cache, but it exceeded the size of the cache drive.

    Is there a way to only move some of the VMs to the cache drive? Does everyone run docker containers off the array?

    I run dockers and appdata from cache. If you set system and appdata shares to Cache:Prefer and ran out of space, it should already have mixed array and cache - nothing is missing. If you want to change the mix of what's on array and cache (e.g. to get certain VMs on cache), you'll have to move things around manually. If you want to move the appdata share to the array, just set it back to Cache:Yes and invoke the mover.


    Also worth checking that none of your dockers are massive, as some can misbehave with the logging.

  4. 14 minutes ago, nraygun said:

    I upgrade to 6.9.1 from 6.8.3 and it went well using the above process from @NAStyBox! Thanks unRaid Devs!


    However, I think step 3 moved my VMs off of the SSD cache and into the array.

    Can I just move them back to the SSD?

    Set the share back to Cache:Prefer and run the mover.

  5. I upgraded to 6.9.0 and decided to reformat my cache (nvme pool) using the Mover process on this page:

    I went through the steps, checked all my cache content had moved to the array, then reformatted cache and brought up the array. But no dockers on my docker page, all gone. The docker location is correct:



    And my docker.img is there:



    The date implies it's been written since the restart though.


    Any ideas? Diagnostics attached.


    EDIT: Looks like I just need to add them all again. No idea why they would disappear though.



  6. 7 minutes ago, Capt.Insano said:



    Emby will not use hardware transcoding unless I also issue the following command and then restart the container:

    chmod -R 777 /dev/dri

    As such I have added that command back into my go file.

    Yes, a shame they did all the work on the drivers and didn't fix permissions.


    Thanks for the process, that's where I arrived in the end too.

  7. 1 minute ago, BVD said:

    If you want to load it on boot every time and never use it in a vm, yeah. Otherwise I'd add it to a user script so you can decide when and where you want to use those resources.

    I just need it available in a docker, I don't have any VMs. But after running "modprobe i915" in shell and restarting the docker, still no joy.

  8. 1 minute ago, BVD said:

    That file just overwrites the blacklist, allowing you to use the driver either via hypervisor or docker/vm by loading the driver wherever its needed. To load it in unraid, it's just "modprobe i915", or you can add it to the file to run it automatically on boot.

    Thanks. Add it to the go file or i915.conf?

  9. 5 hours ago, BVD said:

    I put the command up further back, just head to earlier comments:

    Okay, so I ran the "touch /boot/config/modprobe.d/i915.conf", took the entries out of my go file and rebooted. Now I have no hardware encoders or decoders available in Emby. Was there something else I needed to do? Thanks for the assistance!

  10. 1 minute ago, John_M said:


    That will still work. There's now a better way of doing it that also works with other GPUs and also keeps your go file cleaner.


    Thanks. So what would the new way entail for me (apart from cleaning the go file)?

  11. Sorry, I don't really understand the GPU talk here. I've upgraded to 6.9.0 fine, no issues, but I still have this in my go file:


    modprobe i915
    chmod -R 777 /dev/dri


    Doesn't seem to be causing a problem. I put it there to get hardware transcoding with emby, which is probably working. Am I doing it wrong?

  12. 1 hour ago, ken-ji said:

    Odd. I've never seen any transcoding files - I'm transcoding to RAM vi a mounted directory under /tmp - unless I look while someones actively playing something. So I've never this issue.

    Me too. As soon as playback stops, the folder is empty.

  13. 4 hours ago, alturismo said:

    may a side question, why would you need a newer vlc ?

    as note, its the last option you should choose in terms of issues for remuxing ...

    vlc seems to be working fine but throws a lot of errors, e.g.

    2020-12-09 02:32:54 [xTeVe] Streaming Status:      Receive data from VLC
    2020-12-09 02:32:54 [xTeVe] VLC log:               [0000563efd486500] main interface error: no suitable interface module
    2020-12-09 02:32:54 [xTeVe] VLC log:               [0000563efd487c20] main interface error: no suitable interface module
    2020-12-09 02:32:54 [xTeVe] VLC log:               [0000563efd487c20] dummy interface: using the dummy interface module...
    2020-12-09 02:32:55 [xTeVe] Streaming Status:      Buffering data from VLC

    And why use? My ipTV service has recently changed something, and as a result it errors out when using the xTeVe buffer with Emby:

    2020-12-09 00:00:10 [xTeVe] Buffer: true [xteve]
    2020-12-09 00:00:10 [xTeVe] Buffer Size: 1024 KB
    2020-12-09 00:00:10 [xTeVe] Channel Name: 5USAB
    2020-12-09 00:00:10 [xTeVe] Client User-Agent:
    2020-12-09 00:00:10 [xTeVe] Streaming Status: Playlist: ipTV - Tuner: 1 / 3
    2020-12-09 00:00:10 [xTeVe] Streaming Type: [TS]
    2020-12-09 00:00:10 [xTeVe] Streaming URL: http://url.url.net:80/USER/PASS/4766
    2020-12-09 00:00:11 [xTeVe] Streaming Status: HTTP Response Status [200] OK
    2020-12-09 00:00:11 [xTeVe] Content Type:
    2020-12-09 00:00:11 [xTeVe] Content Type:
    2020-12-09 00:00:11 [xTeVe] [ERROR] Streaming error (Server sends an incompatible content-type) - EC: 4003

    vlc is the only thing that works for it. They say they only changed dns, but it's broken the service for Emby (all my other clients work fine, Emby is the only one using xteve).

  14. On 11/19/2020 at 11:20 PM, limetech said:

    If you feel like you have not been treated fairly, I apologize for that and suggest perhaps a different server solution would be better for you to be involved with.

    This is quite the statement for a "mea culpa" thread, comes across as "sorry, but if you don't like it, GTFO." I *assume* that's not what you meant... 🙄

    • Like 1
  15. I just grab the log from user scripts. As I say, it's not very helpful. You can also run the line in the console and grab the output. The problem will be SD returning crap data and causing g2g to fail, but unless they admit it we're stumped.


    Btw, you should change your grabber script to only overwrite your XML file if the new XML file is big enough. That way, even if it fails you'll have a week or so of data.