I take it back. This could be the issue. 

Normally, the Apply button is grayed out and always stays grayed out, no matter the schedule option selected (daily, monthly, etc). However, using the Web Developer extension in Chrome to enable form fields, the Apply button does become available. After clicking on it, the below log entries appear in /var/log/syslog

Sep 18 11:08:54 unraid root: error: /update.php: missing csrf_token
Sep 18 11:09:03 unraid root: error: /update.php: missing csrf_token

Quote

If updating your plugins does not solve your issue, then post in the relevant support thread for the plugin.  There will be hints on the log line as to which plugin generated the error.

Not too sure where to go from here. Is the Scheduler considered a plugin which needs to be updated since the alert is triggered from there?

 

unraid-diagnostics-20200918-1111.zip

Edited September 18, 20205 yr by MrLinux

Maybe this might help.

 

Nothing to do with Safe Mode etc. (Makes no difference to the UI)

 

Scheduler:600 Uncaught TypeError: Cannot read property 'value' of undefined
    at presetMover (Scheduler:600)
    at HTMLDocument.<anonymous> (Scheduler:585)
    at i (dynamix.js?v=1570392778:4)
    at Object.fireWith [as resolveWith] (dynamix.js?v=1570392778:4)
    at Function.ready (dynamix.js?v=1570392778:4)
    at HTMLDocument.J (dynamix.js?v=1570392778:4)
presetMover @ Scheduler:600
(anonymous) @ Scheduler:585
i @ dynamix.js?v=1570392778:4
fireWith @ dynamix.js?v=1570392778:4
ready @ dynamix.js?v=1570392778:4
J @ dynamix.js?v=1570392778:4

 

Note: I don't use a Cache Drive as a comparison.

 

Edited September 18, 20205 yr by Splash

Maybe this might help.
 
Nothing to do with Safe Mode etc. (Makes no difference to the UI)
 

Scheduler:600 Uncaught TypeError: Cannot read property 'value' of undefined    at presetMover (Scheduler:600)    at HTMLDocument. (Scheduler:585)    at i (dynamix.js?v=1570392778:4)    at Object.fireWith [as resolveWith] (dynamix.js?v=1570392778:4)    at Function.ready (dynamix.js?v=1570392778:4)    at HTMLDocument.J (dynamix.js?v=1570392778:4)presetMover @ Scheduler:600(anonymous) @ Scheduler:585i @ dynamix.js?v=1570392778:4fireWith @ dynamix.js?v=1570392778:4ready @ dynamix.js?v=1570392778:4J @ dynamix.js?v=1570392778:4

 

Does this mean it is a 6.9b25 issue?


Sent from my iPhone using Tapatalk

2 minutes ago, MrLinux said:

Does this mean it is a 6.9b25 issue?


Sent from my iPhone using Tapatalk

Dont think so - 

 

 

Ive tested the above setting using Microsoft Edge, Chrome and Brave web browsers all with no difference.

Edited September 18, 20205 yr by Splash

FWIW, I don't have a cache drive either. Plan to install a raid 1 pool this weekend. 

I just installed my Raid 1 Cache Pool (2 x 1TB NVMe SSD) and can now schedule my parity checks.

That suggests a bug, did you start with a clean beta25 install?

8 minutes ago, JorgeB said:

That suggests a bug, did you start with a clean beta25 install?

Yes. This was my very first time using unRAID.

 

FWIW, I did click the gear from the Dashboard to go to the scheduler when it mentioned parity check wasn't scheduled. See screenshot. I didn't notice this before installing the Cache Pool, not to say it wasn't there all along. Before, I would get to the scheduler via Settings > Scheduler. Both methods are allowing me to set a schedule now, even if I disable Parity Check and go back in either way.

 

Before

 

After

Edited September 21, 20205 yr by MrLinux

Thanks, confirmed it's a bug:

 

@JorgeB, Dumb question. How do I mark you post as the solution?

We can't do that on this forum, we can only recommend a post so it appears at the top, but only mods can do that, though it's really not a solution in this case, but I'll do it in case another user has the same issue before it's fixed and finds this thread.

On 9/21/2020 at 6:45 PM, MrLinux said:

I just installed my Raid 1 Cache Pool (2 x 1TB NVMe SSD) and can now schedule my parity checks.

I just did this too, and thought i'd come back and comment the same 

https://github.com/limetech/webgui/pull/748

 

Fixed for next release

Awesome thank you!