February 17, 201511 yr I searched the Version 6 area for a previous Defect Report on this, but did not find one. unRAID OS Version: 6.0.beta10a Description: In the Mover Settings there are HH and MM values that can be specified for the time of day the Mover runs. MM values go from 00 to 55 in steps of 5. HH values go from 01 to 23 in steps of 1. Thus there does not seem to be a way to specify a time of 00:xx. How to reproduce: Click on the Settings tab, then under Mover Settings, Time of day, click on the drop-down menu for HH. Expected results: HH values should range from 00 to 23. Actual results: HH values range from 01 to 23. Other information: None. This is in no way a show-stopper for me (on my 6th unRAID server build). Just passing this on to help improve an already great system.
February 17, 201511 yr Author Upgraded three of my servers to 6.0-beta13 . . . defect is indeed gone in that version. Guess I should check for a new release before submitting a Defect Report. Thanks again for your help eschultz.
February 19, 201511 yr Author Hmmm. My Parity Check times went up from just under 10 hours to just over 11 hours after the upgrade. There was *some* other activity but certainly not an hours worth. Between my last Parity Check and the upgrade I also added a Cache drive. I'm running another Parity Check, without the Cache drive, and no other activity, to get another data point. If it's still much more than 10 hours, I'll downgrade back to 6.0-beta10a and run it again to be more sure that *just* the version change is responsible for the performance difference. 16 x 4TB drive array on the server in question by the way.
February 19, 201511 yr Author Apologies if my posts are cluttering this Defect Report; I'm hesitant to start a new Defect Report when I'm not sure there's a defect. But it does look like significant disk throughput was lost between 6.0-beta12 and 6.0-beta13. In fact I see that the beta13 download is no longer on the LimeTech Download page. I can tell by the reported "Estimated speed" that I'm running Parity Checks more slowly; seeing low 120MB/s initially on my primary server when I usually see ~135MB/s initially. For additional experimentation I'm trying Parity Checks on my backup server (20 x 3TB). With beta13 I'm only seeing low 40MB/s Parity Check speeds, with beta12 it's in the low 60MB/s range. With beta10 I routinely saw full-run averages of 67.xMB/s; will try going back to that next to make sure that's still the case.
February 19, 201511 yr Author I've confirmed that I still get high 60MB/s Parity Check speeds (just saw 68.9MB/s about 10 minutes in) on my backup server (20 x 3TB) with 6.0-beta10a, but only low 60MB/s speeds (61-62MB/s) with beta12 and only low 40MB/s speeds with beta13. If I had a beta11 release I could check that too, if it would help get to the bottom of this problem.
Archived
This topic is now archived and is closed to further replies.