Dr. Nepharius
Members
-
Joined
-
Last visited
-
I created one using doing almost a 1:1 to the original picture, but when applying I don't think it looks good since it gets crowded. Either way I uploaded here and will try to work on a V2 once I have some downtime during the week. Planning on making the lines thicker and using less horizontal bars.
I recently replaced my old Node 304 with an i7 7700 with the UGREEN 6800 Pro and installed Unraid on it and it was working like a charm. Since I have multiple backups (tested multiple times and able to go back to a normal state) and was looking forward to test the Arc GPUs, I installed the new Unraid 7 beta. The GPU works without issues and almost everything is working as intended except for 1 situation: updating docker containers. Doing that, more than often, causes my server to “crash” and for the life of me I can’t figure it out why. Before updating to Unraid 7 beta I didn’t have any issues whatsoever. I selected a few apps to update and the process starts as normal, but hangs (Image 0031) 2) Shortly after it fails, saying that there’s already a container using the same name, which is 100% not the case (Image 0032) 3) The screen stays like this forever (left like this for quite some time) and after I refresh, it takes forever to load anything on the GUI, independent of the page. 4) After the main ”Dashboard“ loads, it doesn’t show the docker containers or VMs that are running, despite them running if I type their IP/port (Figure 0033). The only container that it doesn’t work is the one that failed to update. In terms of troubleshooting steps I tried: Stopping and starting the docker service. It hangs at the stopping portion and it never fully stops Stopping and starting the docker service thru CLI. Same issue that the service is never truly stopped Kill processes that are related to docker, images and containers and attempting the above. Although I didn’t get any error on killing the processes, the docker service fails to stop/start Attempt to reboot and turn-off the server thru the CMD and physical button, for a normal reboot process. It triggers the reboot, but it stops at unmounting something that I can’t quite remember and it never goes past that. The only solution that works is to forcefully reboot the server by turning off the power or using a kernel trick. After the reboot the server works as normal and no issues with any containers, although I have the same issue as above when trying to update a container. I added the anonymized diagnostics as well. I appreciate beforehand if anyone can help. unraid-diagnostics-20240709-1556.zip
