loady

I have this issue that wasnt there before, if all dockers are started, the drives wont spin down, they seem to go crazy every five minutes or so then silent but dont spin down, even if i spin them all down they will all spin back up eventually over a couple of minutes, i have been testing to see which docker it is, it doesnt seem to be any specific docker and what i have found is that if i start any 12 of them the server is quiet and drives will spin down and stay spun down, if i start a 13th docker, it doesnt matter which docker it is, the drives all spin up and starts going mad, i have tested all the dockers individually and none of them spin the drives up on thier own or even started in small groups. I dont think it is because the docker image is to small but i wouldnt know. The docker image is on the cache drive and always has been, could it be the drive failing ? i cant see any obvious signs.

This is odd, so it doesnt matter which docker it is, i have 14 in total, as soon as i start the 13th one, doesnt matter which docker it is, the server crashes, drives goes crazy and have to hard boot

It isnt the any single docker, i added them one by in reverse order, the ones i thought were causing the issue are fine, now the ones i added in last start the drives going crazy, it seems that it starts to do it when i start a certain number of dockers, what ever the last ones are i add look to be the cause but on thier own they are fine, i only 14 dockers, not sure what gives here

all docker apart from ?MariaDB and Radarr are installed, Radarr seems to keep the drives spun up and chattering every minute or so, i have left it for an hour, spun them down but it keeps spinning back up and making lots of reads, it wasnt doing this previously, it isnt locking up the server though. If i stop Radarr it goes back to normal, can spin down drives and they stay spun down, i have added fresh diags, going to try MariaDB again to see if that is still the culprit for locking up the server warptower-diagnostics-20250110-1235.zip

I will need it eventually, its the datbases for nextcloud, i have installed all the dockers except for the mariaDB one, the server is not locking up but the drives are going crazy and staying spun up. Will stopping dockers one by one untill it settles work to find out which one is causing it ? warptower-diagnostics-20250109-1500.zip

MariaDb is the culprit i think, not even sure what its for, think it had something to do with my nextcloud, not really sure as it was set up for me, i had noticed that the GUI had stopped working whereas before it would take me to something, as soon as i installed it the drives all started chattering and it started to get laggy, i removed it before it completley locked up and will carry on with the rest of the dockers then do that one last again

Its been sat there all night without the docker service started and all the disk are spun down, i have just deleted it and started docker service and all is quiet still, disk 8 has spun up but there isnt that constant chattering of all the drives when the service is running, GUI is nice and fluid. I guess start adding them one ast a time ?

as soon as i start the service, i deleted the docker image and started to reinstall the previous dockers as per the link you provided, it got to about the 4th one when it got to the point of being unresponsive so i would say that it is any one particular docker, i think it would do it if i started the service with no dockers present as well

warptower-diagnostics-20250107-1732.zipsyslog Pretty sure its on the cache drive, when i put in the new hardware it is my intention to have two x 1tb nvme drives for the cache

i did this but it locked whilst reinstalling the dockers, ill reboot it again and grab diags with docker running before it locks up again, its definatley something to do with it as it will run fine without the docker enabled

Looking good, zero errors...problem now is if i start the docker service the drives are going crazy and its just locking up, i also want to add the two 12TB drives i got for dual parity Doesnt seem to want to shut down now with power button, even after an hour, i dont really want to cold shut down it, are these SSH settings correct ?

That worked, its not lagging now and the drives are quiet...replace disk 2 now ?

Happy new year to you. Ok, was going to change hardware but still having issues here, the server seems to stagnate now, after about 20 mins its so laggy it becomes unusable, you can still ping it, see the share in windows but cant access it, i cant SSH into it, now disk two is disabled where it wasnt before although i was planning to change that one, it will turn off with a press of the power button but takes about 30 minutes to actually shut down, so the new diags and syslog should be from a clean shutdown. I had to shut down again and restart it because by the time i had written this post it had become unresponsive again whilst getting the syslogsyslogwarptower-diagnostics-20250105-1439.zip I have rebooted into to safe mode, if that is stable can i go ahead with replacing disk 2 in safe mode ? EDIT: scrap that, its doing the same in safe mode too now, hardeware change next for sure now, no matter what

Safe to say that disk was fubered for sure ! i am going to put the new hardware in before i swap disk2 as it is now crashing during parity check.

Merry Christmas to you. So disk 6 is all rebuilt and up and running, do i need to change ALL the disks showing error ? i think a couple are heat errors which i will be resolving when i get a variable potentiometer to briing the fan bank voltage down. Disk2 was needing replacing and then i ran into to problems with disk 6, so should i go ahead with replacing disk2 ? warptower-diagnostics-20241225-1203.zip