NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
ReadyNAS 104 upgraded to OS 6.4.0 shutdown hang
Following upgrade to this release I am unable to shutdown.
System hangs with "Shutting dow. Goodbye." - I left it in this state overnight.
Power must be removed to complete shutdown.
Can confirm beta 3 fixes the no shoutown with custom MTU issue.
74 Replies
Replies have been turned off for this discussion
There are a couple of us having the same issue here https://community.netgear.com/t5/ReadyNAS-Beta-Release/Issues-with-OS-6-4-0-beta/td-p/976214
No definitive answer yet unfortuntaely.
A
Indeed I saw after a google search. I noticed it in the beta thread but it appears to have come through to release :-(
I was also suffering this bug and I saw something on another forum suggesting it only occurred whilst the drives has spun down during "off cycles" and the fix was to disable drive spin down. A slightly more elegant solution for me was to load the anti-virus app and schedule a full "data scan" 5 mins before the planned timer shutdown, this would ensure the drives were spinning when the planned shutdown triggered. It has worked for me for the last 3 nights :-) HTH
Doens't make any difference whether its a scheduled or a manully instigated shutdown on my device (web guid and power button).
I've tired disableing disk spin down and it hasn't made any difference.
Restart works fine.
Sounds like a bug/fault in signaling the hardware 'power off'.
My RedyNAS 10400 has the same problen sind I upgreded to 6.4.0. However so far shutdown via admin webpage or powwer button worked. Schedueld shutdown does not power down the ReadyNAS. There is no hint about it in the logfile. I log all loglevels for all categories. There is the normal system shutdown entry with a green dot. The next log entry is the normal system entry that backgrounf services started with a green dot. Logging into the NAS I unfortunately I could not find a readable logfile equivlent to syslog. We are waiting for for a hint or better a solution to this problem by netgear
Addendum to my last entry.
I did a few test with shutdown (booting up and then shutting down without any action on the NAS inbetween).
I got the following results:
- shutdown via power button: system shuts down and powers off like it shoud
- shutdown via admin webpage: system shuts down and powers off
- shutdown via ssh login as admin: (shutdown -h -P)
system shuts down and powerd off
if the option -P is not given the systems shuts down but does not power off
(power button is on but not blinking)
I did not test scheduled shutdown again since it never worked since uppdate to 6.4.0.
(The system was probably down, power button blinking, god bye message an disply and nor reacting to anything except power disconnect)
Hi.
My father in law and myself have upgraded to firmware 6.4.0 and we both have the same issue that I cannot shutdown the 102 Readynas applicance via the power button by pressing twice or scheduled shutdown.
It use to work fine for firmware V6.2.5. I saw in the forums that people had problems with this firmware in the beta versions. Was wondering if anyone else has this issue with the released version? Is there a fix or should I downgrade firmware to the previous version? Is there a way to do that?
Grant.
The scheduled shutdown and hanging shutdown should be treated as two seperate issues until a link is proven. The scheduled shutdown seems to be problem with triggering the process. The 'hanging' shutdown is a problem completing the task/firmware receiving message for power off.
gw_rocks apprently is isn't possible to downgrade (well at least there isn't a supported method). I would leave it powered on until you hear otherwise :-)
Hi werwolf, gw_rocks, MartynHeat1 & rivit,
I've sent you guys all a PM. Please check your inbox.
Kind regards,
BrianL
NETGEAR Community TeamMy ReadyNAS 102 hangs too after upgraded to 6.4
Best regards
Ralf
Notes from Netgear level 3 support below... I asked that spun down disks also be tested to see if they cause an issue, which they confirmed will be tested next week.........
Notes added by 34004
Hello, Sir
This is QingHong from Netgear level 3 engineer, this case was assigned to me.
According to my Experience, and I checked NAS logs, there are some kernel error, so I guess this issue was caused by MTU 9000.
I have reproduce this issue in my lab.
I will escalate this issue to R&D engineer, this need a bit long time to fix this issue, so please disable this function, and I will give you update when I received any feedback, thanks.
Regards,
QH
[T060]MTU was the solution for me. Changed it to default & shutdown correctly last night. No other changes required.
Hello all,
You guys might want to try the BETA FW 6.4.1-T21.
Regards,
- I would stay on 6.2.5 if I had my time again
BJB, why on earth would you even think about "upgrading" to a firmware release you know doesn't work?
I'd steer well clear if I were you.
That Beta 1 release doesn't seem to mention shutdown issues, so I'll hold fire I think, especially given words like "hopefully" are used in the list of fixes.
ColinR1,
Exactly. This is why I was clarifying the directions I was being given. Did not make sense to me to upgrade to firmware that has issues unless there is a known trigger for the issues that can be avoided 100%.
Jophus, you mentioned you would have stayed on 6.2.5.....The other question is let's say I wait until the 6.4.X firmware has fixed this issue......Do I understand the suggestion correctly that I should go to an interim version first since I am way back on 6.1.9? Or can I just forge ahead? If I do need an interim version, I just need a link on the process of how to obtain it and install it.
Not used to being out of the loop. On the PC side I can give the advice....I am just not up to speed on the the Readynas firmware stuff...:smileyhappy:
Thanks,
BJB
- If 6.1.9 works for you, with no bugs, issues or complaints, I would recommend you stick with it.
If 6.2.x has features or fixes you need, go to the latest version of 6.2.5.
6.4.0 has issues and bugs. Wait for 6.4.2 or .3
I will be following this rationale from now... But I can't downgrade to 6.2.5 - Thanks grahamu59. Can you please tell me what version number you are presented with when logging into OS6 admin page after installing the 6.4.1 beta?
I installed beta 3 this afternoon but I see version as 6.4.0 on my rn102.
Thanks - Thanks. No, I had the same problem upgrading 6.2.5 to 6.4.0 where it would not upgrade until I hard factory reset the box using a paperclip.
I will try a hard reset and see if that works. I had no problem upgrading 6.1.9 to 6.2.4 and then 6.2.5... But 6.4.0 has presented problems.An update: An update to 6.4.1. beta 3 won't work on my rn102. Back with Netgear support to investigate the problem. Looks like I have the "mismatched checksum" issue with upgrading 6.4.0 to 6.4.1 beta 3. This is the same issue I had with 6.2.5 to 6.4.0 upgrade.
The issue manifests where the uploaded, update image file checksum does not match the expected checksum. On a reboot, the system tries to flash the image, notices the checksum of the file does not match what is expected, and promptly does not flash the image update to the system. The error is silent and does not show in the OS6 log file. The admin webpage silently remains on the previous version.
The previous workaround was to install an "app" which netgear created. The "app" addressed "the known issue".
To discover if this is an issue, the initrd log file (when you "download logs" from the log page of frontview) shows something like:
[2015/11/16 19:27:49] Update image checksum mismatch (f5c6610f8a13b136600a1481017e7a4e/1b743406f16f4c33e8a121f72da05702)!
Netgear support have "escalated this to R&D"
Beta 3 installed on my RN102 using a modified workaround from the 6.2.5 -> 6.4.0 update: Installed the Beta 3 update, DID NOT RESTART and installed the workaround update file. On restarting I was on 6.4.1-T35 (Yay!)
Enabled Jumbo Frames, and restarted = OK
Started copying files to the NAS = slightly slower that MTU 1500 - why? DMESG and kernel logs show heaps of:
mvneta d0074000.ethernet eth0: bad rx status 0f830000 (overrun error), size=xxx
where xxx is a frame size less than 9000
Anyway, shutdown NAS from OS6 ..... AND..... same problem as before. The NAS is still on, with blue lights lit, but no response. Pulling power is the only way to shut it down.
Beta 3 has not solved my MTU 9000 problem. Back at MTU 1500 the box is CPU limited on transfers but shuts down and wakes-on-LAN. Back with NG support.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
