CS01-HS

They all need to be "cool" which is determined by the Resume setting, not the Pause setting ("hot") Set debug logging to "Testing"

Are you sure it's not user error? The latest update fixed it for me, thanks itimpi! Sep 8 06:55:01 NAS parity.check.tuning.php: DEBUG: -----------MONITOR start------ Sep 8 06:55:01 NAS parity.check.tuning.php: DEBUG: Parity check appears to be paused Sep 8 06:55:01 NAS parity.check.tuning.php: TESTING: parity temp=32 (settings are: hot=40, cool=35)) Sep 8 06:55:01 NAS parity.check.tuning.php: TESTING: disk1 temp=36 (settings are: hot=40, cool=35)) Sep 8 06:55:01 NAS parity.check.tuning.php: TESTING: disk2 temp=35 (settings are: hot=40, cool=35)) Sep 8 06:55:01 NAS parity.check.tuning.php: DEBUG: array drives=3, hot=0, warm=1, cool=2 Sep 8 06:55:01 NAS parity.check.tuning.php: DEBUG: Array operation paused but drives not cooled enough to resume Sep 8 06:55:01 NAS parity.check.tuning.php: DEBUG: -----------MONITOR end------- Sep 8 07:00:01 NAS parity.check.tuning.php: DEBUG: -----------MONITOR start------ Sep 8 07:00:01 NAS parity.check.tuning.php: DEBUG: Parity check appears to be paused Sep 8 07:00:01 NAS parity.check.tuning.php: TESTING: parity temp=33 (settings are: hot=40, cool=35)) Sep 8 07:00:01 NAS parity.check.tuning.php: TESTING: disk1 temp=35 (settings are: hot=40, cool=35)) Sep 8 07:00:01 NAS parity.check.tuning.php: TESTING: disk2 temp=35 (settings are: hot=40, cool=35)) Sep 8 07:00:01 NAS parity.check.tuning.php: DEBUG: array drives=3, hot=0, warm=0, cool=3 Sep 8 07:00:01 NAS parity.check.tuning.php: Resumed Non-Correcting Parity Check (77.7% completed) as drives now cooled down Sep 8 07:00:01 NAS root: Cache used space threshhold (75) not exceeded. Used Space: 72. Not moving files Sep 8 07:00:01 NAS parity.check.tuning.php: DEBUG: written RESUME (COOL) record to /boot/config/plugins/parity.check.tuning/parity.check.tuning.progress Sep 8 07:00:02 NAS parity.check.tuning.php: DEBUG: -----------MDCMD start------ Sep 8 07:00:02 NAS parity.check.tuning.php: DEBUG: detected that mdcmd had been called from sh with command mdcmd check RESUME Sep 8 07:00:02 NAS parity.check.tuning.php: DEBUG: -----------MDCMD end------- Sep 8 07:00:02 NAS kernel: mdcmd (236): check RESUME Sep 8 07:00:02 NAS kernel:

