RN202 does not remember last state after power loss, always powers up
Hello everybody,
I recently bought a diskless ReadyNAS 202 and I'm still in the process of setting things up. However, I noticed that it always powers up when its power supply was interrupted, regardless if it was running or in standby before.
If I recall correctly, I have read somewhere that the RN202 is supposed to remember the last power state and revert to that state. Is this correct?
When I gracefully shut down the NAS and then pull the plug, I would like it to stay in standby when I put it back in. How do I do that?
My RN202 is running the latest v6.4.2, wake on LAN is deactivated (network LEDs are nevertheless always lit).
Re: RN202 does not remember last state after power loss, always powers up
Hi mdgm
I just sent you the logs according to the instructions you kindly provided. This is the use case I described in my email:
My use case is this: Each night, I gracefully shut down the NAS via the power button. After that, I cut the power to the NAS by switching off a switchable power strip. The next morning, I switch the power strip on again.
Expected behaviour: The Hardware Manual states the the NAS should remember its last power state. Hence, I expect the NAS to remain shut down/switched off.
Actual behaviour: A few seconds after switching on the power strip, the NAS boots. It does so every time.
Re: RN202 does not remember last state after power loss, always powers up
Well, in my use case it's a night, so 6-8 hours. But the NAS exhibits the same behaviour if I unplug it for a couple of minutes. Since I got it a couple of days ago, not once has it stayed off after power loss.
Re: RN202 does not remember last state after power loss, always powers up
Sorry, I just realised I misread your question. I cut the power about 10 minutes after the NAS completes shutdown (all front lights off, network LEDs from the NIC stay lit).
Re: RN202 does not remember last state after power loss, always powers up
I was able to reproduce your issue. It should be fixed in the next firmware release. There is a workaround you can apply for now though. Enable the Power Timer option in the Power tab, and set the schedule to always be on. This should make it behave like it's supposed to for your use case.
