several of the dockers and plugins had updates, so i started with the plugins and those updated fine.

i moved on to the dockers and did update all as i normally do. this time i noticed it was trying to stop the first docker for a long time.

i opened the docker page from another browser tab and it showed the docker was already up-to-date but i couldn't access it and the docker's log said something about it being marked to be destroyed or something like that.

but i think the dockers were still being updated eventhough it looked like it was still stuck trying to stop the first docker, because the next dockers also started to showing up-to-date when i came back to the page.

after a while i couldn't access the webui and none of the dockers seem to be working.

i thought i'd give it some time and waited about an hour now, webui still down. i get the nginx internal server error 500 page.

but SSH is still ok. VMs are also ok (pfsense still working).

 

any suggestions what i should do? should i try restarting unraid? what's the command for restarting?

or try to restart webui? (if that's possible)

 

curious whether this has anything to do with my btrfs cache pool failing 2 days ago. docker image, appdata, vms were on it. moved everything that was on it to a new xfs cache pool and everything seemed fine.

but whatever the issue, the docker update seems to have triggered it. maybe a corrupted docker image?

i tried doing diagnostic from SSH but it seem to get stuck

i also tried powerdown -r and it also got stuck.

finally i had to hold the power button to force shutdown. unraid started back up and of course started parity check.

all the dockers appeared up-to-date but some dockers couldn't start so i removed them and added them back. really great that we can add dockers back by using templates so that bit was super easy.

 

things seem like back to normal now but since couldn't get the diagnostics so i guess we won't be able to figure out what went wrong. but i think it most probably had to something to do with docker. maybe just a glitch.