Here are the relevant lines from the syslog. I can send the entire log after some cleanup if necessary. It looks like I was wrong about the difference between hot/cold settings but something's causing a failure to resume even when all drive temperatures reach "cool." Start of Parity check (difference of 3 between hot and cool): Sep 7 13:10:23 NAS parity.check.tuning.php: DEBUG: -----------UPDATECRON start------ Sep 7 13:10:23 NAS parity.check.tuning.php: DEBUG: created cron entries for running increments Sep 7 13:10:23 NAS parity.check.tuning.php: DEBUG: created cron entry for monitoring disk temperatures Sep 7 13:10:23 NAS parity.check.tuning.php: TESTING: updated cron settings are in /boot/config/plugins/parity.check.tuning/parity.check.tuning.cron Sep 7 13:10:23 NAS parity.check.tuning.php: DEBUG: -----------UPDATECRON end------- Sep 7 13:10:31 NAS kernel: mdcmd (217): check Resume Sep 7 13:10:31 NAS kernel: md: recovery thread: check P ... Sep 7 13:15:01 NAS parity.check.tuning.php: DEBUG: -----------MONITOR start------ Sep 7 13:15:01 NAS parity.check.tuning.php: TESTING: parity temp=36 (settings are: hot=40, cool=37)) Sep 7 13:15:01 NAS parity.check.tuning.php: TESTING: disk1 temp=37 (settings are: hot=40, cool=37)) Sep 7 13:15:01 NAS parity.check.tuning.php: TESTING: disk2 temp=38 (settings are: hot=40, cool=37)) Sep 7 13:15:01 NAS parity.check.tuning.php: DEBUG: array drives=3, hot=0, warm=1, cool=2 Sep 7 13:15:01 NAS parity.check.tuning.php: DEBUG: Non-Correcting Parity Check with all drives below temperature threshold for a Pause Sep 7 13:15:01 NAS parity.check.tuning.php: DEBUG: -----------MONITOR end------- Sep 7 13:18:57 NAS autofan: Board temp is 46C, hottest disk is 40C (/dev/sdh), setting fan speed to: 165 (76% @ 1588rpm) Sep 7 13:20:01 NAS parity.check.tuning.php: DEBUG: -----------MONITOR start------ Sep 7 13:20:01 NAS parity.check.tuning.php: TESTING: parity temp=36 (settings are: hot=40, cool=37)) Sep 7 13:20:01 NAS parity.check.tuning.php: TESTING: disk1 temp=37 (settings are: hot=40, cool=37)) Sep 7 13:20:01 NAS parity.check.tuning.php: TESTING: disk2 temp=38 (settings are: hot=40, cool=37)) Sep 7 13:20:01 NAS parity.check.tuning.php: DEBUG: array drives=3, hot=0, warm=1, cool=2 Sep 7 13:20:01 NAS parity.check.tuning.php: DEBUG: Non-Correcting Parity Check with all drives below temperature threshold for a Pause Sep 7 13:20:01 NAS parity.check.tuning.php: DEBUG: -----------MONITOR end------- Sep 7 13:25:02 NAS parity.check.tuning.php: DEBUG: -----------MONITOR start------ Sep 7 13:25:02 NAS parity.check.tuning.php: TESTING: parity temp=36 (settings are: hot=40, cool=37)) Sep 7 13:25:02 NAS parity.check.tuning.php: TESTING: disk1 temp=37 (settings are: hot=40, cool=37)) Sep 7 13:25:02 NAS parity.check.tuning.php: TESTING: disk2 temp=38 (settings are: hot=40, cool=37)) Sep 7 13:25:02 NAS parity.check.tuning.php: DEBUG: array drives=3, hot=0, warm=1, cool=2 Sep 7 13:25:02 NAS parity.check.tuning.php: DEBUG: Non-Correcting Parity Check with all drives below temperature threshold for a Pause Sep 7 13:25:02 NAS parity.check.tuning.php: DEBUG: -----------MONITOR end------- Sep 7 13:25:11 NAS autofan: Board temp is 45C, hottest disk is 42C (/dev/sdh), setting fan speed to: 195 (90% @ 1819rpm) Sep 7 13:30:01 NAS parity.check.tuning.php: DEBUG: -----------MONITOR start------ Sep 7 13:30:01 NAS parity.check.tuning.php: TESTING: parity temp=36 (settings are: hot=40, cool=37)) Sep 7 13:30:01 NAS parity.check.tuning.php: TESTING: disk1 temp=37 (settings are: hot=40, cool=37)) Sep 7 13:30:01 NAS parity.check.tuning.php: TESTING: disk2 temp=38 (settings are: hot=40, cool=37)) Sep 7 13:30:01 NAS parity.check.tuning.php: DEBUG: array drives=3, hot=0, warm=1, cool=2 Sep 7 13:30:01 NAS parity.check.tuning.php: DEBUG: Non-Correcting Parity Check with all drives below temperature threshold for a Pause Sep 7 13:30:01 NAS parity.check.tuning.php: DEBUG: -----------MONITOR end------- Sep 7 13:35:01 NAS parity.check.tuning.php: DEBUG: -----------MONITOR start------ Sep 7 13:35:01 NAS parity.check.tuning.php: TESTING: parity temp=36 (settings are: hot=40, cool=37)) Sep 7 13:35:01 NAS parity.check.tuning.php: TESTING: disk1 temp=37 (settings are: hot=40, cool=37)) Sep 7 13:35:01 NAS parity.check.tuning.php: TESTING: disk2 temp=38 (settings are: hot=40, cool=37)) Sep 7 13:35:01 NAS parity.check.tuning.php: DEBUG: array drives=3, hot=0, warm=1, cool=2 Sep 7 13:35:01 NAS parity.check.tuning.php: DEBUG: Non-Correcting Parity Check with all drives below temperature threshold for a Pause Sep 7 13:35:01 NAS parity.check.tuning.php: DEBUG: -----------MONITOR end------- Sep 7 13:40:01 NAS parity.check.tuning.php: DEBUG: -----------MONITOR start------ Sep 7 13:40:01 NAS parity.check.tuning.php: TESTING: parity temp=36 (settings are: hot=40, cool=37)) Sep 7 13:40:01 NAS parity.check.tuning.php: TESTING: disk1 temp=37 (settings are: hot=40, cool=37)) Sep 7 13:40:01 NAS parity.check.tuning.php: TESTING: disk2 temp=38 (settings are: hot=40, cool=37)) Sep 7 13:40:01 NAS parity.check.tuning.php: DEBUG: array drives=3, hot=0, warm=1, cool=2 Sep 7 13:40:01 NAS parity.check.tuning.php: DEBUG: Non-Correcting Parity Check with all drives below temperature threshold for a Pause Sep 7 13:40:01 NAS parity.check.tuning.php: DEBUG: -----------MONITOR end------- Drives overheat, check is paused, drives begin cool-down: Sep 7 13:45:01 NAS parity.check.tuning.php: DEBUG: -----------MONITOR start------ Sep 7 13:45:01 NAS parity.check.tuning.php: TESTING: parity temp=39 (settings are: hot=40, cool=37)) Sep 7 13:45:01 NAS parity.check.tuning.php: TESTING: disk1 temp=42 (settings are: hot=40, cool=37)) Sep 7 13:45:01 NAS parity.check.tuning.php: TESTING: disk2 temp=42 (settings are: hot=40, cool=37)) Sep 7 13:45:01 NAS parity.check.tuning.php: DEBUG: array drives=3, hot=2, warm=1, cool=0 Sep 7 13:45:01 NAS parity.check.tuning.php: Paused Non-Correcting Parity Check (39.6% completed) : Following drives overheated: 42 42 Sep 7 13:45:02 NAS parity.check.tuning.php: DEBUG: written PAUSE (HOT) record to /boot/config/plugins/parity.check.tuning/parity.check.tuning.progress Sep 7 13:45:02 NAS parity.check.tuning.php: DEBUG: -----------MDCMD start------ Sep 7 13:45:02 NAS parity.check.tuning.php: DEBUG: detected that mdcmd had been called from sh with command mdcmd nocheck PAUSE Sep 7 13:45:02 NAS parity.check.tuning.php: DEBUG: -----------MDCMD end------- Sep 7 13:45:02 NAS kernel: mdcmd (218): nocheck PAUSE Sep 7 13:45:02 NAS kernel: Sep 7 13:45:02 NAS kernel: md: recovery thread: exit status: -4 Sep 7 13:45:02 NAS parity.check.tuning.php: TESTING: Heat notifications disabled so Pause Following drives overheated: 42 42 not sent Sep 7 13:45:02 NAS parity.check.tuning.php: DEBUG: -----------MONITOR end------- Sep 7 13:50:01 NAS parity.check.tuning.php: DEBUG: -----------MONITOR start------ Sep 7 13:50:01 NAS parity.check.tuning.php: DEBUG: Parity check appears to be paused Sep 7 13:50:01 NAS parity.check.tuning.php: TESTING: parity temp=39 (settings are: hot=40, cool=37)) Sep 7 13:50:01 NAS parity.check.tuning.php: TESTING: disk1 temp=42 (settings are: hot=40, cool=37)) Sep 7 13:50:01 NAS parity.check.tuning.php: TESTING: disk2 temp=42 (settings are: hot=40, cool=37)) Sep 7 13:50:01 NAS parity.check.tuning.php: DEBUG: array drives=3, hot=2, warm=1, cool=0 Sep 7 13:50:01 NAS parity.check.tuning.php: DEBUG: Array operation paused with some drives still too hot to resume Sep 7 13:50:01 NAS parity.check.tuning.php: DEBUG: -----------MONITOR end------- Sep 7 13:50:08 NAS autofan: Board temp is 39C, hottest disk is 40C (/dev/sdh), setting fan speed to: 165 (76% @ 1605rpm) Sep 7 13:55:01 NAS parity.check.tuning.php: DEBUG: -----------MONITOR start------ Sep 7 13:55:01 NAS parity.check.tuning.php: DEBUG: Parity check appears to be paused Sep 7 13:55:01 NAS parity.check.tuning.php: TESTING: parity temp=39 (settings are: hot=40, cool=37)) Sep 7 13:55:01 NAS parity.check.tuning.php: TESTING: disk1 temp=42 (settings are: hot=40, cool=37)) Sep 7 13:55:01 NAS parity.check.tuning.php: TESTING: disk2 temp=42 (settings are: hot=40, cool=37)) Sep 7 13:55:01 NAS parity.check.tuning.php: DEBUG: array drives=3, hot=2, warm=1, cool=0 Sep 7 13:55:01 NAS parity.check.tuning.php: DEBUG: Array operation paused with some drives still too hot to resume Sep 7 13:55:01 NAS parity.check.tuning.php: DEBUG: -----------MONITOR end------- Sep 7 14:00:01 NAS parity.check.tuning.php: DEBUG: -----------MONITOR start------ Sep 7 14:00:01 NAS parity.check.tuning.php: DEBUG: Parity check appears to be paused Sep 7 14:00:01 NAS parity.check.tuning.php: TESTING: parity temp=39 (settings are: hot=40, cool=37)) Sep 7 14:00:01 NAS parity.check.tuning.php: TESTING: disk1 temp=42 (settings are: hot=40, cool=37)) Sep 7 14:00:01 NAS parity.check.tuning.php: TESTING: disk2 temp=42 (settings are: hot=40, cool=37)) Sep 7 14:00:01 NAS parity.check.tuning.php: DEBUG: array drives=3, hot=2, warm=1, cool=0 Sep 7 14:00:01 NAS parity.check.tuning.php: DEBUG: Array operation paused with some drives still too hot to resume Sep 7 14:00:01 NAS parity.check.tuning.php: DEBUG: -----------MONITOR end------- Sep 7 14:00:01 NAS root: Cache used space threshhold (75) not exceeded. Used Space: 72. Not moving files Sep 7 14:05:01 NAS parity.check.tuning.php: DEBUG: -----------MONITOR start------ Sep 7 14:05:01 NAS parity.check.tuning.php: DEBUG: Parity check appears to be paused Sep 7 14:05:01 NAS parity.check.tuning.php: TESTING: parity temp=39 (settings are: hot=40, cool=37)) Sep 7 14:05:01 NAS parity.check.tuning.php: TESTING: disk1 temp=42 (settings are: hot=40, cool=37)) Sep 7 14:05:01 NAS parity.check.tuning.php: TESTING: disk2 temp=42 (settings are: hot=40, cool=37)) Sep 7 14:05:01 NAS parity.check.tuning.php: DEBUG: array drives=3, hot=2, warm=1, cool=0 Sep 7 14:05:01 NAS parity.check.tuning.php: DEBUG: Array operation paused with some drives still too hot to resume Sep 7 14:05:01 NAS parity.check.tuning.php: DEBUG: -----------MONITOR end------- Sep 7 14:10:01 NAS parity.check.tuning.php: DEBUG: -----------MONITOR start------ Sep 7 14:10:01 NAS parity.check.tuning.php: DEBUG: Parity check appears to be paused Sep 7 14:10:01 NAS parity.check.tuning.php: TESTING: parity temp=39 (settings are: hot=40, cool=37)) Sep 7 14:10:01 NAS parity.check.tuning.php: TESTING: disk1 temp=42 (settings are: hot=40, cool=37)) Sep 7 14:10:01 NAS parity.check.tuning.php: TESTING: disk2 temp=42 (settings are: hot=40, cool=37)) Sep 7 14:10:01 NAS parity.check.tuning.php: DEBUG: array drives=3, hot=2, warm=1, cool=0 Sep 7 14:10:01 NAS parity.check.tuning.php: DEBUG: Array operation paused with some drives still too hot to resume Sep 7 14:10:01 NAS parity.check.tuning.php: DEBUG: -----------MONITOR end------- Sep 7 14:15:01 NAS parity.check.tuning.php: DEBUG: -----------MONITOR start------ Sep 7 14:15:01 NAS parity.check.tuning.php: DEBUG: Parity check appears to be paused Sep 7 14:15:01 NAS parity.check.tuning.php: TESTING: parity temp=37 (settings are: hot=40, cool=37)) Sep 7 14:15:01 NAS parity.check.tuning.php: TESTING: disk1 temp=34 (settings are: hot=40, cool=37)) Sep 7 14:15:01 NAS parity.check.tuning.php: TESTING: disk2 temp=38 (settings are: hot=40, cool=37)) Sep 7 14:15:01 NAS parity.check.tuning.php: DEBUG: array drives=3, hot=0, warm=1, cool=2 Sep 7 14:15:01 NAS parity.check.tuning.php: DEBUG: Array operation paused but drives not cooled enough to resume Sep 7 14:15:01 NAS parity.check.tuning.php: DEBUG: -----------MONITOR end------- Sep 7 14:15:07 NAS autofan: Board temp is 41C, hottest disk is 38C (/dev/sdh), setting fan speed to: 135 (62% @ 1386rpm) Sep 7 14:20:01 NAS parity.check.tuning.php: DEBUG: -----------MONITOR start------ Sep 7 14:20:01 NAS parity.check.tuning.php: DEBUG: Parity check appears to be paused Sep 7 14:20:01 NAS parity.check.tuning.php: TESTING: parity temp=37 (settings are: hot=40, cool=37)) Sep 7 14:20:01 NAS parity.check.tuning.php: TESTING: disk1 temp=34 (settings are: hot=40, cool=37)) Sep 7 14:20:01 NAS parity.check.tuning.php: TESTING: disk2 temp=38 (settings are: hot=40, cool=37)) Sep 7 14:20:01 NAS parity.check.tuning.php: DEBUG: array drives=3, hot=0, warm=1, cool=2 Sep 7 14:20:01 NAS parity.check.tuning.php: DEBUG: Array operation paused but drives not cooled enough to resume Sep 7 14:20:01 NAS parity.check.tuning.php: DEBUG: -----------MONITOR end------- Sep 7 14:25:01 NAS parity.check.tuning.php: DEBUG: -----------MONITOR start------ Sep 7 14:25:01 NAS parity.check.tuning.php: DEBUG: Parity check appears to be paused Sep 7 14:25:01 NAS parity.check.tuning.php: TESTING: parity temp=37 (settings are: hot=40, cool=37)) Sep 7 14:25:01 NAS parity.check.tuning.php: TESTING: disk1 temp=34 (settings are: hot=40, cool=37)) Sep 7 14:25:01 NAS parity.check.tuning.php: TESTING: disk2 temp=38 (settings are: hot=40, cool=37)) Sep 7 14:25:01 NAS parity.check.tuning.php: DEBUG: array drives=3, hot=0, warm=1, cool=2 Sep 7 14:25:01 NAS parity.check.tuning.php: DEBUG: Array operation paused but drives not cooled enough to resume Sep 7 14:25:01 NAS parity.check.tuning.php: DEBUG: -----------MONITOR end------- Sep 7 14:27:40 NAS autofan: Board temp is 40C, hottest disk is 36C (/dev/sdh), setting fan speed to: 105 (48% @ 1117rpm) Sep 7 14:30:01 NAS parity.check.tuning.php: DEBUG: -----------MONITOR start------ Sep 7 14:30:01 NAS parity.check.tuning.php: DEBUG: Parity check appears to be paused Sep 7 14:30:01 NAS parity.check.tuning.php: TESTING: parity temp=37 (settings are: hot=40, cool=37)) Sep 7 14:30:01 NAS parity.check.tuning.php: TESTING: disk1 temp=34 (settings are: hot=40, cool=37)) Sep 7 14:30:01 NAS parity.check.tuning.php: TESTING: disk2 temp=38 (settings are: hot=40, cool=37)) Sep 7 14:30:01 NAS parity.check.tuning.php: DEBUG: array drives=3, hot=0, warm=1, cool=2 Sep 7 14:30:01 NAS parity.check.tuning.php: DEBUG: Array operation paused but drives not cooled enough to resume Sep 7 14:30:01 NAS parity.check.tuning.php: DEBUG: -----------MONITOR end------- Sep 7 14:35:01 NAS parity.check.tuning.php: DEBUG: -----------MONITOR start------ Sep 7 14:35:01 NAS parity.check.tuning.php: DEBUG: Parity check appears to be paused Sep 7 14:35:01 NAS parity.check.tuning.php: TESTING: parity temp=37 (settings are: hot=40, cool=37)) Sep 7 14:35:01 NAS parity.check.tuning.php: TESTING: disk1 temp=34 (settings are: hot=40, cool=37)) Sep 7 14:35:01 NAS parity.check.tuning.php: TESTING: disk2 temp=38 (settings are: hot=40, cool=37)) Sep 7 14:35:01 NAS parity.check.tuning.php: DEBUG: array drives=3, hot=0, warm=1, cool=2 Sep 7 14:35:01 NAS parity.check.tuning.php: DEBUG: Array operation paused but drives not cooled enough to resume Sep 7 14:35:01 NAS parity.check.tuning.php: DEBUG: -----------MONITOR end------- Sep 7 14:40:01 NAS parity.check.tuning.php: DEBUG: -----------MONITOR start------ Sep 7 14:40:01 NAS parity.check.tuning.php: DEBUG: Parity check appears to be paused Sep 7 14:40:01 NAS parity.check.tuning.php: TESTING: parity temp=37 (settings are: hot=40, cool=37)) Sep 7 14:40:01 NAS parity.check.tuning.php: TESTING: disk1 temp=34 (settings are: hot=40, cool=37)) Sep 7 14:40:01 NAS parity.check.tuning.php: TESTING: disk2 temp=38 (settings are: hot=40, cool=37)) Sep 7 14:40:01 NAS parity.check.tuning.php: DEBUG: array drives=3, hot=0, warm=1, cool=2 Sep 7 14:40:01 NAS parity.check.tuning.php: DEBUG: Array operation paused but drives not cooled enough to resume Sep 7 14:40:01 NAS parity.check.tuning.php: DEBUG: -----------MONITOR end------- Sep 7 14:45:01 NAS parity.check.tuning.php: DEBUG: -----------MONITOR start------ Sep 7 14:45:01 NAS parity.check.tuning.php: DEBUG: Parity check appears to be paused Sep 7 14:45:01 NAS parity.check.tuning.php: TESTING: parity temp=37 (settings are: hot=40, cool=37)) Sep 7 14:45:01 NAS parity.check.tuning.php: TESTING: disk1 temp=34 (settings are: hot=40, cool=37)) Sep 7 14:45:01 NAS parity.check.tuning.php: TESTING: disk2 temp=38 (settings are: hot=40, cool=37)) Sep 7 14:45:01 NAS parity.check.tuning.php: DEBUG: array drives=3, hot=0, warm=1, cool=2 Sep 7 14:45:01 NAS parity.check.tuning.php: DEBUG: Array operation paused but drives not cooled enough to resume Sep 7 14:45:01 NAS parity.check.tuning.php: DEBUG: -----------MONITOR end------- Drives all "cool" but check still paused Sep 7 14:50:01 NAS parity.check.tuning.php: DEBUG: -----------MONITOR start------ Sep 7 14:50:01 NAS parity.check.tuning.php: DEBUG: Parity check appears to be paused Sep 7 14:50:01 NAS parity.check.tuning.php: TESTING: parity temp=33 (settings are: hot=40, cool=37)) Sep 7 14:50:01 NAS parity.check.tuning.php: TESTING: disk1 temp=35 (settings are: hot=40, cool=37)) Sep 7 14:50:01 NAS parity.check.tuning.php: TESTING: disk2 temp=35 (settings are: hot=40, cool=37)) Sep 7 14:50:01 NAS parity.check.tuning.php: DEBUG: array drives=3, hot=0, warm=0, cool=3 Sep 7 14:50:01 NAS parity.check.tuning.php: DEBUG: Array operation paused but drives not cooled enough to resume Sep 7 14:50:01 NAS parity.check.tuning.php: DEBUG: -----------MONITOR end------- Mover-tuning settings updated without changing values, I hoped this might jumpstart it, nope Sep 7 14:52:31 NAS ool www[2754]: /usr/local/emhttp/plugins/parity.check.tuning/parity.check.tuning.php 'updatecron' Sep 7 14:52:31 NAS parity.check.tuning.php: DEBUG: -----------UPDATECRON start------ Sep 7 14:52:31 NAS parity.check.tuning.php: DEBUG: created cron entries for running increments Sep 7 14:52:31 NAS parity.check.tuning.php: DEBUG: created cron entry for monitoring disk temperatures Sep 7 14:52:31 NAS parity.check.tuning.php: TESTING: updated cron settings are in /boot/config/plugins/parity.check.tuning/parity.check.tuning.cron Sep 7 14:52:31 NAS parity.check.tuning.php: DEBUG: -----------UPDATECRON end------- Sep 7 14:55:01 NAS parity.check.tuning.php: DEBUG: -----------MONITOR start------ Sep 7 14:55:01 NAS parity.check.tuning.php: DEBUG: Parity check appears to be paused Sep 7 14:55:01 NAS parity.check.tuning.php: TESTING: parity temp=33 (settings are: hot=40, cool=37)) Sep 7 14:55:01 NAS parity.check.tuning.php: TESTING: disk1 temp=35 (settings are: hot=40, cool=37)) Sep 7 14:55:01 NAS parity.check.tuning.php: TESTING: disk2 temp=35 (settings are: hot=40, cool=37)) Sep 7 14:55:01 NAS parity.check.tuning.php: DEBUG: array drives=3, hot=0, warm=0, cool=3 Sep 7 14:55:01 NAS parity.check.tuning.php: DEBUG: Array operation paused but drives not cooled enough to resume Sep 7 14:55:01 NAS parity.check.tuning.php: DEBUG: -----------MONITOR end------- Sep 7 15:00:01 NAS parity.check.tuning.php: DEBUG: -----------MONITOR start------ Sep 7 15:00:01 NAS parity.check.tuning.php: DEBUG: Parity check appears to be paused Sep 7 15:00:01 NAS parity.check.tuning.php: TESTING: parity temp=33 (settings are: hot=40, cool=37)) Sep 7 15:00:01 NAS parity.check.tuning.php: TESTING: disk1 temp=35 (settings are: hot=40, cool=37)) Sep 7 15:00:01 NAS parity.check.tuning.php: TESTING: disk2 temp=35 (settings are: hot=40, cool=37)) Sep 7 15:00:01 NAS parity.check.tuning.php: DEBUG: array drives=3, hot=0, warm=0, cool=3 Sep 7 15:00:01 NAS parity.check.tuning.php: DEBUG: Array operation paused but drives not cooled enough to resume Sep 7 15:00:01 NAS parity.check.tuning.php: DEBUG: -----------MONITOR end------- Mover-tuning settings updated to lower "cool" by 2 (difference of 5 now between hot and cool), check still doesn't resume: Sep 7 15:02:52 NAS ool www[19347]: /usr/local/emhttp/plugins/parity.check.tuning/parity.check.tuning.php 'updatecron' Sep 7 15:02:52 NAS parity.check.tuning.php: DEBUG: -----------UPDATECRON start------ Sep 7 15:02:52 NAS parity.check.tuning.php: DEBUG: created cron entries for running increments Sep 7 15:02:52 NAS parity.check.tuning.php: DEBUG: created cron entry for monitoring disk temperatures Sep 7 15:02:52 NAS parity.check.tuning.php: TESTING: updated cron settings are in /boot/config/plugins/parity.check.tuning/parity.check.tuning.cron Sep 7 15:02:52 NAS parity.check.tuning.php: DEBUG: -----------UPDATECRON end------- Sep 7 15:05:01 NAS parity.check.tuning.php: DEBUG: -----------MONITOR start------ Sep 7 15:05:01 NAS parity.check.tuning.php: DEBUG: Parity check appears to be paused Sep 7 15:05:01 NAS parity.check.tuning.php: TESTING: parity temp=33 (settings are: hot=40, cool=35)) Sep 7 15:05:01 NAS parity.check.tuning.php: TESTING: disk1 temp=35 (settings are: hot=40, cool=35)) Sep 7 15:05:01 NAS parity.check.tuning.php: TESTING: disk2 temp=35 (settings are: hot=40, cool=35)) Sep 7 15:05:01 NAS parity.check.tuning.php: DEBUG: array drives=3, hot=0, warm=0, cool=3 Sep 7 15:05:01 NAS parity.check.tuning.php: DEBUG: Array operation paused but drives not cooled enough to resume Sep 7 15:05:01 NAS parity.check.tuning.php: DEBUG: -----------MONITOR end-------

