NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Hermes_Muc
Jul 14, 2010Aspirant
Uncontrolled power-ups with RN Pro after Raidar Upg.
After upgrading my ReadyNAS Pro to RAIDiator 4.2.12, I now experience uncontrolled system starts.
System now boots up uncontrolled at least three times a day when turned off.
Of course, scheduler an WoL are disabled.
Any ideas what that might be caused from?
Thanx & Best Regards
System now boots up uncontrolled at least three times a day when turned off.
Of course, scheduler an WoL are disabled.
Any ideas what that might be caused from?
Thanx & Best Regards
56 Replies
Replies have been turned off for this discussion
- ultrabikeAspirantMy readyNAS Pro would not have uncontrolled power-ups with 4.2.12 or 4.2.13. BUT my readyNAS Pro would not always auto power up after upgrading with either 4.2.12 or 4.2.13. I also had issues with disk spin down (system would be unresponsive) with 4.2.13, so I had to disable disk spin down.
I downgraded to 4.2.11 and all these problems went away. ultrabike wrote: My readyNAS Pro would not have uncontrolled power-ups with 4.2.12 or 4.2.13. BUT my readyNAS Pro would not always auto power up after upgrading with either 4.2.12 or 4.2.13. I also had issues with disk spin down (system would be unresponsive) with 4.2.13, so I had to disable disk spin down.
I downgraded to 4.2.11 and all these problems went away.
Please open seperate threads for Disk Spin Down as it could be disk.- ultrabikeAspirant
Jedi Knight wrote: ultrabike wrote: My readyNAS Pro would not have uncontrolled power-ups with 4.2.12 or 4.2.13. BUT my readyNAS Pro would not always auto power up after upgrading with either 4.2.12 or 4.2.13. I also had issues with disk spin down (system would be unresponsive) with 4.2.13, so I had to disable disk spin down.
I downgraded to 4.2.11 and all these problems went away.
Please open seperate threads for Disk Spin Down as it could be disk.
I understand. But since 4.2.11 solved my problems and meets my needs, I'm not going to open a new ticket or attempt to debug this problem. My comment's main purpose was to inform that I have the same uncontrolled power-ups problem with FW versions 4.2.12 and 4.2.13 (problem replication).
Furthermore, I appreciate this post since it provided me information on what FW (4.2.11) to use to have my system stable again. - BartDPAspirantI too have this issue :(
I used the power timer, but now due to this bug I'm forced to stop the readynas manually and then use the power switch to prevent it from booting :(
hope this can be fixed soon since I'm a lazy guy :) - Bart, We are looking into this issue.. thanks for reporting :)
- saadhijalAspirantI powered down my Pro BE running 4.2.13 and left on a 10 days trip. Came back yesterday to find it running. Had a shouting match with my sons the theme being do not touch my stuff when I am away. Powered down last night and this morning it was running again and I found this thread. This is going to cost me big time when I tell them that I believe them now.
- ultrabikeAspirantI experienced the same problem with 4.2.11 (unable to power up @ scheduled time while the logs DO show the system powered up).
Based on what I've read in this thread I toggled the power up/down option and re-filled the schedules (since somehow they cleared themselves!). Then I powered down the system (not reboot, just powered down), unplugged the system from power, and removed the Ethernet cable for 1 minute. I then brought up the system again, and problem when away... - sdouekGuideI have the same problem on my pro, weather I power down from the button or from frontview. The systems turns itself back on after 10 minutes. If I also turn of the console switch controlling the pro's electricity and turn it back on it will turn on without me touching the pro's on button itself.
I have the following enabled:
1) disk spin down set to 90 minutes
2) network monitoring of UPS
I have power timer & Wake on Lan Disabled.
It looks like to me that it treats a power down like a power failure and reboots when power is restored. - sdouekGuideI have fixed the problem but was advised by tech support to RMA the unit in. The tech guy says that when a unit powers on for no reason it is usually indicative of a PSU going bad. At his suggestion he recommends I RMA the unit. I was kind of bummed since the unit was less the 2.5 months old and had to pay for shipping. I think netgear should stand by their product and offer free shipping but that is another story.
Has anyone else heard of this type of PSU problem ?
To fix the problem I had to remove both network cables and the USB connection to my UPS. Waited about 15 minutes and plugged everything back in and the problem went away. Apparently there may be enough current in either the network cables or the USB to trigger the PSU to turn on again.
Note: you have to physically remove the cables turning of the switch and the ups unit is not enough. saadhijal wrote: I powered down my Pro BE running 4.2.13 and left on a 10 days trip. Came back yesterday to find it running. Had a shouting match with my sons the theme being do not touch my stuff when I am away. Powered down last night and this morning it was running again and I found this thread. This is going to cost me big time when I tell them that I believe them now.
Could you try with 4.2.15?
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!