atvking

I was having a similar issue to you and before searching for a solution on this thread I decided to create a Post-run script. The script waits 5 mins then restarts any containers that use the container as their network. This seems to have "fixed" the issue for me, however, I don't have auto update enabled so I suppose I could just do what you did with the container grouping/restart order and omit the script. Maybe the script is worth a shot If you're still interested in enabling the auto update feature(and it's still not working). If you'd like to try, make sure to save your script with Unix line breaks (In Notepad++ click Edit > EOL Conversion > Unix (EF)). Put the script somewhere that's accessible via the plugin and make it executable (Open terminal and run "chmod +x /mnt/user/path/to/script/script_name.sh"), then point to that script as a "Post-run script" in the plugin. #!/bin/bash # Some values from the plugin - might be useful to you for further customization ACTION=$1 DEST_PATH=$2 SUCCESS=$3 # log results to file LOG_FILE="/mnt/user/path/to/logs/log_name.log" # Specify your gluetun container name here NETWORK_NAME="GluetunVPN" NETWORK_ID=$(docker inspect -f '{{.Id}}' "$NETWORK_NAME" 2>/dev/null) mkdir -p "$(dirname "$LOG_FILE")" { echo "--------------------------------------------------------------------------------------------------------------------------------" echo "Run Date: $(date '+%Y-%m-%d %H:%M:%S')" echo "Backup Status: $SUCCESS" # 5-minute delay sleep 300 if [ -z "$NETWORK_ID" ]; then echo "Error: Could not find Network ID for $NETWORK_NAME. Is the name correct?" else # Get list of containers using your Gluetun container as thier network CONTAINER_LIST=$(docker inspect --format '{{if eq .HostConfig.NetworkMode "container:'$NETWORK_ID'"}}{{.Name}}{{end}}' $(docker ps -aq) 2>/dev/null | sed 's/\///' | grep .) # Alternatively, get list of containers using any container as thier network - In this case setting and validating NETTWORK_NAME and NETWORK_ID are not needed. # CONTAINER_LIST=$(docker inspect --format '{{if (ge (len .HostConfig.NetworkMode) 10)}}{{if eq (slice .HostConfig.NetworkMode 0 10) "container:"}}{{.Name}}{{end}}{{end}}' $(docker ps -aq) 2>/dev/null | sed 's/\///' | grep .) if [ -z "$CONTAINER_LIST" ]; then echo "No containers found using network: container:$NETWORK_NAME ($NETWORK_ID)" else for container in $CONTAINER_LIST do RUNNING=$(docker inspect -f '{{.State.Running}}' "$container" 2>/dev/null) if [ "$RUNNING" == "true" ]; then # Only restart containers that are already running - You may want to change this docker restart "$container" > /dev/null 2>&1 if [ $? -eq 0 ]; then echo "Successfully restarted $container." else echo "Error: Failed to restart $container." fi else echo "Skipping $container: Not currently running." fi done fi fi echo "Process complete." # Only keep the last 500 lines of log - Can probably set this to a lower number tail -n 500 "$LOG_FILE" > "$LOG_FILE.tmp" && mv "$LOG_FILE.tmp" "$LOG_FILE" } >> "$LOG_FILE" 2>&1 exit 0

Mbits/sec does not equal MB/s... 1MB is 8Mbs (8 bits to a byte) Therefore your rsync transfer speed was 24.32 Mbits/s (pretty much spot on your iperf3 test) Mbits/s is often also written as Mb/s. The uppercase vs lowercase B is an important differentiation .

I just experienced this issue with several containers (Nextcloud, Swag, Sonarr, Radarr, Plex, and a few more) and was able to fix it so I thought I would share what I did in case anyone came looking in the future. I was having issues with steps 4-7 causing my server to hang and the GUI to become unresponsive so here's what I tried that ultimately worked for me: Try steps 4-7. If they don't work or cause a server hang, comeback and start at 2. Shutdown Unraid (force it if you have to and are comfortable with the risk) Once restarted, stop any running containers (not sure if necessary but I did it as a precaution) Delete orphaned images via the bottom of the Docker tab in Advanced mode. While still in Advanced mode, force update any containers that were failing to start with the error listed by OP. Disable and re-enable the docker service via Settings > Docker (not sure if required, did this as a shortcut to get containers to auto-start rather than manually starting each). Check your docker tab and attempt to start anything that hasn't auto-started, they should all start as expected.

Can you share how you managed to reformat the pool if you were unable to stop the array? I'm having the same issue right now and it's looking like a reformat is my only option.