Jump to content

Kudjo

Members
  • Posts

    27
  • Joined

  • Last visited

Posts posted by Kudjo

  1. I'm excited to give this a try.

     

    I've installed this and noticed a few issues:

    1) No WebUI comes up. So, I am unable to use it for now.

    2) There is no option on your current template that allows the user to select WHERE files will be saved/stored to. Reading through the docs yields very little on what path we should map to.

     

    What do you think? Would you like me to try something on my end?

     

  2. This may very well be what I've been looking for! (I was looking into salt just a little while ago)

    But, I am new to Terraform. Could you post instructions on the github? I'm excited to try it out on my unraid. (I was just trying to get some cloud images up and running in unraid's KVM with no luck. I'm sure I was missing something simple, because I think I've done it before) So, I'd love to give this a try!

  3. On 12/5/2020 at 6:45 AM, XisoP said:

    Hey all,

     

    I just upgraded my PMS image from very old to 1.21.latest. I now see a version not available in the docker overview. Is this common or is there something wrong in my config?

     

    224731635_versionNA.thumb.png.a8e8f907893225b89a92ea5d951ef3fc.png

     

    Similar to XisoP, but I'm not coming from old build. I'm currently running 1.21.1.3876 (which is current, at time of posting) and running "check for updates" doesn't change the "not available" message. I've also tried restarting the docker image; no luck. I'm just about out of ideas.

    Do any of you fine folks have a suggestion I can try?

  4. I'm helping someone with this too (a dirty shutdown made his two SSDs in his cache pool become unmountable).

     

    Did you ever figure out what to do about the "Error mkdiring" message? (JorgeB is correct, it is not creating the folders, but we're running the command as root with no luck.)

     

    Any ideas?

  5. 3 minutes ago, binhex said:

    damn you guys are quick!, my automated script only picked up the change 30 mins ago, there is a 1 hour delay as i have found the url is not updated quick enough sometimes on mojang website, so it should start building in the next hour from now.

    When you provide us with an excellent build, I turn around and serve it to a dozen others who are ITCHING to play on the new update. All I'm saying is this is kind of your fault for making this work so well. ;P

     

    I'll tell them to cool their jets and wait a few hours.

     

    Thanks again.

    • Like 1
  6. 42 minutes ago, Milldor said:

    The 1.16 update is out now on the server section of Mojangs website. Is there any way we can update the container ourselves or do you have to repackage it?

    +1

    If possible, I don't mind doing it on my own so you're not bothered. Thank you for building this! I've been using it for MONTHS with no problems at all.

  7. 15 hours ago, ich777 said:

    Have you deleted the directory in your appdata too?

     

    EDIT: I attached the full Altitude log after a fresh install.

    altitude.log 147.31 kB · 1 download

    I did remember to delete that directory after trying to reinstall it once or twice. When I finally remembered, I deleted the directory and tried again from scratch and got the log that I posted earlier. (I'll repost it from my most recent attempt from a minute ago). 

     

    Quote

    ---Checking for Altitude Server executable ---
    spawn /altitude/altitude.sh -c
    Unpacking JRE ...
    Starting Installer ...
    Error: missing `server' JVM at `/altitude/altitude.sh.8.dir/jre/lib/i386/server/libjvm.so'.
    Please install or use the JRE or JDK that contains these missing components.
    send: spawn id exp3 not open
    while executing
    "send "/altitude\n""
    -------------------------------------------------------------------
    ---Can't install Altitude Server. Putting server into sleep mode---
    -------------------------------------------------------------------

     

    I don't know if this helps, but I noticed that when it runs altitude.sh, it temporarily creates a directory called: "altitude.sh.xxx.dir" where xxx is equal to some number. I can see it start to unpack to the freshly created directory, but then it deletes that directory. So, all I'm left with is "appdata\altitude\altitude.sh"

     

    Yours installs properly after "Unpacking JRE ..."

     

    I'm on unraid 6.8 rc4. Did they make a change that I should be aware of?

     

    What should I do next? I'm happy to help.

  8. I removed (and deleted the image) of the Altitude docker and when I reinstalled, I keep getting this in the log:

     

    Quote

    ---Checking for Altitude Server executable ---
    ---Downloading and installing Altitude Server---
    spawn /altitude/altitude.sh -c
    Unpacking JRE ...
    Starting Installer ...
    Error: missing `server' JVM at `/altitude/altitude.sh.10.dir/jre/lib/i386/server/libjvm.so'.
    Please install or use the JRE or JDK that contains these missing components.
    send: spawn id exp3 not open
    while executing
    "send "/altitude\n""
    -------------------------------------------------------------------
    ---Can't install Altitude Server. Putting server into sleep mode---
    -------------------------------------------------------------------

     

    Does anyone have any ideas on what I should do about it? The only other thing that changed is I am now running unraid 6.8 rc4.

     

    Thanks again for all you do.

  9. Also, if anyone cares, you can use the game's included "server_configurator.exe" to make your own Server config file (called: "launcher_config.xml") which you can then load into the appdata location on ich777's Docker build. Just overwrite the one that's already there and all of YOUR settings are what the Docker loads on the next restart.

  10. ich777,

    Thank you so much for your great game server builds! I use several of them. Is it possible to get one working on unraid for Altitude (Free on Steam and off steam)? Pretty please?

     

    I got it up and running following their instructions but immediately thought of you and your excellent work on other games.

     

    Links:

    Altitude on Steam Link

    Altitude developer page for linux server files and instructions

     

    What do you think?

     

    Again, THANK YOU for you superb efforts!

  11. On 4/3/2019 at 7:04 PM, aptalca said:

    You're confusing different tags.

     

    ...

     

    I hope that's clear.

     

    If you simply want to use version 1.15.1.791-8bec0f76c, the easiest way would be to set the "VERSION" variable to "docker" so it doesn't do any updates during container start, and use the image "linuxserver/plex:1.15.1.791-8bec0f76c-ls11" so you'll use the image that comes with that version with no in container updates

    I hadn't understood the difference. Thank you for clearly explaining how all that works.

     

    That new knowledge, mixed with your instructions got me up and running as desired. Thank you very much!!!

  12. 9 hours ago, aptalca said:

    First of all, the additional variable is only needed if you're trying to go back to 1.14, not 1.15. Second, you're missing some digits in the version you are entering. It needs to be longer than that.

    Third, the "latest" you're seeing in that screenshot is for the docker image, not the version of Plex inside the image

    This was highly informative. Thank you. Okay, I'll go in order.

    1) I didn't know that was specific for 1.14, thank you for telling me that. I don't remember seeing that requirement, so I'm glad I know now. Are there any other times when that variable should be applied?

    2) You're absolutely correct, I'm missing the rest of the tag in that screenshot (I pinky promise I've used the correct tag before). Unfortunately, the tag: "1.15.1.791-8bec0f76c-ls11" still doesn't do the trick for me. Plex is still reporting that it's on version 1.15.2.793. :( I'm getting my tags from: https://hub.docker.com/r/linuxserver/plex/tags if there's somewhere else I should be looking up the tags then maybe that's my problem; incorrect tag names.

    3) I'm basing my experience off of the official Plex Inc Docker container. It reported the Tag number I had selected as the version, so I assumed it worked the same for the LinuxServer Container. So, thank you for teaching me that doesn't seem to be the case for this one. 

     

    Any ideas of what to try now?

    plex version problem 3.PNG

  13. On 3/28/2019 at 6:58 AM, aptalca said:

    Along with the version for 1.14blah, pass an environment variable where PLEX_DOWNLOAD="https://downloads.plex.tv/plex-media-server"

    2087480686_plexversionproblem.thumb.PNG.2efa227e5b943a9b2a9139e6bd4d23ca.PNG

     

    No change...

     

    749512846_plexversionproblem2.PNG.d52e9e71c6e925ff059310050f294746.PNG

     

    I added the variable, as you suggested. But I must be missing something. No matter what I try, the "version" still reports as "latest" and the Plex container still says I'm running 1.15.2.793.

     

    Could someone please point out what I'm missing/doing wrong? I'd love to have this control again.

     

    Thanks.

  14. On 3/26/2019 at 8:09 AM, Wavey said:

    Hey I updated to 1.15.2.793 and now Im trying to roll back to 1.14.1.5488 due to the server hanging once a day. I put 1.14.1.5488-cc260c476-ls9 in the version field but it doesnt roll back. Even tried just 1.14.1.5488 and the server still says 1.15.2.793. Im running Unraid Version: 6.6.7. This always worked in the past, anything change that Im unaware of?

    I am having this EXACT same problem.

    Trying to rollback because I sometimes can't leave the Plex home screen. (I can still play everything if I click it directly and search still works, but plex will never leave the home screen). The TAG/Version method has worked before, but it won't roll back this time. I'm also running Unraid Version 6.6.7. The official Plex docker rolls back like normal using the same TAG method, so I wonder if there might be a hangup with this build in particular?

     

    Does anyone have any suggestions?

  15. Good news: adding "append vfio_iommu_type1.allow_unsafe_interrupts=1 initrd=/bzroot" to the syslinux.cfg file worked for getting the VM to boot with the card!

     

    Another snag, though. I get the following message whenever I run the unbind/bind command: "-bash: echo: write error: No such device". The BIOS dump only produces a 126KB file, so I don't think it's happening properly.

     

    So, two questions:

    1) remind me what we need the bios file for again if we can get the card to boot using the UnRaid GUI? (I'm sure we DO, I'm just unclear what the difference/advantage is between bios dumped and added to XML vs not)

    2) Is there a way to verify the validity of my bios dump other than filesize? (And if filesize is the only way to check, how do I know I have the right filesize)

     

    Almost there! I'm so grateful for your great videos that help me get the most out of unraid. I feel I'm close, I just want to understand what's going on. (Teach me to "fish")

     

    Thank you, again!

  16. I was hoping for some help. I have tried this with 5 video cards on two different systems (and three different versions of unraid) and have gotten the same result each time so it has to be something I'm missing.

     

    Whenever I go to start a VM with a GPU assigned as the passthrough, I am met with the following:

     

    Execution error

     

    internal error: process exited while connecting to monitor: 2017-02-24T16:31:08.340691Z qemu-system-x86_64: -device vfio-pci,host=02:00.0,id=hostdev0,bus=pci.0,addr=0x5: vfio: failed to set iommu for container: Operation not permitted
    2017-02-24T16:31:08.340724Z qemu-system-x86_64: -device vfio-pci,host=02:00.0,id=hostdev0,bus=pci.0,addr=0x5: vfio: failed to setup container for group 11
    2017-02-24T16:31:08.340729Z qemu-system-x86_64: -device vfio-pci,host=02:00.0,id=hostdev0,bus=pci.0,addr=0x5: vfio: failed to get group 11
    2017-02-24T16:31:08.340744Z qemu-system-x86_64: -device vfio-pci,host=02:00.0,id=hostdev0,bus=pci.0,addr=0x5: Device initialization failed

     

    No amount of googling or searching on unraid forums has explained why this might be happening or how I might fix it. Any ideas?

     

    vt-x and vt-d enabled in BIOS, UNRAID 6.3.2, using OVMF and "i440fx-2.7", Windows 10 VM, currently trying to passthrough an Nvidia 1070 Founder's Edition and also have an EVGA GTX 1060 SC 3GB (and several other older cards, 550ti, 8600, etc.), GPU is all alone in IOMMU group 11, Enable PCIe ACS Override set to "No"

×
×
  • Create New...