khaotiq

Not sure if this will help some - but after running rm /var/lib/docker/network/files/local-kv.db /etc/rc.d/rc.docker restart I was missing my custom docker network, no problem, I re-added it, but none of the containers automatically reconnected. I noticed I could go in and manually adjust the template and reselect the new custom network and the container would start fine...but this would take way too long to go through each one. I ChatGPT made a script that will get list of all containers. Will check network of each container and if using the defined network, it will disconnect it and reconnect it the new one(of same name), skipping any containers that use some other network (br0, bridge, host...) #!/bin/bash # Network name network_name="proxynet" # List all containers containers=$(docker ps -a --format '{{.Names}}') for container in $containers; do # Retrieve the container's network information network_info=$(docker inspect --format='{{range $key, $value := .NetworkSettings.Networks}}{{if eq $key "'$network_name'"}}true{{end}}{{end}}' $container) # Check if the container is connected to the specified network if [ "$network_info" = "true" ]; then echo "Updating network for $container" # Disconnect from the old network (ignore errors if not connected) docker network disconnect --force $network_name $container 2>/dev/null # Connect to the new network docker network connect $network_name $container # Restart the container to apply changes docker restart $container else echo "$container is not connected to $network_name, skipping..." fi done

Yes I am sure everything is OK. What about "Preserve current assignments", I assume just leave as default, no. For diagnostics, the whole zip or specific log? Also, I am currently in safe mode. Should I reboot back to normal?

So....I probably went about this the wrong way to begin with, but... I replaced my parity drive with a larger drive to then at a later point in time add another larger drive to increase capacity. As it was rebuilding parity, I accidently disconnected (loose cable, bumped) another drive and it became "disabled". With that drive disabled, rebuilding the parity on the new drive paused and wouldn't start. I read that in order to re-enable the disabled drive I would need to stop array, unassign, start maintenance, stop, then reassign...but that put that drive in "New Device" status. I haven't tried starting the array because of this, and as the parity never finished rebuilding. There is nothing wrong with that drive or any others including the old parity drive...I was just increasing capacity. I have now seen and been suggested to look at Tools > New Config or to remove the drive and try and mount elsewhere and copy the data. Restart the array and copy the data back. I looked at New Config but honestly the wording is intimidating and I don't want to continue and mess things up further. In the above screen shot, Parity is also showing as a "New Device" but that is the old Parity drive that I reinstalled, with the idea to just rebuild disk 5 from the old parity...but when it showed up as New Device I aborted that idea. Any help would be greatly appreciated