lovaan Posted November 15, 2018 Share Posted November 15, 2018 So at midnight last night my server started a parity-check, and as far as I know it shouldn't have. I currently have it in the scheduler to run yearly on the 15th of January. Is there any other reason it would start on it's own without manually starting it, or is it more likely I have a glitch in a config file somewhere? Link to comment
Squid Posted November 15, 2018 Share Posted November 15, 2018 What's the uptime listed on the top right of the GUI? Does it correspond with the start of the parity check? Also, there were some schedule problems with some of the 6.6 series. Update to 6.6.5 Link to comment
Duglz Posted November 15, 2018 Share Posted November 15, 2018 I'm getting the same thing on 6.6.3, will upgrade to 6.6.5 tonight to see if that helps. Uptime has been up for 2+ days and one started around 14 hours ago. Diag attached. storage-diagnostics-20181115-1440.zip Link to comment
Squid Posted November 15, 2018 Share Posted November 15, 2018 6.6.5 still has a problem if you select Sunday as the day to run checks. Any other day though works fine. Already fixed for the next release Link to comment
lovaan Posted November 15, 2018 Author Share Posted November 15, 2018 Yeah - uptime is somewhere in the 30 day range. Having selected a yearly parity check Sunday isn't even an option to select. I'm still on 6.6.1, so I'll just wait for that next release before I decide to update. In the mean time I suppose I'll just keep an eye out for spontaneous parity checks. Link to comment
Duglz Posted November 30, 2018 Share Posted November 30, 2018 I did an update to 6.5.5 and I got another random parity start that crashed my server. Attached diag. storage-diagnostics-20181130-0534.zip Link to comment
JorgeB Posted November 30, 2018 Share Posted November 30, 2018 Parity check started because: Nov 30 04:24:29 Storage emhttpd: unclean shutdown detected Link to comment
heisenfig Posted December 9, 2018 Share Posted December 9, 2018 I'm on 6.6.5 and had the parity checks scheduled weekly on Sunday. It was doing a parity check every morning at 8am (if it wasn't still running from the previous one). I disabled the schedule and it stopped. I just re-enabled it weekly on sunday, then changed it to weekly Saturday evening. Then I noticed that it was running a few minutes later (before the scheduled time). I don't know if it started before I switched it to Saturday. I'll keep an eye on it and see if it's still doing it daily with it set for Saturday's. Link to comment
trurl Posted December 9, 2018 Share Posted December 9, 2018 14 minutes ago, heisenfig said: I'm on 6.6.5 On 11/15/2018 at 5:53 PM, Squid said: Already fixed for the next release 6.6.6 already released Monday Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.