December 30, 200916 yr I noticed that my 4.5 keeps initiating and running parity-checks. The system finished one check sometime in the middle of the night and automatically started another one. I do not see any errors reported on the maid GUI web page. There has been not power failure that I am aware off. The system was not recently rebooted. I have not changed anything in the configuration. Why does it keeps running checks and how can I tell if there is something more insidious going on? Thanks.
December 30, 200916 yr I noticed that my 4.5 keeps initiating and running parity-checks. The system finished one check sometime in the middle of the night and automatically started another one. I do not see any errors reported on the maid GUI web page. There has been not power failure that I am aware off. The system was not recently rebooted. I have not changed anything in the configuration. Why does it keeps running checks and how can I tell if there is something more insidious going on? Thanks. You can start by posting a syslog. Instructions in the wiki. unRAID will never initiate a parity check on its own. It has no built-in schedule, unless you add one, nor does it have any process I'm aware of that will start a parity check on an error after the array has been started. It will initiate a parity check if it is shut down without being stopped first and then re-started. This will happen in a power failure unless you add scripts and a UPS to shut down cleanly in an extended failure. Your syslog will show if the server rebooted during the night and provide any other clues that might be helpful in analysis. Joe L.
December 30, 200916 yr Joe, Sorry... Here it is... As far as I can see, your server was rebooted at 9:09 this morning. Dec 30 09:09:32 Tower syslogd 1.4.1: restart. it had a power hit perhaps??
December 30, 200916 yr Author Interesting... My other PC did not report a power failure. the unRAID box is on a UPS. I wonder why it went down... Maybe I need to go to a more robust UPS? Thanks Joe!
Archived
This topic is now archived and is closed to further replies.