I just experienced some 100% load, 'system is sluggish', >80-degC CPU temp, 76C HDD temp, can't kill docker container, can't complete an OS reboot or shutdown, can't even log back in to TOS via web interface, TNAS app for Android or PuTTY/SSH weirdness this weekend with my recently purchssed F2-424. My TNAS is running TOS6 running off a NVMe and my media files on a WD Red Plus in Bay#1.
The other day, I installed the photo app 'immich' to the NVMe via Docker/Portainer and I think there was a configuration issue as I soon noticed over 450,000 thumbnails had been created that day (on the HDD) and were now appearing on the most recent day in my image timeline (which I don't think is correct)... and then, I think, it found all these new images and triggered new thumbnails to be created for each of those new images, a horrible loop that apparently put the CPU at 100% load. As I said in the opening sentence, it wouldn't complete shutdown via TOS and eventually got so sluggish I couldn't even complete a log in via PuTTY/SSH from my PC.
Having manually powering off the TNAS via the button on the back of the device, I waited for it to finish booting to TOS and then logged in and saw it immediately at 100%. Could not even complete the simple task of going App Center>Installed->Portainer->Open, or ...Installed->Docker Manager->Open. Logging in via PuTTY/SSH I ran a docker kill command, which resulted in an error message or hang, and did not kill all the immich containers.
What could I do?
I had an idea: if I manually powered off via the button (which is not ideal as the drive was busy being written to), I could then remove the Bay#1 caddy, power back on, and hopefully with the drive no longer accessible, my 'immich' docker container couldn't run its routine so the CPU load should be far lower and perhaps I could at last manually stop the container. Yes, that actually worked. I stopped the container, and made some changes to my immich docker compose/.env settings and then put the drive back in and rebooted. SUCCESS!
But it is a very worrying situation when you see the CPU and HDD temps soaring and find the TNAS OS almost 100% unresponsive, and actually unable to even complete a successful login attempt so you can try to do something about it remotely. I think mine ran for 10 hours at 100% load and high temps....
The other day, I installed the photo app 'immich' to the NVMe via Docker/Portainer and I think there was a configuration issue as I soon noticed over 450,000 thumbnails had been created that day (on the HDD) and were now appearing on the most recent day in my image timeline (which I don't think is correct)... and then, I think, it found all these new images and triggered new thumbnails to be created for each of those new images, a horrible loop that apparently put the CPU at 100% load. As I said in the opening sentence, it wouldn't complete shutdown via TOS and eventually got so sluggish I couldn't even complete a log in via PuTTY/SSH from my PC.
Having manually powering off the TNAS via the button on the back of the device, I waited for it to finish booting to TOS and then logged in and saw it immediately at 100%. Could not even complete the simple task of going App Center>Installed->Portainer->Open, or ...Installed->Docker Manager->Open. Logging in via PuTTY/SSH I ran a docker kill command, which resulted in an error message or hang, and did not kill all the immich containers.
What could I do?
I had an idea: if I manually powered off via the button (which is not ideal as the drive was busy being written to), I could then remove the Bay#1 caddy, power back on, and hopefully with the drive no longer accessible, my 'immich' docker container couldn't run its routine so the CPU load should be far lower and perhaps I could at last manually stop the container. Yes, that actually worked. I stopped the container, and made some changes to my immich docker compose/.env settings and then put the drive back in and rebooted. SUCCESS!
But it is a very worrying situation when you see the CPU and HDD temps soaring and find the TNAS OS almost 100% unresponsive, and actually unable to even complete a successful login attempt so you can try to do something about it remotely. I think mine ran for 10 hours at 100% load and high temps....
Statistics: Posted by DanielB — Today, 13:49