When trying to schedule my parity check, I cannot "Apply" it after changing it from Disabled to Monthly. In other threads, it was suggestged to enable/disable notifications. I did this but doesn't seem to work. I did it by flipping detailed/summary and unchecking all notification options. Maybe I didn't do it right?

 

unraid-diagnostics-20200912-1307.zip

 

[Solution]

Scheduling became available after installing and setting up my RAID1 Cache pool (2 x 1TB NVMe SSD). Maybe this is a bug in 6.9.0b25?

Edited September 21, 20205 yr by MrLinux
Added solution

Lots of this in syslog:

Sep 12 12:41:37 unraid kernel: traps: node[18277] trap invalid opcode ip:561baad9070f sp:7fff2093b428 error:0 in node[561baad8c000+77b000]
Sep 12 12:41:39 unraid kernel: traps: node[18343] trap invalid opcode ip:555bf6e6370f sp:7ffdf4287d78 error:0 in node[555bf6e5f000+77b000]
Sep 12 12:41:40 unraid kernel: traps: node[18368] trap invalid opcode ip:559dd34a670f sp:7ffcb4b7c288 error:0 in node[559dd34a2000+77b000]
Sep 12 12:41:43 unraid kernel: traps: node[18431] trap invalid opcode ip:55c31874e70f sp:7ffd845efdf8 error:0 in node[55c31874a000+77b000]

 

Have you done memtest lately?

5 minutes ago, trurl said:

Lots of this in syslog:

Sep 12 12:41:37 unraid kernel: traps: node[18277] trap invalid opcode ip:561baad9070f sp:7fff2093b428 error:0 in node[561baad8c000+77b000]
Sep 12 12:41:39 unraid kernel: traps: node[18343] trap invalid opcode ip:555bf6e6370f sp:7ffdf4287d78 error:0 in node[555bf6e5f000+77b000]
Sep 12 12:41:40 unraid kernel: traps: node[18368] trap invalid opcode ip:559dd34a670f sp:7ffcb4b7c288 error:0 in node[559dd34a2000+77b000]
Sep 12 12:41:43 unraid kernel: traps: node[18431] trap invalid opcode ip:55c31874e70f sp:7ffd845efdf8 error:0 in node[55c31874a000+77b000]

 

Have you done memtest lately?

Yes. I just built this box about a week ago with all new parts and did a successful memtest before installing unRAID.

 

Would memory issues prevent the scheduler from saving?

I can try to run another memtest to see if that can help.

Edited September 12, 20205 yr by MrLinux

Found that those errors were coming from grafana. These errors went away after I restarted the docke and fixed some port conflicts in other dockers. 

Sep 12 12:41:37 unraid kernel: traps: node[18277] trap invalid opcode ip:561baad9070f sp:7fff2093b428 error:0 in node[561baad8c000+77b000]
Sep 12 12:41:39 unraid kernel: traps: node[18343] trap invalid opcode ip:555bf6e6370f sp:7ffdf4287d78 error:0 in node[555bf6e5f000+77b000]
Sep 12 12:41:40 unraid kernel: traps: node[18368] trap invalid opcode ip:559dd34a670f sp:7ffcb4b7c288 error:0 in node[559dd34a2000+77b000]

 

post new diagnostics

Thanks. Attached

unraid-diagnostics-20200913-1335.zip

Have you tried after booting in SAFE mode?

Have you tried after booting in SAFE mode?

Not yet. Will that fix the issue or I have to always go to safe mode to set the schedule?


Sent from my iPhone using Tapatalk

Just trying to see if something about one of your plugins might be causing this.

Tried it in safe mode and "Apply" still isn't activating when switching from Disabled to Monthly.

 

Are you setting the Day of the Month and Time of the Day fields?

6 minutes ago, trurl said:

Are you setting the Day of the Month and Time of the Day fields?

Those fields are disabled

No clue. Maybe @bonienl will have an idea.

Post new diagnostics from SAFE mode.

https://imgur.com/a/E9nJb4c - Short video of the user experience (normal mode). I'll get another diagnostics in safe mode

Safe Mode Diag attached. Does it matter if I have the array started or not? It wasn't started when I made this diagnostics.

 

Thanks all for the help.

unraid-diagnostics-20200914-1010-safe-mode.zip

Edited September 14, 20205 yr by MrLinux

Does the parity scheduler act the same in safe mode? How about with a different browser? Different PC?

1 hour ago, jonathanm said:

Does the parity scheduler act the same in safe mode? How about with a different browser? Different PC?

Yes, same behavior in both normal and safe mode. 

Yes, different browsers: Chrome and Safari. Safari has no extensions and Chrome was tested in Incognito mode as well. Also tested on my iPhone with the same behavior. 

 

This is also a fairly fresh install (less than a week old). Not sure if it's a bug of 6.9b25. I have to use this version since it as the drivers for my motherboard's 2.5GBit ethernet adapter.

Edited September 14, 20205 yr by MrLinux

Can you post the contents of /config/plugins/dynamix.cfg from the flash drive?

root@unraid:/boot/config/plugins/dynamix# cat dynamix.cfg
[notify]
entity="0"
normal="0"
warning="0"
alert="0"
unraid="0"
plugin="0"
docker_notify="0"
language_notify="0"
report="0"
display="0"
date="d-m-Y"
time="h:i A"
position="top-right"
path="/tmp/notifications"
system="*/1 * * * *"
unraidos="11 0 * * *"
version="10 0 * * *"
docker_update="10 0 * * *"
language_update="10 0 * * *"
status="20 0 * * *"
[display]
warning="70"
critical="90"
hot="45"
max="55"

 

Try renaming the file to something else.  Reboot and then see if it'll let you change the schedule

No dice. Not sure if it was expected, but the file didn't re-recreate. 

 

root@unraid:/boot/config/plugins/dynamix# cat dynamix.cfg
cat: dynamix.cfg: No such file or directory
root@unraid:/boot/config/plugins/dynamix# uptime
 13:02:16 up 17 min,  1 user,  load average: 0.13, 0.41, 0.78

 

I am receiving the same issue with the scheduler. I am able to change the drop down, but the apply button remains grayed out. Selecting done, ignores the changes.

 

Verison: 6.9.0-beta25 2020-07-12

 

Logs:

Sep 18 17:01:31 UnRaid root: error: /update.php: missing csrf_token
Sep 18 17:06:12 UnRaid root: error: /update.php: missing csrf_token
Sep 18 17:06:25 UnRaid root: error: /update.php: missing csrf_token
Sep 18 17:07:17 UnRaid root: error: /update.php: missing csrf_token

 

Related to : 

 

 

Edited September 18, 20205 yr by Splash
Updated Information

2 hours ago, Splash said:

Sep 18 17:01:31 UnRaid root: error: /update.php: missing csrf_token

 

Unfortunately, this doesn't seem to be happening on my system. It still doesn't work in Safe Mode.

root@unraid:/# grep -i CSRF /var/log/syslog
root@unraid:/#