× NETGEAR will be terminating ReadyCLOUD service by July 1st, 2023. For more details click here.
Orbi WiFi 7 RBE973
Reply

RN102 firmware update

Lovenupload
Aspirant

RN102 firmware update

Hi all,Hoping for some help.

I have the RN102. currently running firmware 6.2.5.  Yes that old.

Ever since I've owned it I have had no luck updating the firmware.

 

I have downloaded 6.5.2 and tried to manually do it. It says its updating and gets to about halfway up the blue update bar then the blue bar shoots all the way to the end.

 

The NAS then reboots, but I'm still on Firmware 6.2.5.

 

Any ideas?

 

Thanks In Advance

 

Message 1 of 14

Accepted Solutions
StephenB
Guru

Re: RN102 firmware update


@Lovenupload wrote:

[1262]: Error: Connection failure: Connection refuses.
Is this relevant?

Could be, it depends on what connection it was (and why).

 

Can you look at volume.log?  Scroll down until you get to the df -h and df -i sections.  I'd like to see the two entries for /dev/md0:

=== df -h ===
Filesystem      Size  Used Avail Use% Mounted on
/dev/md0        3.7G  829M  2.7G  24% /

=== df -i ===
Filesystem      Inodes IUsed   IFree IUse% Mounted on
/dev/md0       1048576 14418 1034158    2% /

 

 

View solution in original post

Message 12 of 14

All Replies
StephenB
Guru

Re: RN102 firmware update


@Lovenupload wrote:

I have downloaded 6.5.2 and tried to manually do it. It says its updating and gets to about halfway up the blue update bar then the blue bar shoots all the way to the end.

 

The NAS then reboots, but I'm still on Firmware 6.2.5.

 

Any ideas?

 


Is the NAS able to connect to the internet?  If you are using NTP (automatic time sync) you can download the log zip and look for NTP time adjustments in connman.log.  If those are present, then it is able to reach the internet.

 

Also, if you have a scratch (spare) disk, you could try powering down the NAS, removing the current disks (labeling by slot), and then do a factory install with the spare disk inserted.  Then try the manual update with the spare.

Message 2 of 14
Lovenupload
Aspirant

Re: RN102 firmware update

Ok. So I've found out my rn102 is not connected to the internet. It is accessible through my network though.
I don't run a Netgear router, so how do I set up a different router to let the NAS go online.
Also I am not great at computers and networking. So be kind. Thanks
Message 3 of 14
StephenB
Guru

Re: RN102 firmware update


@Lovenupload wrote:
Ok. So I've found out my rn102 is not connected to the internet. It is accessible through my network though.
I don't run a Netgear router, so how do I set up a different router to let the NAS go online.
Also I am not great at computers and networking. So be kind. Thanks

Can you summarize how you reached that conclusion?

 

Is the NAS set up to use DHCP, or did you configure a static IP address?

Message 4 of 14
Lovenupload
Aspirant

Re: RN102 firmware update

Ip setting on the network tab are
DHCP IPV4 DHCP IPV6.
Message 5 of 14
Lovenupload
Aspirant

Re: RN102 firmware update

To summarise no apps will download and cannot update. Is there a way to check the connection?
I've logged into the router and the NAS shows up as connected to the router, and the router is connected to the internet. I turned off the router firewall but it didn't make any difference
Message 6 of 14
StephenB
Guru

Re: RN102 firmware update


@Lovenupload wrote:
 Is there a way to check the connection?


Yes, and I told you how in an earlier post in this thread.

 

If you are using NTP (automatic time sync) you can download the log zip and look for NTP time adjustments in connman.log.  If those are present, then it is able to reach the internet.

 

NTP is enabled by default, so it likely is on.  Click on the settings wheel next to device time on the main page in the admin web ui.  You should see a pop-up then.  Make sure synchronize time with an internet server is checked.

 

Then go to the logs page, and download the log zip using the button on the upper right of the page.  Open connman.log (notepad will read it) and look for entries like this:

Jun 30 23:52:28 NAS connmand[5599]: ntp: adjust (slew): +0.000869 sec

If you see these adjustments, then the NAS is reaching the internet.

 

Message 7 of 14
Lovenupload
Aspirant

Re: RN102 firmware update

I have no connman.log.
Core and Cron are the only 2 logs that start with a c.

Message 8 of 14
Lovenupload
Aspirant

Re: RN102 firmware update

I do appreciate you trying to help by the way.
Message 9 of 14
StephenB
Guru

Re: RN102 firmware update


@Lovenupload wrote:
I have no connman.log.
Core and Cron are the only 2 logs that start with a c.


Try searching systemd-journal.log for ntp, and see if you find it there.

Message 10 of 14
Lovenupload
Aspirant

Re: RN102 firmware update

Right. Yes we have some results
[1103]: ntp: time slew +0.018225 s
So I'm online.
Last log says
[1262]: Error: Connection failure: Connection refuses.
Is this relevant?
Message 11 of 14
StephenB
Guru

Re: RN102 firmware update


@Lovenupload wrote:

[1262]: Error: Connection failure: Connection refuses.
Is this relevant?

Could be, it depends on what connection it was (and why).

 

Can you look at volume.log?  Scroll down until you get to the df -h and df -i sections.  I'd like to see the two entries for /dev/md0:

=== df -h ===
Filesystem      Size  Used Avail Use% Mounted on
/dev/md0        3.7G  829M  2.7G  24% /

=== df -i ===
Filesystem      Inodes IUsed   IFree IUse% Mounted on
/dev/md0       1048576 14418 1034158    2% /

 

 

Message 12 of 14
Lovenupload
Aspirant

Re: RN102 firmware update

Hi Stephen.
I don't know what's happened, but I tried to update the firmware again to 6.5.2 manually and it did it. From then on everything seemed to work. Now at 6.10.7
I'd like to thank you for your patience with me.
It may have been Firefox settings as the Netgear web UI needed permission . But i did that to start with, so I'm not sure.
Thanks again for your help
Message 13 of 14
StephenB
Guru

Re: RN102 firmware update


@Lovenupload wrote:
I don't know what's happened, but I tried to update the firmware again to 6.5.2 manually and it did it. From then on everything seemed to work. Now at 6.10.7


Great!

Message 14 of 14
Top Contributors
Discussion stats
  • 13 replies
  • 1995 views
  • 1 kudo
  • 2 in conversation
Announcements