I haven't tested enough to be certain but I think if the difference between hot pause and cool resume isn't sufficient it won't resume. With Hot pause: 2 below Cool resume: 5 below (Difference of 3) It didn't resume With Hot pause: 2 below Cool resume: 7 below (Difference of 5) It did resume But it's possible I misinterpreted and something else caused the resume failure.

You need to delete the port mappings from the Jdownloader container and add them instead to the qbittorrentvpn container, instructions here: https://www.reddit.com/r/unRAID/comments/ejeo20/how_to_pass_any_docker_container_through_a_vpn_on/

I use Duplicacy for local backups (network share and USB.) I recently restored two ~60GB VMs as a test, one from each source. Worked fine although you can't navigate away from the restore screen or it'll stop. Other than that and the hassle of the initial setup it's worked fairly well. Add the password as a container variable or automated backups after a container update will fail pending manual log in.

I got around it using the M.2 slot (mine was limited to Key A+E)

Great resource, I hadn't seen that before. (The GCM cipher significantly improved my download speed.) One question after reading it re: Privoxy for Sonarr, etc: Does the proxy setup offer some advantage over setting qbittorrent as the container network for Sonarr, etc. (per Part 2 here)?

I just updated and tested. (1) and (3) are fixed but re: (2) it looks like PAUSE (correctly) references the highest temperature disk but RESUME references the lowest temperature disk (it should be highest). Still, plenty good enough. Thank you. Aug 1 12:20:01 NAS parity.check.tuning.php: DEBUG: -----------MONITOR start------ Aug 1 12:20:01 NAS parity.check.tuning.php: TESTING: parity temp=38 (settings are: hot=40, cool=35)) Aug 1 12:20:01 NAS parity.check.tuning.php: TESTING: disk1 temp=40 (settings are: hot=40, cool=35)) Aug 1 12:20:01 NAS parity.check.tuning.php: TESTING: disk2 temp=41 (settings are: hot=40, cool=35)) Aug 1 12:20:01 NAS parity.check.tuning.php: DEBUG: array drives=3, hot=2, warm=1, cool=0 Aug 1 12:20:01 NAS parity.check.tuning.php: Paused Non-Correcting Parity Check (86.5% completed) : Following drives overheated: 40 41 Aug 1 12:20:01 NAS parity.check.tuning.php: DEBUG: written PAUSE (HOT) record to /boot/config/plugins/parity.check.tuning/parity.check.tuning.progress Aug 1 12:20:01 NAS parity.check.tuning.php: DEBUG: -----------MDCMD start------ Aug 1 12:20:01 NAS parity.check.tuning.php: DEBUG: detected that mdcmd had been called from sh with command mdcmd nocheck PAUSE Aug 1 12:20:01 NAS parity.check.tuning.php: DEBUG: -----------MDCMD end------- Aug 1 12:20:01 NAS kernel: mdcmd (169): nocheck PAUSE Aug 1 12:20:01 NAS kernel: Aug 1 12:20:02 NAS kernel: md: recovery thread: exit status: -4 Aug 1 12:20:02 NAS parity.check.tuning.php: TESTING: Heat notifications disabled so Pause Following drives overheated: 40 41 not sent Aug 1 12:20:02 NAS parity.check.tuning.php: DEBUG: -----------MONITOR end------- Aug 1 12:35:01 NAS parity.check.tuning.php: DEBUG: -----------MONITOR start------ Aug 1 12:35:01 NAS parity.check.tuning.php: DEBUG: Parity check appears to be paused Aug 1 12:35:01 NAS parity.check.tuning.php: TESTING: parity temp=38 (settings are: hot=40, cool=35)) Aug 1 12:35:01 NAS parity.check.tuning.php: TESTING: disk1 temp=40 (settings are: hot=40, cool=35)) Aug 1 12:35:01 NAS parity.check.tuning.php: TESTING: disk2 temp=41 (settings are: hot=40, cool=35)) Aug 1 12:35:01 NAS parity.check.tuning.php: DEBUG: array drives=3, hot=2, warm=1, cool=0 Aug 1 12:35:01 NAS parity.check.tuning.php: DEBUG: Array operation paused but drives not cooled enough to resume Aug 1 12:35:01 NAS parity.check.tuning.php: DEBUG: -----------MONITOR end------- Aug 1 12:40:02 NAS parity.check.tuning.php: DEBUG: -----------MONITOR start------ Aug 1 12:40:02 NAS parity.check.tuning.php: DEBUG: Parity check appears to be paused Aug 1 12:40:02 NAS parity.check.tuning.php: TESTING: parity temp=36 (settings are: hot=40, cool=35)) Aug 1 12:40:02 NAS parity.check.tuning.php: TESTING: disk1 temp=34 (settings are: hot=40, cool=35)) Aug 1 12:40:02 NAS parity.check.tuning.php: TESTING: disk2 temp=38 (settings are: hot=40, cool=35)) Aug 1 12:40:02 NAS parity.check.tuning.php: DEBUG: array drives=3, hot=0, warm=2, cool=1 Aug 1 12:40:02 NAS parity.check.tuning.php: Resumed Non-Correcting Parity Check (86.5% completed) as drives now cooled down Aug 1 12:40:02 NAS parity.check.tuning.php: DEBUG: written RESUME (COOL) record to /boot/config/plugins/parity.check.tuning/parity.check.tuning.progress Aug 1 12:40:02 NAS parity.check.tuning.php: DEBUG: -----------MDCMD start------ Aug 1 12:40:02 NAS parity.check.tuning.php: DEBUG: detected that mdcmd had been called from sh with command mdcmd check RESUME Aug 1 12:40:02 NAS parity.check.tuning.php: DEBUG: -----------MDCMD end------- Aug 1 12:40:02 NAS kernel: mdcmd (170): check RESUME Aug 1 12:40:02 NAS kernel: Aug 1 12:40:02 NAS kernel: md: recovery thread: check P ... Aug 1 12:40:02 NAS parity.check.tuning.php: TESTING: Heat notifications disabled so Resume Drives cooled down not sent Aug 1 12:40:02 NAS parity.check.tuning.php: DEBUG: -----------MONITOR end-------

