mozyman

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