LyhjeHylje

That was the problem, thank you. The default value was almost, but not quite right for me so I guess I overlooked that 😓

I just tried Transmission_VPN and I have strange problem. If I leave "network type" as "bridge" I cannot connect to webui but sonarr finds transmission. If I change network to custom "br0" (which I guess I created according to some guide, I cannot remember why) then I can connect transmission UI via it's own local ip address but then sonarr cannot find it (with the same address). How I should set my network so that sonarr can use transmission and I can see what it is doing?

Novnc works for tens of seconds and then disconnects, reloading browser tab restores connection for another while. Started sometime (but not immediately) after upgrading to 6.8.2. Does not affect docker containers with ui. Restarting VM does not help. I was able to make it work for a few days straight by restarting unraid and clearing browsing data, I don't know which one (or both) actions did the trick. I have tried firefox and brave (=chromium). Yesterday I created a new VM from scratch and today it too started disconnecting itself. Both VM's (pre- and past- 6.8.2) are linux mint machines and almost stock (no crazy configurations) I can of course boot my machine again and clear browsing data again but I'd rather not do that for every few days. Otherwise unraid has been solid but I'd like to solve this.. Update: after just letting it be by itself for awhile the situation seems to be improved and novnc is not disconnecting (at the moment). Puzzling

Seems plausible, I'll check my cables and keep an eye on it. Thank you for help.

Too bad I noticed your message only after rebooting. Hope there is some clue to be found tessu-diagnostics-20190214-1941.zip

Unraid log shows: Are my hard-drives failing? What are loop devices? Reboot seems to clear problems but I have no idea what is going on and how to fix it.

Today I got this error: And if I stop any container and try to start it again: I have no idea what is going on. I do not think today's errors are caused by mover since it has not been run.

Thanks for the help. The vm disk has 20G allocation and I have some 370G free space on cache. One thing I forgot to mention is that I have mounted non-cache share inside the vm. It is probably this connection that gets broken by mover. I usually have to boot the vm several times before it starts properly. The containers that I have seen affected by mover (krusader, duplicati, plex) also have access to non-cache shares. But it seems that they do not break every time.

Sometimes after scheduled mover activity my vm (linux mint) starts to complain that disk is read-only and I need to restart unraid and the vm in order to sort things out. My docker containers also tend to break at the same time. Some of them (duplicati) complain not being able to write to disk. I have set appdata and domains as "cache: prefer". Should I change that to "only"?