Happy to. Attached with identifying information anonymized (I think.) If I had a nickel... Ha! Yeah I realized I confused you two and edited my post but not in time (my apologies.) disks.ini.txt

First, thanks for this very handy plugin. I think there are minor bugs in the temperature-pausing code: The assigned-slots check (which I believe you just added) reports an incorrect total. I have 3 array disks, 2 cache disks and 4 Unassigned Devices disks. The plugin shows 4 total (I assume array) disks Parity check is paused with hot=1, warm=2, cool=1 and resumed with hot=1, warm=1, cool=2. Seems like pause/resume should be based on hot alone The PAUSE debug reports the label of the overheated drive as "temp" Aug 1 07:50:01 NAS parity.check.tuning.php: DEBUG: -----------MONITOR start------ Aug 1 07:50:01 NAS parity.check.tuning.php: DEBUG: Parity check appears to be paused Aug 1 07:50:01 NAS parity.check.tuning.php: DEBUG: drives=4, hot=1, warm=2, cool=1 Aug 1 07:50:01 NAS parity.check.tuning.php: Resumed Non-Correcting Parity Check (57.8% completed) as drives now cooled down Aug 1 07:50:01 NAS parity.check.tuning.php: DEBUG: written RESUME (COOL) record to /boot/config/plugins/parity.check.tuning/parity.check.tuning.progress Aug 1 07:50:01 NAS parity.check.tuning.php: DEBUG: -----------MDCMD start------ Aug 1 07:50:01 NAS parity.check.tuning.php: DEBUG: detected that mdcmd had been called from sh with command mdcmd check RESUME Aug 1 07:50:01 NAS parity.check.tuning.php: DEBUG: -----------MDCMD end------- Aug 1 07:50:01 NAS kernel: mdcmd (162): check RESUME Aug 1 07:50:01 NAS kernel: Aug 1 07:50:01 NAS kernel: md: recovery thread: check P ... Aug 1 07:50:01 NAS parity.check.tuning.php: DEBUG: -----------MONITOR end------- Aug 1 07:55:01 NAS parity.check.tuning.php: DEBUG: -----------MONITOR start------ Aug 1 07:55:01 NAS parity.check.tuning.php: DEBUG: drives=4, hot=1, warm=1, cool=2 Aug 1 07:55:01 NAS parity.check.tuning.php: Paused Non-Correcting Parity Check (58.4% completed) : Following drives overheated: temp Aug 1 07:55:01 NAS parity.check.tuning.php: DEBUG: written PAUSE (HOT) record to /boot/config/plugins/parity.check.tuning/parity.check.tuning.progress Aug 1 07:55:01 NAS parity.check.tuning.php: DEBUG: -----------MDCMD start------ Aug 1 07:55:01 NAS parity.check.tuning.php: DEBUG: detected that mdcmd had been called from sh with command mdcmd nocheck PAUSE Aug 1 07:55:01 NAS parity.check.tuning.php: DEBUG: -----------MDCMD end------- Aug 1 07:55:01 NAS kernel: mdcmd (163): nocheck PAUSE Aug 1 07:55:01 NAS kernel: Aug 1 07:55:01 NAS kernel: md: recovery thread: exit status: -4 Aug 1 07:55:01 NAS parity.check.tuning.php: DEBUG: -----------MONITOR end-------

