majbom

I have been using that for years and updated it the other day - then it all went south Anyway - I have deleted the WiredTigerLog files and I can start my VMs again. Thanks GOD I appreciate your fast and useful help!

I have these I've just found out that unifi.controller produces a lot of 100MB "WiredTigerLog" files every minute 😲

I just tried to delete some of the appdata - that was enough so I'm running QDirStat to see what's piling up. Thanks a lot so far! 🙏

Yeah, I was a bit to fast there. I have now set the cache settings as you described. That only free'd 45 MB. So when I try to install QDirStat, it fails. I have tried to make the docker image file 10GB instead of 20, but it makes no difference.

@trurl Can you see anything regarding my VMs? Unraid says "No Virtual Machines installed". Are they corrupt maybe?

Thanks a lot @trurl ! So my dockers are lost, is that correct understood?

Of course, thanks! tower-diagnostics-20211111-2015.zip

Hi. Apparently I have something installed or setup so my cache drive is filled to the limit; 0 bytes left 😞 Now I'm not able to start the Docker service and my VMs seems gone 😢 I have tried to move all shares away from the cache drive, but it doesn't help. I would've liked to run QDirStats (to help me solve what is going on and clean up), but as my Docker service is down, that's not possible. Where do I go from here? Please tell me what info you need to give a hint. Thanks

One last question: I found out that the unwritable directory (/config/cache/tmp/) had "root" assigned as both user and group. So I tried to uninstall the container, wiped the directory in appdata and installed the docker again. But it's still the same. Isn't that wrong? And is it in the container or the LMS the error exists? Thanks

Okay, I'll try that. Thanks

It looks like the rest of my dockers (except for the last part of course )

I may have found a problem; I have these [21-08-20 14:43:22.1482] main:: ([undef]) Warning: [14:43:22.1481] EV: error in callback (ignoring): Cannot write to '/config/logs/server.log': at /usr/share/squeezeboxserver/CPAN/Log/Log4perl/Appender/File.pm line 241. [21-08-20 14:43:22.1482] main:: ([undef]) Warning: (in cleanup) Cannot write to '/config/logs/server.log': at /usr/share/squeezeboxserver/CPAN/Log/Log4perl/Appender/File.pm line 241. [21-08-20 14:43:22.1488] main:: ([undef]) Error: Select task failed calling Slim::Networking::Async::HTTP::_http_read_body: Error in tempfile() using /config/cache/tmp/XXXXXXXXXX: Parent directory (/config/cache/tmp/) is not writable for every 8th millisecond 😬

Thanks for quick reply. It's this one:

Hey there Thanks for this great docker 👍 I've just noticed that my server.log is 165 GB (!). Isn't there som rotation on this file?

Done - thanks for the tip!

The Download share does use the cache. Actually I had it written in my post, but deleted it again, as I figured it couldn't be that I think I'll disable cache on Downloads then, as I don't want it to be filled with "video"-stuff, leading to other shares can't use it. Thanks for the clarification!

I've tried to re-install Krusader (including removing the folder from appdata), as I suspect it to be the problem. But the problem remains. The files shows up on the cache drive (/mnt/cache/video/) when I move files (with Krusader) from a share on /mnt/user/ (/mnt/user/Downloads/) to another share on /mnt/user/ (/mnt/user/video/) The "video" share has following settings: "Use cache" - "No" "Included disks" - "Disk 1, Disk 3" "Excluded disks" - "None" and there is over 1TB free space on Disk 1 + 3. What am I missing?

Nothing spectacular in the diagnostics?

tower-diagnostics-20191127-0810.zip Okay, it should be attached here

It's been a while, but the problem still exist. I've downloaded my diagnostics, how should I post it? A link to the zip-file, or do you only need one of the files in it? Thanks

I think I found the problem; Krusader was using "/mnt" instead of "/mnt/user".

Hi John Thanks for your reply. I don't have any dockers with a direct mapping to /mnt/cache/video. I've tried the solution you provided and will keep an eye on the cache drive.

Hi I got this message from Fix Common Problems: "Share video set to not use the cache, but files / folders exist on the cache drive". So I checked the settings which were correct ("use cache drive": no). I moved the files using unBALANCE, and finally removed the folder "video" from the cache-drive. But after I moved some files to my video-share, it uses the cache drive again. I have 2 4TB HDDs; one is completely full and the other has a lot of free space (> 2TB) - both of the drives are included for the video share. Why does unraid keep using the cache drive for this share? Thanks :-)

I crossed my fingers and did a hard reset. After that, I did "new config" and rebuild parity. Now it all works great. Thank you for your help guys.

Well, misfortunes rarely come singly. I have now tried to shutdown the array, to "change config", but it seems that a few docker-images hangs on shutdown I have tried to shutdown/reboot from dashboard, but nothing happens. Last I have tried shutdown from SSH, and now the webui refuses connection. The shares are still accessible, and I can still SSH into it. What to do?