-
Posts
43882 -
Joined
-
Last visited
-
Days Won
137
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by trurl
-
-
You will have to use a different Flash.
-
That GUID doesn't look like it is unique. Are all of them like that?
-
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/
-
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.
-
3 hours ago, scubieman said:
Thank you! Sorry about wrong thread.
For future reference, you can always get to the right thread by clicking on the docker icon in the webUI and selecting Support, or from the Support page link for the docker in Apps (Community Applications).
- 1
-
If you don't know why you have it and it is giving you trouble then get rid of it.
-
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?
-
Syslog itself isn't to blame. Have you got atop installed? At the terminal, what do you get with this?
du /var/log
-
Also, the loop devices are vdisks, such as your docker image. Though these are contained on a disk, it is possible to corrupt them without actually having a disk problem.
Any particular reason you have allocated 40G to your docker image? You should never need more than 20.
-
-
Not clear from your description. Is that the output you had when it crashed? The point of tailing the syslog is to get the last thing that happens.
-
1 minute ago, scubieman said:
If i choose for it to run daily. What time does it run?
The built-in schedules can be seen and adjusted at Settings - Scheduler - Fixed Schedules
- 2
-
Go to Tools - Diagnostics and attach the complete diagnostics zip file to your next post.
-
Go to Tools - Diagnostics and attach the complete diagnostics zip file to your next post.
-
2 hours ago, gacpac said:
Have you tried signing out of plex and signing in again? That usually works for me.
- 1
-
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?
-
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.
-
4 hours ago, cimmy01 said:
I’ve tried every container in the CA plugin.
On 1/15/2019 at 9:50 AM, trurl said:The plexinc container isn't supported by anyone on the Unraid forum.
You might try starting over with either linuxserver or binhex container and see if there will be help on one of those support threads.
-
44 minutes ago, Fidelix said:
Never buying Seagate again.
The super slow one was a WD. And most were very old.
-
You asked that this thread be deleted, but others have replied and I am reluctant to delete their posts.
If you found a solution, please share it with the rest of the community. It might help someone else.
-
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:
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.
-
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.
-
55 minutes ago, chris1259 said:
I didn't want to assume that everyone had "user" in their path.
All user shares are mounted in /mnt/user. Simple as that.
-
What do you have for DNS?
Brand new, precleared drive: "Unmountable: No file system"
in General Support
Posted
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?