Just to follow up on my earlier post re: configuring the plugin to only keep 1 weekly backup, I hacked the code to accept "6" in the Number of days to keep backups field (7 was the lowest non-zero limit) and it's working as expected.

I've got PCI passthrough working for a USB controller (Renesas uPD720202) with the following XML. Mojave recognizes it but performance is terrible, it can't even keep up with mouse movements. Is there a known solution or path to investigate? <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </source> <alias name='hostdev1'/> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </hostdev>

Rebuild-DNDC will automatically restart the main container (qBittorrent) as well so it'd help if you lose connectivity but it looks like you haven't since the curl command returns your VPN IP. I don't see any inactivity timeouts in my log just a series of successful curl commands to portchecker.co Sorry I can't help more.

Next time it happens test container connectivity by running something like: docker exec -it vpn curl ipinfo.io I renamed my container vpn. Substitute whatever name you have in the command above. If everything's working it should return your VPN IP and additional details. To test the connection and restart containers automatically you can run Rebuild-DNDC available in the Community Apps. Detailed description here: https://github.com/elmerfdz/rebuild-dndc

Smart caching. Pull frequently-accessed files into cache dynamically. Saves power, wear and tear on the array, reduces noise (if your fans vary with HDD temps.)

I believe it supports encrypted backups. Another one to look at is duplicati, also in CA – more user friendly but much slower backups to attached USB and network SMB.

