Naticus

This is probably because your buffer directory has millions of files in it. I have so many right now that it won't even list the files so I'm purging the directory beyond 14 days of modified time and then will restart the container. Obviously double-check this and fix the path before just blindly running. There were issues reported on the git repo back in October that have since been closed out and Josh5 has added a buffer retention setting. From what others had said, unmanic was maybe making files every few seconds for months. find /mnt/user/appdata/unmanic/.unmanic/logs/buffer -type f -mtime +14 -exec rm {} \; Edit: lol so I'm waiting for this to complete the removal and I realized I had done an ls -l in the logs directory before I started. I have 170 MILLION hardlinks on the buffer directory. Yeah, this would explain why it took like 45 min to start unmanic and have a working webui.

Yep, can confirm this is just a workaround. Luckily @bonienl has a script proposed for 7.1.3 that will force re-create the network from my understanding. The issue for me seems completely related to whether a docker container using br0 is started automatically or not, because it seems to have interfered with the creation of shim-br0. br0 is created fine, but shim-br0 is not.

First, thanks for all the work you're doing on this! I thought it was just my install of NerdPack that was broken until I found this package. Second, one tool I am really missing from NerdPack is ctop, found here: https://github.com/bcicen/ctop Thanks again!

That's a relief that it's on Unraid's side! I've only been running Unraid for 2 days now and found My Servers and thought I broke something until I found this thread. I'll be patient and hopefully it'll all be good soon.