Jump to content
  • Docker path works when pointed to /mnt/cache/minecraft but not /mnt/user/minecraft


    Seltonu
    • Minor

    When setting up a minecraft server through TQ's docker (highest download count under "minecraft" in CA), when the data path is set to /mnt/user/minecraft/ the minecraft server is unusably slow and crashes 60 seconds after a user tries to break a block (server tick timeout). Server works perfectly when this value is changed to /mnt/cache/minecraft/. Completely reproducible for me after remove/reinstall, and reboot. Expected behavior is that either path value should work.

     

    The share "minecraft" is an empty share set to Cache Only. Also reproducible even after deleting and recreating the share.

     

    Hopefully someone else can try to reproduce this, I won't be able to test much starting tomorrow as users will be on the server. Please let me know if there's any information to add, I'm brand new to unraid!




    User Feedback

    Recommended Comments

    You need to include your diagnostics for this.  

     

    There's a few containers out there that seem to have issues when their data files / appdata is set to /mnt/user/... but work perfectly with /mnt/cache/...,  

    Link to comment
    4 hours ago, Squid said:

    You need to include your diagnostics for this.  

     

    There's a few containers out there that seem to have issues when their data files / appdata is set to /mnt/user/... but work perfectly with /mnt/user/...,  

    Should the second /mnt/user/... actually be /mnt/cache/... ?   Does not seem to make sense otherwise :) 

    • Thanks 1
    Link to comment

    Oddly enough... today I can't reproduce this bug even with a reboot. The only thing I can think is that the mover had the chance to run again (though it was run yesterday after installing the cache drive), so maybe it was related to some files not getting properly migrated? But like I said the share was even deleted/recreated with Cache Only...

     

    I'm unsure if I should close this bug, I'll attach system diagnostic just in case. Apologies for not having a diagnostic from while the bug was occurring, I don't know if this will be helpful

    vault-diagnostics-20211219-1605.zip

    Link to comment


    Join the conversation

    You can post now and register later. If you have an account, sign in now to post with your account.
    Note: Your post will require moderator approval before it will be visible.

    Guest
    Add a comment...

    ×   Pasted as rich text.   Restore formatting

      Only 75 emoji are allowed.

    ×   Your link has been automatically embedded.   Display as a link instead

    ×   Your previous content has been restored.   Clear editor

    ×   You cannot paste images directly. Upload or insert images from URL.


  • Status Definitions

     

    Open = Under consideration.

     

    Solved = The issue has been resolved.

     

    Solved version = The issue has been resolved in the indicated release version.

     

    Closed = Feedback or opinion better posted on our forum for discussion. Also for reports we cannot reproduce or need more information. In this case just add a comment and we will review it again.

     

    Retest = Please retest in latest release.


    Priority Definitions

     

    Minor = Something not working correctly.

     

    Urgent = Server crash, data loss, or other showstopper.

     

    Annoyance = Doesn't affect functionality but should be fixed.

     

    Other = Announcement or other non-issue.

×
×
  • Create New...