Hi at all,
I am very new to Unraid and this Forum, so please forgive me if I have choosen the wrong thread.
All runs well with the system but the time needed for parity-check ist very long in my opinion: a little more than 1 day and 3 hours.
Therefore I tried to install the "Parity Check Tuning" to split the time of parity checking.
Always when trying to start the "Schedule" from Main/Array Operation I got the Message "The Unraid Cumulative Parity Check option must not be used if you want to use this plugin to handle pause and resume of scheduled Parity Checks".
So I disabled the "Standard" Parity check but always got the "Incompatible Options" when trying to fill in the options of the tool.
My searches here and in Google were not successful. What did I wrong?
Could anybody explain the situation and give a little help to get he parity checking run in parts? "Normally" the system sleeps from 1 to 7 o´clock in the night.
Sorry for my bad English. And thanx in advance for your help!
Hannes

jobonas-diagnostics-20240314-1129.zip

You must still have the standard parity check set to the schedule when you want the parity checks started, but you must set the Cumulative Parity Check setting to No if you are using the Parity Check Tuning plugin to handle pause/resuming of increments. 

 

I'll reword that message to make it slightly clearer.

 

Thanx a very lot! Now it runs without Error-windows!
I am very happy for this fast reaction and solution!
 

Hello, i need some help.  I have the same problem.

I want a parity check once a week. Because i have 24 TB disk, it takes a long time.

I have installed the parity check tuning plugin. 

Can i get some help, how to configure to do so?

I get the same error like the user in this post.

It should  not begin at zero after a reboot.

thank you

Eberhard

18 minutes ago, ziebolz said:

I want a parity check once a week

Why?

 

Parity is maintained real-time. Anytime the array is written, parity is updated at the same time. 

 

Most do monthly checks or even less frequently. 

 

Parity check is not required for parity to be valid. 

 

Do you often have parity errors? If so you need to investigate why.

No, but i had pending sectors on one new drive . They are gone after a preclear and check. Now there is no reason to sent it to WD. If i write a file, i think there is no verify after writing. When i do a parity check for the next weeks, i thought there would appear a parity error, if the drive had a sector problem?

1 hour ago, ziebolz said:

It should  not begin at zero after a reboot.

Have you configured the plugin in its settings to restart array operations after a reboot?    Even if you have for safety reasons the operation is not resumed if you get an unclean shutdown.  If you think you have everything configure correctly then posting diagnostics taken after a case where it does not restart the array operation might allow me to tell you why.

 

As was mentioned doing a check once a week is definitely overkill unless you think you have unreliable hardware.  Probably the commonest interval is monthly, although less frequently (e.g. quarterly) is also not unusual.

On 3/14/2024 at 11:23 AM, Hannes55 said:

Therefore I tried to install the "Parity Check Tuning" to split the time of parity checking.
Always when trying to start the "Schedule" from Main/Array Operation I got the Message "The Unraid Cumulative Parity Check option must not be used if you want to use this plugin to handle pause and resume of scheduled Parity Checks".

That message is misleading and I will look into clarifying.    You must not disable the built-in parity check running at the frequency you want as the plugin never initiates a parity check - just handles pausing and resuming of one already initiated.    What the message is saying is that you must disable the option in the standard settings for the cumulative checks as otherwise you will get strange results as the standard software and the plugin both try and handle pauses and resumes and get in each others way.

Ok thank you now it works.

Weekly is too much. I will do a check one ore two times in the next week, to check the hardware. When this passes with no error, it is ok for the next  time i think.

But i need the resume option, because this mainboard is very slow and runs not 24-7.

Thank you for your help.

4 minutes ago, ziebolz said:

But i need the resume option, because this mainboard is very slow and runs not 24-7

I use that feature myself as I switch my system off overnight.   If it is not resuming because you are getting unclean shutdowns then that needs fixing first.