smashingtool

1) Yes, check out https://hub.docker.com/r/linuxserver/mcmyadmin2/ 2) Yep 3) Not as a docker, but a Windows VM would work fine for this. Check out https://lime-technology.com/gaming-on-a-nas-you-better-believe-it/ and 4) I'm not sure on this, maybe someone else can tell you. FYI, the trial version may be enough for you to figure that out. Edit: Based on the networks settings screen, this looks doable. Make sure to to install Community Applications first thing. It makes installing dockers and plugins much easier! I recommend LinuxServer.io's docker containers. http://tools.linuxserver.io/dockers

Restart the plex container

https://lime-technology.com/forum/index.php?topic=41562.0 It's easy to do. I suggest you install the docker and look at how it names the config folder and whatnot, and then move your current config on top of it, remove the docker, and reinstall the docker.

Is it unusual to use the cache drive as a spot to hold all the config for dockers/plugins? And the Docker image? Because that's what I do. I don't even use the other aspect of it I don't think.

Only the update notifications(Plugins and Dockers) are broken for me. All of the rest work fine.

Is there any way to know when the software in a docker (The image?) has an update available? The Docker page only checks for container updates, but that isn't the same thing. I'll sometimes open a container like Plex to have it tell me in the Plex WebUI that an update is available, which i get by restarting the container. Some sort of external notification or autoupdate would be nice. I know that is probably unfeasible, but if it is doable, I'd at least like to voice my desire for it. Thanks!

Awesome! This has been bothering me lately(i've noticed it since 6.1.7). I don't suppose it supports dockers too?

hi smashingtool, Do you see anything out of the ordinary in either unraid's or unbalance's logs ? The heart of the operation is an rsync command, any error it might come up with should be written to the log. But rsync can also slow down/pause with a failing disk. Let me know if you find any other evidence of what might have happened. I dont see any evidence of a failing disk. Otherwise, here's the main error i found in unBALANCE's logs: I: 2016/02/10 07:50:52 core.go:651: diskmv finished I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1) I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0] I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1) I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0] I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1) I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0] I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1) I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0] I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1) I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0] I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1) I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0] I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1) I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0] I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1) I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0] I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1) I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0] I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1) I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0] I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1) I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0] I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1) I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0] I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1) I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0] I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1) I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0] I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1) I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0] I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1) I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0] I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1) I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0] I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1) I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0] I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1) I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0] I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1) I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0] I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1) I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0] I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1) I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0] I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1) I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0] I: 2016/02/10 07:50:52 core.go:651: Cannot stat file /proc/32071/fd/70: No such file or directory I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1) I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0] I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1) I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0] I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1) I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0] I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1) I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0] I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1) I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0] I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1) I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0] I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1) I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0] I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1) I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0] I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1) I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0] I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1) I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0] I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1) I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0] I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1) I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0] I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1) I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0] I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1) I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0] I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1) I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0] I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1) I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0] I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1) I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0] I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1) I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0] I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1) I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0] I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1) I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0] I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1) I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0] I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1) I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0] I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1) I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0] I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1) I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0] I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1) I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0] I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1) I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0] I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1) I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0]

If you turn on Plugin update notifications then you already get notified..... The feature is currently broken for me. They refresh/search, but I never get notified. Lots of other people reported the same thing in the 6.1.7 thread

Thanks, It's great that you made that, I'll give it a shot. My only other question now is whether it's possible to pause or stop unBALANCE after you start it.

I tried to use this to empty a disk so I could format it. It should have finished overnight, but didn't. It stopped at 120 gigs. So this morning I set it to run again, and it stopped at 116 gigs, but ~120 gigs disappeared from my array. I checked my disk shares, and sure enough, the drive that was supposed to be emptied had copies of files that were also on other disks. So now I'm paranoid that I have a bunch of copies of files on various disks. Is that something that the built in unraid mover would ultimately fix? Or am I doomed to have to compare files over my 4 disks for a while?

That's what it says in the beginning of this very post.... I do wish we had some sort of actual roadmap available though, with an outline of the intended changes and additions. I know forecasting that stuff is never perfect, but some official indications of the trajectory of unRaid would be nice.

Just wait till you experience Docker. It's made unRaid a whole new OS I waited till the release candidates were available for 6.0 to update, and after updating, I was kicking myself for waiting so long.

Do the Plugins/Docker updates notifications not work for anyone else? They seem to actually run the check 4 times a day like i set it to, but I never get notified. When I randomly visit my plugins page, it now shows the updates without me pressing the check button. Testing the notification with Pushbullet definitely works, and when I enable other notifications, those definitely come through as well. I have the checkboxes for agent checked for the update notifications, and still nothing gets to me.

Probably by editing the config.ini file

Once I added the ports it started working consistently. Before, it would randomly sync(using the relay servers, most likely!), but it never maintained a constant connection to other devices, and i went a few hours where nothing worked. Avoiding the relay servers is better anyway. Higher speeds, more direct of a connection. According to the documentation anyway.

Syncthing is set to listen at tcp://0.0.0.0:22000, both officially and in the config present for this docker. But the container template is not set to forward that. I installed Syncthing yesterday and it was great, but this morning it has had connection issues. I noticed this at that time, and was wondering if it should be a part of the template? There may be a great reason why it's not included, but I figured I would bring it up. Edit: The documentation says to also listen to 21027 with UDP, fwiw.

This fixed the excessive usage in my case: http://lime-technology.com/forum/index.php?topic=45249.0 The official Limetech Sync docker had a log file 7GB in size after a day

Did it leave out only the Annuals? Or just random issues?

Okay, so let's say you have a folder of issues for Saga. Open Mylar, and search for Saga in the top search bar. It should pull up lots of results. Go to page 2 and add the Saga with 32 issues. At this point, it should add the comic and scan your current comic folder and notice that you have issues of it.

Thank you. Due to that, I found out that the official Limetech BTSync docker was the culprit for me. It had created a 7GB log file since last night!

Yep, just read through a few threads and found myself here. Turns out my LimeTech BTSync container has a 7.3GB log file! I reinstalled it last night and my docker utilization has crept up all day

It wasn't my thing either until a friend of mine basically forced me to read one. If a Hunter S Thompson type character in a dystopian futuristic society dealing with politics and journalism and a corrupt government sounds interesting, definitely Transmetropolitan. That's what my friend had me read, and I was hooked within a few issues. It starts out slightly slow, but by the end of the third one, I liked it a lot. 60 total. Y - The Last Man is great. Basically, in the first issue (of 60 total), every male mammal on the planet dies except for 2, a guy and his pet monkey. Watching how society reacts to such a thing is explored while the main characters try to figure out what happened and why. Fables is a comic about a bunch of fairy tale and fable characters who had to flee their homelands and move to New York. 150 total. We3 is a short 3 issue comic about 3 prototype animal weapons who escape a test lab and try to survive. Emotional story with basically no spoken words. Saga is like a Star Wars and Romeo and Juliet-ish story mashed together. Unlike the above two, this is an ongoing story. Maus is the famous graphic novel that depicts living in Nazi Germany, but mice are the characters. I believe it is required reading in quite a few college courses these days.

There's lots of great non superhero comics/graphic novels for adults. Let me know if you want some recommendations or options

Another option is to search for the comics themselves and add them manually. Then it will scan the comics and see that you have them. Obviously this is painful if you have a ton of comics.