ryanakata

I made a thread yesterday and am having the same issue and just found where the GPU is gone in the logs. Either my GPU died or something in the update went wonky. Commenting to follow.

Only plex. Other containers and seem fine but I’ll double check on the next crash. I almost feel like it only crashes when trying to stream media but have not verified that yet.

Last night my Plex docker began crashing, but I could restart the docker and it would come right back up. I'd resume watching our show and then it would hang with the docker crashed again. I updated from 7.2.2 to 7.2.4 after a few crashes just to make better use of a reboot, same issue persists. I've looked through the docker logs and do not see any indications of something in the Plex docker crashing itself and am hoping maybe there is something else in these logs that stands out? ryanflix-diagnostics-20260430-0636.zip

UUID: b9cb5a6f-abae-436e-863a-18c9dfed7085 Scrub started: Mon Nov 3 06:40:38 2025 Status: finished Duration: 0:04:54 Total to scrub: 403.88GiB Rate: 1.37GiB/s Error summary: csum=82 Corrected: 0 Uncorrectable: 82 Unverified: 0

Gave it a shot since 7.2 released and I hadn't tried since 7.0 and 7.1. Still getting the same crashes. If I rever to 6.12.15 the server can run perfectly fine forever. Diagnostics attached, please help. ryanflix-diagnostics-20251101-2133.zip

Server is fairly untouched for a year or more, out of nowhere the docker.img fills up. I change it from an image to a folder and a day later that folder is 100% filled on my cache drives. Trying to trace down the issue on what it may be. Looks like whatever /dev/loop2 is on the binhex-deluge container is taking up almost 500G in a day. How can I narrow down it's for sure that container and work on reclaiming space?

Any luck? I know there's a spot in the settings for the docker img location. Just wondering if that's mapped directly to /cache/ even if the share is set to the disks? I know when replacing drives the mover does not move the .img file even with docker disabled so I feel like something has to be set to the old /cache/ location. New USB wouldn't be hard to test just to see if it helps, if your new docker img is on the array then it should pick up everything and just start if the disks are in the right order.

You don't have to move anything, it's super easy to do, however, what is still trying to write to cache? You may need to check your docker and vm settings if it's trying to find the docker.img that may have been there. But in Unraid settings, just go hit new config and add drives without the cache there.

I see people having docker issues, for what it is worth, I had it on both of my systems every day on any 6.12 release with macvlan. I moved all dockers to br1 on a second nic and there's been zero crashes in a week or so now. I think that fixed it. I'd use IPVLAN but my ATT gateway is weird with port forwarding based on MACs rather than IPs and everything breaks.