Problem in 6.9.4 - Unable to schedule volume actions at 2AM

[x219c]

Hey everyone... I have a bug report.

I updated my production NAS to 6.9.4 and am unable to schedule volume actions (scrubs, etc) for 2 AM. Every time I do, I click apply, then OK, and it shows the schedule as 2PM. I can't put the beta on this machine to test for the same problem. 

More detail:

Machine: RN516

I am scheduling these items to happen monthly on a day number. So, every month on the 2nd at 2AM, for example. I am in CST. I have deleted the scheduled items and attempted to readd them. Tried different ways to submit (just clicking ok without apply). I have tried setting it as 2PM, thinking it might just be set opposite. This is not just a display problem, the tasks begin at 2PM, as indicated in the schedule.

Maybe unrelated: I attempted to edit 4 schedules at a time, which crashed the web interface and required a reboot.

Thanks.

[Leia · Accepted solution]

@x219c, @StephenB, @steveoelliott, @scravatt, @bedlam1

This bug has been fixed on 6.9.5 beta1. You can download the firmware from the urls in this post. https://community.netgear.com/t5/ReadyNAS-Beta-Release/ReadyNASOS-6-9-5-T7-Beta-1/td-p/1656915

[StephenB]

I just checked this, and I am seeing the same issue.  The only AM time that is retained is 12 AM.  All the others are converted to PM.

[bedlam1]

This looks similar to a problem I had LINK

Have you tried selecting 24 hour format perhaps

[scravatt]

---

I have the exact same issue. Certain AM timesetting on a volume schedule jumps to PM when I click apply om the main page. Very frustrating.

For example 12:15AM works fine, but 11:15AM updated to 11:15PM.

---

[StephenB]

I've confirmed this issue myself and report it to Netgear.

[steveoelliott]

This comes down to testing and verification...

I would assume Netgear have an extensive testing strategy even before making BETA releases available. They ideally need a scripted checklist / testing plan for all this kind of basic stuff as it clearly has been overlooked.

[Leia · Accepted solution]

@x219c, @StephenB, @steveoelliott, @scravatt, @bedlam1

This bug has been fixed on 6.9.5 beta1. You can download the firmware from the urls in this post. https://community.netgear.com/t5/ReadyNAS-Beta-Release/ReadyNASOS-6-9-5-T7-Beta-1/td-p/1656915