April 1, 20242 yr As I only run a full parity check once a quarter, I am not sure when this issue may have arisen since the last check I did. I do not have the Parity Check Tuning plugin so expect the check to take about 12 hours on a 40TB system (5 x 8TB disks incl parity). No Smart errors on any disks. It's housed in an unheated cool area and whilst parity runs, no disk temp goes bout 46C with most of the time the disks operate about 40C. I set the job running and it ran for about 2.5 hours with no issues at which time I logged off the UI to go to bed. Looking at the previous log, it appears the system may have just shutdown even though the S3 sleep plugin is set to monitor for parity check. Have attached my diagnostics file if that helps to figure out what is going on! Thanks nas-diagnostics-20240401-1044.zip Edited April 1, 20242 yr by Bob Corless
April 1, 20242 yr Community Expert Sounds like an issue with the S3 sleep plugin so you should probably bring this up in its support thread.
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.