trurl

Moderators
  • Posts

    43882
  • Joined

  • Last visited

  • Days Won

    137

Posts posted by trurl

  1. 18 minutes ago, rmp5s said:

    I just noticed that the dashboard says "parity disk not present" even though I have the new 8TB assigned as a cache drive.

    Parity and cache have nothing to do with each other. The whole point of cache is it is not part of the parity array.

     

    Also, 8TB is an unusually large disk to assign as cache. Do you perhaps really intend to assign that disk as parity?

  2. 3 minutes ago, Sharpey212 said:

    I stated with 20GB and Fix Common Problems kept message says docker images getting full so kept adding 10GB to it. I need shrinking now because I have deleted a few dockers.

     

    If you were filling 20GB then you definitely had something misconfigured, regardless of how many dockers you were using. Did you figure out what the real problem was? Increasing the size doesn't do anything except make it take longer to fill up.

     

    See the "Docker Image Filling Up" section in the Docker FAQ:

     

    https://forums.unraid.net/topic/57181-real-docker-faq/

     

  3. 7 minutes ago, Squid said:

    install the auto update plugin and just have it update everything and not have to worry about it.

    This is what I do. If it weren't for these "reports" popping up all over the forum I wouldn't have even known about this.

  4. CIFS relates to SMB. Looks like login failures trying to access your network shares.

     

    Your docker.cfg is rather odd. You have a 2TB docker image at /mnt/user/docker.img

     

    That is by far the largest I have ever seen by orders of magnitude. Why are you doing this? It is extremely unlikely you will ever need more than 20G if you have your container applications configured correctly.

     

    And /mnt/user/docker.img is an odd path for it also. I can understand putting it on a specific disk, such as /mnt/cache/docker.img, but why would you put it at the root of the user shares? It's unclear to me where it would even exist in that case. Do you know what disk it's on?

  5. 2 hours ago, gacpac said:

    Hey, this wasn't happening before. 

     

    I noticed that after an update. My server stopped showing up in some computers. It's confusing, I can still access using my TV, my phone, outside my network. 

     

    The message I get is this.

     

    image.thumb.png.024b2e5a7eb4772c6438719afa1936cf.png

     

    Honestly, this doesn't make sense to me.

    Have you tried signing out of plex and signing in again? That usually works for me.

    • Like 1
  6. 2 minutes ago, ampm-it said:

    Can someone help me with the Facebox docker at all? Starting to lose my mind...

    No mater what I do, when i start it, the logs always say "[ERROR] MB_KEY: Invalid MB_KEY"

     

    S: any ideas would be appreciated.

    Maybe obvious, but since you don't say so, did you enter a key?

  7. If you mean the CRC errors those are usually a bad connection, cable, etc.

     

    If you want more advice, go to Tools - Diagnostics and attach the complete diagnostics zip file to your next post.

     

    You can acknowledge those CRC errors by clicking on them in the Dashboard page and they won't alert you again until they increase.

  8. 6 minutes ago, Moose_Flunky said:

    Help!

     

    I'm having trouble attaching to the Plex Media Server.  I've tried two different packages now, Binhex's version and now the version from Limetech.  The docker loads with no errors, but when I open the webui, I find the following message:

    image.thumb.png.bc9a7ff1ebc939446bfa18b839ae79e6.png

     

    My Unraid server (6.6.6) is running with a static IP on a vlan on my network.  The static IP is 10.0.30.200, and is part of Vlan 30.  All of my other dockers have installed and run perfectly.

     

    The managed switch is handling dns and dhcp duties for the various Vlans, and I can connect across vlans without issue. I have forwarded all of the ports that are listed in the docker cfg from my router to the Unraid server.

     

    I'm not certain where the error lies.  Does anyone have any ideas?

    Try logging out of Plex (dropdown in upper right corner of your screenshot) and login in again.

  9. 26 minutes ago, rmp5s said:

    That did the trick.  Thanks!

     

    Nope.  There is not checkbox, as can be seen in the screenshot above.  It was just a glitch.  Solved by a reboot.

    That screenshot is showing the Format button for an Unassigned Device. Totally different thing than formatting a drive assigned to a cache slot. Not what you needed to do but to format an Unassigned Device you must enable "destructive mode" in Settings for Unassigned Devices.

     

    What you needed to do was get Unraid to format the disk AFTER you assign it to a cache slot. The checkbox to enable format in that case is in Main - Array Operations.