And yes it supports schedules. There's a bit of a learning curve though. Took me a couple weeks to get it 100%.

It does versioned backup so there would be an earlier version WITH the deleted file and a later version WITHOUT it. You can configure how many backups to keep and for how long. Maybe that's more complex than you're looking for.

I'm using the Duplicacy docker (which has a GUI) to backup to a Time Capsule which I mount as an unassigned device over SMB. So far so good. An RPi4 with attached USB drive shared over SMB should work at least as well.

+1 Adding "Automatic" as a cache option to populate it algorithmically based on access frequency and last-access-time would be great. It'd even make sense as the default because that matches new users' expectations. There should be a default threshold capacity (maybe configurable) or a "reserved" size because you don't want the cache drive 99% full.

Great plugin. I'm having one problem, maybe a misconfiguration on my part. I have two VMs I backup weekly: Both have the same problem: the primary vdisk from the last backup isn't deleted so there are always two, previous and current. Debian MacOS I've tried changing number of days to 6 (thinking it might be a timing issue) but the plugin prevents it: I've tried using number of backups instead of date but the plugin prevents that as well: Anyone know where I'm going wrong?

I'm stuck on the same "single USB controller" with my j5005. I've ordered this Key A-E to USB Extension Card as a potential work around but I won't get it for another month. I'll report back when I've tested it.

