lostsoulfly

You're not the only one, but most people probably don't limit docker memory on unraid. I didn't for years. But this started for me after upgrading to 6.12.0, 6.11.0 didn't have this issue for me.

Almost three days stable now, you're a Godsend my friend.

I've had so many issues on 6.11.x. edit: I admit, I skipped all of 6.10, so the issues may have started there. I can test that if necessary. I thought they were hardware problems at first. Ran memtest on each of my 4 modules, all passed. Bought a new NVME drive, since I was seeing some odd errors, rebuilt cache pool completely, still have issues. Moved one NVME drive to an external enclosure over USB-C, rebuilt btrfs since the drive "changed," still have issues. Rebuilt docker.img since it had a back block (or something?) that scrubbing couldn't fix. Still have issues. My unassigned USB 3.0 RAID0 drive that I access over SMB has had performance dropping to 0KB/s, and doesn't work at all now. SMB in general has been crashing and fails to mount on my Windows machine. Randomly, after a few hours (or even minutes at times), Unraid just crawls to a halt and the web interface is unresponsive. I'm reverting to 6.9.2 which is my oldest flash backup now, will report back if I have the same issues.sagiri-diagnostics-20221219-1447.zipsagiri-diagnostics-20221219-1935.zip edit2: Back on 6.9.2, no errors in my log unlike 6.11. SMB speeds for a mounted vhdx on my USB drive array are back to normal, 2.5Gbps+. Over two hours now, no errors in my log. This is a new record lately.. Something doesn't like my hardware on the newer versions.

After much pain, I figured out that 14.3.9 was the last version that gives me good speeds. None of the other versions are working properly and I see speeds go from 500KB/s to 9MB/s and fluctuate back and forth, many torrents stall or never start, etc. I've tried every qBittorrent container on the community store and they all have the same performance issues. Anyone have any ideas? I'd love to use the newer versions but they just don't work with unraid for some reason.

I have to reboot my container a few times per week because I wake up the next morning (after a nightly backup script had run to export my sql db) and be unable to login. "Disk I/O error" or "Unable to save device" in the Vaultwarden logs. I just disabled WAL but haven't tested its efficacy on the issue yet, but I'm hopeful. Does this happen to anyone else?

This is how I did it. I'm sticking with this image for a while, since it still works!

Thanks, I can confirm that this resolved it for me as well.. But this update caused me hours of headaches resolving. I will be more careful updating in the future. It wouldn't have been so bad if the container hadn't somehow lost its config multiple times and became orphaned or "stuck" in the unraid UI causing me to start/stop dockerd multiple times.