[[Plugin] Parity Check Tuning]

On 9/19/2021 at 4:34 PM, itimpi said:

I tried to recreate your symptoms but have so far not succeeded?

 

one thing that occurred to me is there any chance a temperature related pause could have been active at the time the scheduled pause should have happened?   If so maybe the plugin is getting confused, and resuming when the temperatures return to good values when it should not?    It is surprisingly hard to set this up as robust test scenario that works correctly which is why I thought it was worth asking first before trying to simulate that specific set of circumstances.

 

Revisting a slightly old comment here - but looks like the scenario you mentioned here might've occurred to myself today.

Parity was scheduled to pause at 9:00am, but temperature related pause triggered at 8:28am, and then resumed at 9:07am.

 

Attached a diagnostics file as well, in case it's something worth looking into.

 

Feb  1 08:28:01 UnraidOS Parity Check Tuning: Paused Correcting Parity Check  (23.5%% completed): Following drives overheated: parity(45C) disk1(43C)
Feb  1 08:28:01 UnraidOS kernel: mdcmd (49): nocheck PAUSE
Feb  1 08:28:01 UnraidOS kernel:
Feb  1 08:28:01 UnraidOS kernel: md: recovery thread: exit status: -4
Feb  1 08:43:03 UnraidOS emhttpd: spinning down /dev/sdb
Feb  1 09:00:16 UnraidOS emhttpd: spinning down /dev/sde
Feb  1 09:00:42 UnraidOS emhttpd: spinning down /dev/sdc
Feb  1 09:07:01 UnraidOS Parity Check Tuning: Resumed Correcting Parity Check  (23.5%% completed) as drives now cooled down
Feb  1 09:07:07 UnraidOS kernel: mdcmd (50): check RESUME
Feb  1 09:07:07 UnraidOS kernel:
Feb  1 09:07:07 UnraidOS kernel: md: recovery thread: check P ...
Feb  1 09:07:07 UnraidOS emhttpd: read SMART /dev/sde
Feb  1 09:07:07 UnraidOS emhttpd: read SMART /dev/sdb
Feb  1 09:07:07 UnraidOS emhttpd: read SMART /dev/sdc

 

unraidos-diagnostics-20220201-1155.zip