NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Tom_BSS
Aug 02, 2016Aspirant
RN-102 firmware upgrade failure
If a NAS 10200 chassis is unbootable (upgrade failure), can the disks be removed and installed in another chassis or read in some other way?
- Aug 02, 2016
Thank you for your help. We resorted to paid Netgear Tech phone support which was very helpful. It turns out the upgrade did go through the first time, but the NAS got hung up somehow. All is good now!
mdgm-ntgr
Aug 02, 2016NETGEAR Employee Retired
Does the NAS show in RAIDar?
Have you tried powering off the system and powering it on again to see what happens?
Have you tried a cold boot (shutdown, unplug power for say 5-10 minutes and then plug power back in)?
Are you still able to access the boot menu?: http://kb.netgear.com/app/answers/detail/a_id/22892/~/how-do-i-access-the-boot-menu-on-my-readynas-102,-202,-212-or-312%3F
Local/remote upgrade should make no difference. Getting prompted for a remote upgrade would just indicate that the NAS has a working internet connection. Either way the integrity of the downloaded image is verified before the update is installed.
Note if the problem is on the disks and not with the chassis then it will remain when moving it to another chassis.
Also you don't have to move to another RN102. You could move to e.g. a RN212 if you prefer.
- Tom_BSSAug 02, 2016Aspirant
The recommended upgrade for this unit, and what I attempted, was to 6.2.5. The USB Recovery tool instructions and links say to use ARM, which is 6.5.1. Should I proceed with the 6.2.5, then maybe take another jump to 6.5.1 later?
- StephenBAug 02, 2016Guru - Experienced User
Tom_BSS wrote:
Should I proceed with the 6.2.5, then maybe take another jump to 6.5.1 later?
I would. There are some warnings about jumping from very old firmware directly to 6.4 and 6.5.
- mdgm-ntgrAug 02, 2016NETGEAR Employee Retired
When you do a normal update from 6.2.5 to 6.5.1, there is a necessary update done on ARM systems such as yours which is not done by default when doing USB Boot Recovery. Generally USB Boot Recovery should be done with the same firmware you are already running e.g. 6.2.5.
Generally I'd check a few other things such as some of what I mentioned above before resorting to trying USB Boot Recovery. USB Boot Recovery should be considered as a last resort and it is not a magic fix for any problem that can be run into.
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!