ReadyNAS NV+ Stuck at "Scheduled on" event after 4.1.10

Thanks guys for feedback.
As being a SW engineer doing my own SW I certainly know that it might be a coincidence. However, it started shortly after upgrading. I have no experience with this forum, but I also expected to see more "noise" for a general problem with the release. On the other hand it would be interesting to know how many people are bothering to use scheduling.
Not thinking of the environment is helps in my case. At least the NAS stays happy so far.
There was everything alreight before upgrading. The only issues I had before were a disk reporting repeatably bad sectors. So I have replaced it. The other problem was when trying an add-on which killed the running installation. I ended up to do a factory reset. Luckily I was able to copy all stuff off the disk before.
I will follow your recommendation and reinstall.

Bad news - the first scheduled power-on after a successful scheduled power-off failed.
The unit was again stuck at "Schedule on" with the blue power light flashing and no activity or disk LEDs lit.
I don't know wether to downgrade to 4.1.8??

--JEBR

:shock: You have my sympathy. Even so, it will not help much.
I will switch back to 4.1.9 then. However, I am stuck with the backup. Suddenly one notices a disadvantage of large disks.

4.1.9 has the ownership problem. I wouldn't recommend that firmware. You could try downgrading to 4.1.8 if you want.

Jebr and Koahnig - I do not note any mention of a current and complete backup of your units. Since both of you have experienced problems I would have thought that would be one of the first things you would do. With an current and complete backup you would then have the luxury of doing a factory default wiping the disks completely and reinstalling the firmware from scratch.

PapaBear wrote:
Jebr and Koahnig - I do not note any mention of a current and complete backup of your units. Since both of you have experienced problems I would have thought that would be one of the first things you would do. With an current and complete backup you would then have the luxury of doing a factory default wiping the disks completely and reinstalling the firmware from scratch.

I was in the process of doing a backup. The downgrade to 4.1.9 did not help. After a couple of successful automatic boots in the morning I am back to square one. It failed this morning again. So, it is not simply a question of the version.
I am contemplating about doing a factory reset. The only advantage I see would be reset of any memory and settings not changed with new versions. Is this worth to do?
Are there some maintenance tools around for checking the HW?

I would like to report a similar issue. I am running 4.1.10 in an Infrant NV, which has been running for quite a while. In my application, my NV wakes up at midnight to be the target of a ReadyNAS Pro (6) backup. I see this error from the Pro, since it reports a communications error when the NV doesn't wake up.

When I inspect the NV, it is stuck on a flashing blue light.

Let me know if there is some way to help get information to the folks who can fix it.