Neural42

Did the issue return just by disabling Syncthing and rebooting? I'm checking because that didn't solve the issue for me. Only deleting Syncthing and my Docker vDisk and then not reinstalling Syncthing solved it.

I'm not sure if this is in the thread or not, but here's a tip. If you are using Krusader to move files to/from a cache drive to your array, map the /media container path to something like: /mnt/user0 The user0 is the important part. That will force it to actually move files, for example, from the cache to the array when you move them.

No worries! I'm hoping some issue is figured out with this. I want to add that my setup is with a UGREEN NAS DXP 6800 Pro, which has a 12th gen i5 processor so it's not likely an AMD-specific issue.

I wonder if it's related to this issue? No Syncthing in that thread, but a similar issue of SHFS consuming more and more RAM given certain circumstances. Maybe it's a side effect of how both Syncthing and Unraid manage file I/O and memory allocation under heavy load.

I'm glad I'm not the only one seeing this. What you wrote is exactly what happened on my server. That means it is most likely some odd issue with Syncthing and unRAID when upgrading to 7.

I wiped all network settings, wiped all Docker containers, downgraded from 7.0, etc. and nothing worked. Even reserving a new IP address and resetting everything possible with the router and the server didn't work. What appear to have solved this (hopefully) was reinstalling unRAID and starting from scratch. Thankfully it was easy to assign the drives back and rebuild parity. Getting all containers set up is still a work in progress. Who knows if it will keep working, but it appears to be for now.

I just checked and I can access it through its Tailscale address. That's something, but it's baffling why overnight it stopped allowing a local connection. Edit: It's back to not working except through Tailscale. I'm working on figuring this out, but it's still not working. Edit #2: It worked for some hours but is back to not working. Nothing has changed with my router. I've verified IP addresses, restarted the router multiple times, restarted the unRAID box multiple times and I can only access through Tailscale.

I got up this morning and tried to log into unRAID through my normal method: http://192.168.XX.XXX and the GUI is completely inaccessible. Everything was fine yesterday and now I have no access. I shut it down, connected a keyboard and monitor and was able to boot into the device, including pulling up the GUI on it directly but any access on any other computer in my home network is not not possible. I've checked my router settings and nothing changed there. Any thoughts about what's going on? Edit: Diagnostic files removed. The issue was clearly gremlins. Internal IP addressed changed overnight, although nothing changed on the device and there was an existing unexpired DHCP reservation for it.

I'm not sure what caused the issue but I'm still going with Syncthing as the most likely culprit. I deleted my Docker vDisk, upgraded to 7.0 and am just using my most needed containers (Jellyfin and Plex) before adding more. Right now I'm sitting at 2.66 GiB of system RAM usage, which is way less than before where system was in the 25 GiB range. I'm going to mark this as solved for now. Edit: I checked in the morning and am at 2.68 GiB of system RAM used, which is excellent. 2nd Edit: Still at only 3.19 GiB of system RAM with more containers running and an rsync of millions of files running. I'm almost certain now the problem was due to a Syncthing issue. 3rd edit: Now it's sitting at 1.5 GiB of system RAM used after more days. Syncthing has not been reinstalled and there have not been any RAM issues.

Thank you for the response about the other issues. I'm working on fixing the appdata, domains, and system issues. The files are moved now. Thanks for the reminder about my docker.img size! I was using a neuroscience research-specific docker image that was large and really needed the high I/O of the store pool so I needed a large vDisk, but I've stopped using that on this machine and have now reverted my vDisk size to the default. As for a fresh install, I meant more in the sense of starting from scratch with 7.0 and not import any configurations other than making sure to set up the array as it currently is. Then I'd install containers one by one to see what happens. I have a hunch that it might be related to Syncthing, but that could be an incorrect hunch. I started using that recently and maybe it's related to having to copy tens of millions of files (these are some of my neuroscience data) to another device. Syncthing uses its own RAM, but maybe because of the number of files, shfs is also spiking up in usage??? Syncthing is the only other recent change other than the OS upgrade. Thank you again for your help so far! I appreciate it.

Just for kicks, I downgraded back to 6.12.14. I'm still getting high RAM utilization from shfs (currently 54.3% of my 40 GB). This didn't happen before the upgrade to 7.0.0, so something weird is happening. I'm hoping I don't have to do a fresh install but that might be what's needed. root 11030 111 54.3 22537388 22176676 ? Ssl Jan20 809:34 /usr/local/bin/shfs /mnt/user -disks 63 -o default_permissions,allow_other,noatime -o remember=0

Edit: Removed diagnostics as they ended up not being important for this particular issue.

I upgraded to 7.0.0 last week. It was quick and painless. However, I've noticed high RAM usage since then. Specifically it looks like shfs is eating up a lot -- almost 50% of my RAM (40 GB total in the system). It never used anything like that before the upgrade. root 10093 107 48.8 20396412 19922852 ? Ssl 06:39 119:10 /usr/libexec/unraid/shfs /mnt/user -disks 63 -o default_permissions,allow_other,noatime -o remember=0 Anyone seen this before and have ideas about how to fix it? My system becomes unresponsive over time (which seems like a memory leak), requiring a hard reboot.