July 19, 20223 yr I do not know where to even begin to troubleshoot this. I've restarted the machine several times.
July 19, 20223 yr Community Expert 11 minutes ago, Sickdove said: where to even begin same with every issue. attach diagnostics to your NEXT post in this thread
July 19, 20223 yr Author 15 minutes ago, Sickdove said: I do not know where to even begin to troubleshoot this. I've restarted the machine several times. Just noticed my cache drive was 100% full. Something in the machine is not working properly and the drives where failing. Once i started the MOVE from cache manually and rebooted the docker started working.
July 19, 20223 yr Community Expert You should avoid completely filling any drive, especially btrfs such as cache. Share N-------d is set cache:no but has files on cache. Mover ignores cache:no shares so those files will remain stuck on cache. You will have to set it to cache:yes and run mover to get them moved to the array. Then you can set it to cache:no Your cache isn't really large enough for much except appdata, domains, system shares where dockers/VMs need to run. So you might not want to cache any other user shares. Mover won't really help keep your cache from filling up since it is impossible to move from fast cache to slow array as fast as you can write to cache.
July 19, 20223 yr Author Thanks for the reply. The system has been working smooth for over a year(+). Something went sideways last week when my parity drive failed. I replaced it it and the third array drive failed too. I am thinking my motherboard is having issues. Or maybe the power supply is not large enough. Or maybe the extreme heat in SoCal. But for some reason the cache drive got full and the entire system failed. If it wasn't for CA-Fix Common Problems i wouldn't have looked at the cache drive been full. In any case this is the time to be prepared in the event the machine fails (Hardware fail) and I need to be able to rebuild the system. (I hope it doesn't)
July 19, 20223 yr Community Expert 34 minutes ago, trurl said: You should avoid completely filling any drive, especially btrfs such as cache. If you don't write much to cached shares mover might be able to move it all to the array before it fills, but 35 minutes ago, trurl said: Mover won't really help keep your cache from filling up since it is impossible to move from fast cache to slow array as fast as you can write to cache. Mover is intended for idle time, default schedule is daily in the middle of the night.
July 20, 20223 yr Author 23 hours ago, trurl said: If you don't write much to cached shares mover might be able to move it all to the array before it fills, but Mover is intended for idle time, default schedule is daily in the middle of the night. Cache is set to run on the hour and move everything to the drives. Something happened when the parity drive failed. I am still trying to sort out why nextcloud has stuff in it. I intentionally didn;t want it to use the cache drive. SO far I am looking to replace the motherboard or power supply. I really can't pinpoint what went wrong.
July 21, 20223 yr Community Expert 9 hours ago, Sickdove said: Cache is set to run on the hour Running mover more often won't help unless these are idle times on the server. On 7/19/2022 at 1:07 PM, trurl said: it is impossible to move from fast cache to slow array as fast as you can write to cache. On 7/19/2022 at 1:43 PM, trurl said: Mover is intended for idle time
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.