I have a USB HDD in unassigned devices which I use for backups. The drive won't spin down for whatever reason, mounted or not. My solution was a modified version of this script that I have User Scripts run every hour. It takes a list of drives, checks for activity and spins them down if they're inactive and spun up. I thought I'd share it. NOTE: The green "led" in Unassigned Devices stays green even when the drive's spun down, I don't know how or if it detects power status. #!/bin/bash # This script looks for recent disk access, and if nothing has changed, puts /dev/disk/by-id/${drive} into spindown mode. # # Set your drive identifiers (listed in /dev/disk/by-id/) ignoring characters after the last "-" # e.g. listing: usb-WD_My_Passport_25E2_75831314363630505A37-0:0 # becomes: usb-WD_My_Passport_25E2_75831314363630505A37 drives=( "<DRIVE_IDENTIFIER_1>" "<DRIVE_IDENTIFIER_2>" ) # spindown delay in minutes SPINDOWN_DELAY=30 # Uncomment to enable debug mode #DEBUG=true # Set the directory where the status files will be stored, # /tmp/ is a fine default STATUS_DIR="/tmp" current=`date` # create status_dir if it doesn't exist mkdir -p ${STATUS_DIR} do_device() { local device_id=$1 device=`ls -l /dev/disk/by-id/ | grep ${device_id} | head -1 | tail -c4` filename="${STATUS_DIR}/diskaccess-${device_id}.status" is_awake=`smartctl --nocheck standby -i /dev/${device} | grep 'Power mode is' | egrep -c 'ACTIVE|IDLE'` if [ "${is_awake}" == "1" ]; then if [ "$DEBUG" = true ]; then echo "${device} is awake" fi stat_new=$(grep "${device}1 " /proc/diskstats | tr -dc "[:digit:]") if [ ! -f "${filename}" ]; then echo ${current} "- ${filename} file does not exist; creating it now." echo ${stat_new} > ${filename} else stat_old=`cat ${filename} | tr -dc "[:digit:]"` # calculate minutes since last update to see if we should sleep current_time=$(date +%s) last_mod=$(stat ${filename} -c %Y) seconds_ago=$(expr $current_time - $last_mod) minutes_ago=$(expr $seconds_ago / 60) if [ "$DEBUG" = true ]; then echo "${device} old stat: ${stat_old}" echo "${device} new stat: ${stat_new}" echo "${device} new stat modified ${minutes_ago} minutes ago" fi if [ "${stat_old}" == "${stat_new}" ]; then if [ $minutes_ago -ge $SPINDOWN_DELAY ]; then echo ${current} "- Drive /dev/${device} is awake and hasn't been used in ${minutes_ago} minutes; spinning down" hdparm -y /dev/${device} > /dev/null 2>&1 else echo ${current} "- Drive /dev/${device} was last used ${minutes_ago} minutes ago, less than spindown setting ($SPINDOWN_DELAY)" fi else echo ${current} "- Drive /dev/${device} has been used..." echo ${stat_new} > ${filename} fi fi else if [ "$DEBUG" = true ]; then echo "${device} is asleep" fi fi } for device_id in ${drives[*]} do do_device ${device_id} done

I'm in the same boat. External disks work consistently, iPhone not at all. Unfortunately my board has a single integrated USB controller and no free PCIe slot so the "pass a controller" solution doesn't work. I tried VirtualHere (USB over ethernet) but apparently iPhone sync with a Mac host requires a Mac client. That didn't work in my case but may work for others.