I pulled out a 500gb ssd from my array (i wasn't using it, it was more so sitting there idle) and i replaced it with an 8tb WD drive.

 

Parity Sync/Data Rebuild keeps pausing and resuming on its own some time later or else at times i have to keep going back and resuming it manually from the "Main/Array Operation" section.

 

I've noticed the disk hitting at or near 50 degrees celcius during the sync. I'll be rearranging all the drives in the case in a few days to help with cooling (its a Fractal 7XL so i have plenty of space)

 

...but for my curiosity, are the temps causing the Parity Sync to pause? Is that a safety feature?

 

voyager-diagnostics-20201114-0220.zip

Edited November 14, 20205 yr by CatMilk

1 hour ago, CatMilk said:

temps causing the Parity Sync to pause? Is that a safety feature?

It's a feature of the Parity Check Tuning plugin you have installed.

 

1 hour ago, CatMilk said:

rearranging all the drives in the case in a few days to help with cooling

You really need to

If you do not want the Parity Check Tuning plugin to pause array operations when disks temperatures exceed the thresholds you set then simply disable that option in the settings for the plugin (or set the temperature thresholds higher),    If you had notifications enabled and had set the option to use them in the plugin settings you should have been getting one from the plugin whenever it paused or resumed the array  action.

 

In addition your syslog is continually being flooded with messages of the form:

Nov 13 18:15:46 Voyager kernel: tun: unexpected GSO type: 0x0, gso_size 27, hdr_len 81
Nov 13 18:15:46 Voyager kernel: tun: de df 82 60 02 c9 f0 2b eb c3 f1 76 a5 61 49 d7  ...`...+...v.aI.
Nov 13 18:15:46 Voyager kernel: tun: df 72 12 e9 52 db f1 a3 d7 bd 9b 54 9c 0d f4 c8  .r..R......T....
Nov 13 18:15:46 Voyager kernel: tun: 2a 9d 1f 10 2e f5 53 ba 59 37 c4 ad 12 27 d4 6b  *.....S.Y7...'.k
Nov 13 18:15:46 Voyager kernel: tun: 19 66 cc 4d 57 cd 80 b8 4a 9d 00 91 3c 1f 3d 7e  .f.MW...J...<.=~

which you want to get resolved as it makes the syslog hard to read.

9 minutes ago, itimpi said:

If you do not want the Parity Check Tuning plugin to pause array operations when disks temperatures exceed the thresholds you set then simply disable that option in the settings for the plugin (or set the temperature thresholds higher),    If you had notifications enabled and had set the option to use them in the plugin settings you should have been getting one from the plugin whenever it paused or resumed the array  action.

 

In addition your syslog is continually being flooded with messages of the form:

Nov 13 18:15:46 Voyager kernel: tun: unexpected GSO type: 0x0, gso_size 27, hdr_len 81
Nov 13 18:15:46 Voyager kernel: tun: de df 82 60 02 c9 f0 2b eb c3 f1 76 a5 61 49 d7  ...`...+...v.aI.
Nov 13 18:15:46 Voyager kernel: tun: df 72 12 e9 52 db f1 a3 d7 bd 9b 54 9c 0d f4 c8  .r..R......T....
Nov 13 18:15:46 Voyager kernel: tun: 2a 9d 1f 10 2e f5 53 ba 59 37 c4 ad 12 27 d4 6b  *.....S.Y7...'.k
Nov 13 18:15:46 Voyager kernel: tun: 19 66 cc 4d 57 cd 80 b8 4a 9d 00 91 3c 1f 3d 7e  .f.MW...J...<.=~

which you want to get resolved as it makes the syslog hard to read.

Thanks for all the replies folks & I'll get those flooding logs sorted.