NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
dsnpevl
Apr 24, 2019Virtuoso
RN312 fails to come back up after update to 6.10.0
Just tried to updated RN312 to 6.10.0 via normal procedure (click button in pop-up on admin page). The new firmware was downloaded and I clicked the button to reboot on the second pop-up in the admin...
- Apr 24, 2019
After waiting for over 2 hours, I decided that the update wasn't going to proceed succesfully. Not sure what is considered normal update duration, but I don't remember it ever taking longer than 30 min.
Eventhough all the warning message advise against it, I took the risk to switch off the RN312. After waiting about a minute, I powered up again. Now I could log in with Putty again. After 10-15 min the admin page became available again with 6.10.0 Hotfix 2 firmware.
dsnpevl
Apr 24, 2019Virtuoso
After waiting for over 2 hours, I decided that the update wasn't going to proceed succesfully. Not sure what is considered normal update duration, but I don't remember it ever taking longer than 30 min.
Eventhough all the warning message advise against it, I took the risk to switch off the RN312. After waiting about a minute, I powered up again. Now I could log in with Putty again. After 10-15 min the admin page became available again with 6.10.0 Hotfix 2 firmware.
dsnpevl
Apr 25, 2019Virtuoso
Update procedure for 6.10.0 on RN516 worked without issues and completed in about 25 min.
- datahardyMay 07, 2019Aspirant
I did an upgrade to 6.10.0, too. System does not complete bootprocess. Hangs at 89% to 99% showing mysql.service. Is there a way to circumvine starting of mysql? Istn't there a timeout for failing units, especially since I do not use mysqld on the system.
Would be great if an netgear official could sddress the issue.
KInd regards
datahardy
- datahardyMay 07, 2019Aspirant
Well, in the meantime I learned that the display shows the last unit started successfully.
Fortunately I had ssh still activated. I used systemctl to check the status of smb. what showed not active. systemctl start smb hung up, so I did a reboot (cli) after a while. After that the device accomplished the boot process and showed up the UI. It should be mentioned that I disconnected the external USB-Drive before reboot. So, one can not be shure, what brougt the "Kuh vom Eis", completely.
Related Content
NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!