fuzzaldrin

🎉 RESOLVED 🎉 OK so I managed to pinpoint that the container was still registered in docker however without any access to the console or terminal I couldn't remove the container or the offending network. I created a script in the User Scripts plugin to run every 2 minutes with the following: #!/bin/bash docker stop adguard docker container rm adguard -f docker network rm adguard_adguard echo Finished echo if an error shows above, nothing was removed I started the docker service from the setting and could immediately see the permanent ping I had running on the unraid admin console drop, waited for the script to run on schedule and immediately I saw the ping successfully respond. I opened a new tab and loaded the unraid admin console/GUI successfully! For the sake of anyone else that may run into this niche issue, I've included the output of the user script below, it shows the script run before the docker service was started and obviously failing to remove the network and container and then subsequently shows the script successfully run and delete the network and container: Script Starting Jan 23, 2026 21:36.01 Full logs for this script are available at /tmp/user.scripts/tmpScripts/docker_remove_adguard/log.txt Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running? Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running? Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running? Finished if an error shows above, nothing was removed Script Finished Jan 23, 2026 21:36.01 Full logs for this script are available at /tmp/user.scripts/tmpScripts/docker_remove_adguard/log.txt Script Starting Jan 23, 2026 21:38.01 Full logs for this script are available at /tmp/user.scripts/tmpScripts/docker_remove_adguard/log.txt adguard adguard adguard_adguard Finished if an error shows above, nothing was removed Script Finished Jan 23, 2026 21:38.01 Full logs for this script are available at /tmp/user.scripts/tmpScripts/docker_remove_adguard/log.txt

I've removed the compose file for that service and tried starting docker and the same behaviour is happening :( After rebooting I can see this in the logs just as I started the docker service: Jan 23 21:05:50 teapot rc.docker: container adguard has an additional network that will be restored: adguard_adguard This is weird because I deleted that compose file from compose manager plugin before starting the docker service so this is lingering somewhere on the system.

This is the contents of the docker.cfg file in the flash drive:

Hi folks, I created a some additional networking in a docker compose file and upon deploying it my unraid server was inaccessible. I had to press the power button to start the shutdown process. On starting the server I can only start the array if the docker service is stopped and I think it is because the network I added in the compose file broke my docker networking config. If I start the docker service the GUI/admin panel fails to load and the server becomes inaccessible again. The compose file is: networks: adguard: driver: bridge ipam: config: - subnet: 192.168.0.0/24 gateway: 192.168.0.1 services: adguard: image: adguard/adguardhome:latest container_name: adguard ports: - 5443:5443/udp - 5443:5443/tcp - 8853:8853/udp - 853:853/udp - 784:784/udp - 853:853/tcp - 3008:3000/tcp - 53:53/udp - 53:53/tcp volumes: - /mnt/user/appdata/adguard/conf:/opt/adguardhome/conf - /mnt/user/appdata/adguard/work:/opt/adguardhome/work restart: unless-stopped networks: adguard: ipv4_address: 192.168.0.53 This is my docker settings page: Route table is here: Could someone please help with getting the docker networking config back to something sensible? My LAN IP range is 192.168.0.1/24

Parity audit for clarity:

Hi folks, I recently got notified of a handful of errors with a 3 year old data disk. I did a parity check (non-writing) and it reported a lot of sync errors. I replaced said disk with a new larger disk and the data rebuild has just finished reporting errors: The notification of the data rebuild was a normal/green notification and so not an alert but am I correct in thinking that the errors in the data rebuild is bad? What are my next steps? I haven't done a correcting parity check since I didn't want to potentially corrupt a good parity but now I'm unsure what to do. Any help is appreciated, thanks in advance.

Yea it's really strange. What I've done previously is preclear the disk using this method and then when it comes to swap out a disk it goes into a SATA port and into the array, rebuild etc.

Just tried a different NTFS formatted disk in the dock and that's not appearing either.

I'm fairly certain those log entries about the USB mass storage device are the docking station. Additionally, I have connected the disk in that dock to my Windows machine and it detects it, I can write to it etc. I'll try a different disk now.

I have a HDD docking station I have previously used to add disks to unassigned devices and then run a preclear, I have done this twice successfully in the past. I'm now in need of an additional disk for the array so I put the disk in the docking station but unassigned devices will not show the disk. I can see the device listed in the logs but beyond that nothing happens. I have stopped the array and restarted the server but that hasn't made a difference. Running version 6.9.1 of Unraid Latest version of UA (2022.10.12) Any thoughts? teapot-diagnostics-20221025-1210.zip