soabwahott
Members
-
Joined
-
Last visited
-
@JorgeB I cleared out /boot/extra and the issue went away. 6.11.5 now works. I heard that openssl can cause problems, this is one of the packages I was using so that might be the culprit.
-
@Snickersdid you resolve this with v 6.11.5? I have the same issue with my key, I went back to v6.11.0 I may have to try the safe mode option and see if it's a a plug-in breaking things
-
I also run 'netdata' and saw similar behaviour, either my 'netdata' docker would stop collecting data or crash completely. The RAM stats posted above are similar to what my own were. I thought I didn't have a problem because I had a fair chunk of memory shown as buff/cache. However, I think because unraid runs in the ramdisk this isn't a true reflection of what's going on compared to a conventional Linux OS.
-
As per others in this thread my issue turned out to be related to filling up the RAM on my server. I use Borg for backups and was running Ubuntu Server previously. Borg by default creates cache files in the home directory. On ubuntu server this was fine because they sat on my main SSD, whereas on Unraid the home directory is created on the ramdisk. Once I told Borg to put the cache files on my array the problem went away and I've had no issues since. If anyone else sees similar behaviour with high reads on loop2 please check your ram usage, if this is showing as very high when the issue occurs it is likely that something is filling it up, e.g. plex transcoding or something else writing to /tmp/ or running outside of docker/vms.
-
-
This started when I upgraded to 6.9
-
I'm seeing the same behaviour, docker loop device is showing a very high amount of reads. System load climbs to ridiculous amount, CPU usage shows as 100%, server becomes unresponsive/sluggish/things start crashing/misbehaving. I've moved 'docker.img' to a separate SSD from 'app_data', but that hasn't helped. Does anyone have a resolution?
