Irithor

A scrub won't return anything specifically in regards to Docker Image corruption. Just overall corruption I believe. I just ended up re-creating the Docker Image and downloading all the images from scratch. I also believe the culprit may be that the Plex Meta Manager container was creating a memory leak due to trying to restart itself in extremely quick succession without just stopping because of a bad update that was pushed that needed to disable part of it's start up process but didn't account for this looping issue. Between those two things the issue seems to have resolved itself for now.

Thanks for taking a look! I thought 96gb for the Docker Image was very large also. I have since decided to just go ahead and recreate the image and re-download my containers. This has allowed me to at least have the service up and running with no containers and a clean image, so that's progress. I am now in the process of turning them back on one by one. It having one or some of them auto-start with the array causes this issue and doesn't resolve until a full reboot. I know the Docker Image can fill up when paths are incorrectly configured but I feel I have pretty meticulously checked and re-checked they are all correct. I've attached a report of the Container Sizes. I'm not sure if they will mean anything to you as you might not be familiar with them but appreciate letting me know if anything looks off to you. Container Sizes.txt

I'm getting huge CPU usage from the docker service causing my system/webgui to lock up. It started right in the middle of normal operation (was renaming some files in Sonarr I think). I cannot attribute it to any specific container as the problem persists even with all containers off. I've tried turning them on/off one at a time but no obvious culprit. If I disable the Docker service entirely though, it seems to go away. The only other change I have made recently is increasing the size of the docker image from 64gb to 96gb. Top is showing Dockerd using around 600%. A couple of orphaned docker images were created around this time but not exactly sure when. I am also noticing irregularly high reads in my cache pool (the one with my appdata and docker img). Is this corruption? Thanks in advance. unraidserver-diagnostics-20230511-0654.zip

Hmm, seems after running consecutive scripts that nothing is being stored in RAM which I suspect means that it's not working for me? Spinning down all disks and then attempting to play still incurs buffering. Is this error in the logs still to be disrgarded?: tr: write error: Broken pipe tr: write error cut: write error: Broken pipe

Trying to get it running now, any chance you'd care to elaborate on the process? Thanks in advance!

If I were to leave the container running 24/7 instead then theoretically yes, but where as booting to GUI only shows about 13-14w consumption on a GTX1650 Super, substituting the container hovers around 20W due to which I assume is an increased workload over simply running the Unraid UI. No boot to GUI and no container hovers around 28w.

Ahh. Initially thought to myself "Can't be that, I definately don't have any containers or VM's using the GPU at all other than the occasional Plex transcode." until it dawned on me i've been booting into GUI mode since watching a Spaceinvader One vid on doing that to force GPU's to idle for lower power consumption over time. For anybody getting the same error as myself and @kl0wn, go to your 'Main' tab and click on your flash under 'Boot Device' and change the boot from 'Unraid OS GUI Mode' back to 'Unraid OS' as this will in effect count as a 'screen'. A shame to lose that power/performance ratio though. If anything can be done to allow multiple screens that would be awesome but as I understand it is a limitation of the operating system. Thanks again, going to have a play now!

Hmm, throwing some errors for me. Any suggestions? Cheers for the work/in advance. steam-headless-2022-01-10T15-46-13.log

Hey @ElectricBrainUK, Cheers for the awesome work, got everything up and running both as a container in Unraid first but then switched to hosting inside Home Assistant with the addon as it seems a bit more reliable. I am having one issue. At this stage, the connection does not seem to persist across server/VM shutdowns, leading to having to sign in (of which it prompts twice?) every time the home assistant server has to reboot. Any way to avoid this? Thanks again!