I just applied the 6.10.4->6.10.5 hotfix. The files are accessible from Windows Explorer, but I cannot do any maintenance via the web page (I tried in various browsers) because the admin page keeps refreshing after about 8 seconds. Looking at the logs, it appears that the time is now far out of accurate; I assume this is why the admin page keeps refreshing. In a previous post, the answer was to reinstall the OS!!!! I have NO IDEA how to do that. Is there a way I can connect to the device WITHOUT using the web-based admin pages? It refreshes too fast for me to go into Settings to adjust the time.This is a fairly urgent problem, and I thank you all in advance for all suggestions.

Sandshark wrote:So what else are you wanting them to do (other than just be quicker about releasing the fix)? They should have stopped pushing the update through their update servers when this problem first surfaced. (Actually they should have run it to ground when the release was still in beta).

An OS re-install is done from the boot menu, not the GUI. See How-do-I-access-the-boot-menu-on-my-ReadyNAS-102-202-212-or-312 . But I'm not sure that will help, as settings like how time is updated are normally retained when the OS is re-installed. A factory default should fix it, but that wipes out your data. Do you have SSH enabled? It's possible to set the time or go back to 6.10.4 via SSH. Was your NAS set up to get NNTP time updates? If so, it is curious that's not working right. Gets me wondering if a dead battery might be the cause for some units doing this, as the time at boot would be wrong.

Thank you for your prompt reply. Yes, as I recall, the NAS was setup to use an NNTP server.Interestingly, https does not work and reverts to http because of an invalid cert. That MAY be part of the problem.Running SSH from a Windows Powershell session returns ssh: connect to host 192.168.1.71 port 22: Connection refusedThis is probably because I never set up SSH access and according to documentation, "SSH access is disabled by default." It seems that SSH access can only be opened via the web page, which, of course, is not an option.Reinstalling the OS is also not an option. I have hundreds of GB of data and I would have to move them to a spare drive, which I do not have. Then I would have to reinstall PHP, PostgreSql, and Plex.As I mentioned, all was working well (save for the invalid cert) before the hotfix.Thanks again,Joel

jrfinkel wrote: Thank you for your prompt reply. Yes, as I recall, the NAS was setup to use an NNTP server. Then the next step is to see if the time is actually being updated. If you have the log zip file, you can look in connman.log for stuff like this: May 02 06:20:54 RN102 connmand[1964]: ntp: adjust (slew): +0.000374 sec Did you set up the NAS to use DHCP? A misconfigured network could result in breaking NTP. For instance, leaving out the DNS server(s) when you configure a static address.

jrfinkel wrote: Reinstalling the OS is also not an option. I have hundreds of GB of data and I would have to move them to a spare drive, which I do not have. You might be confusing the OS reinstall with a factory default. The OS reinstall does a partial reinstall of the OS. It won't affect your data, and you normally don't need to reinstall any apps. Certainly that's the case with plex, I don't use the other two. But not having a backup plan in place for your NAS is taking a big risk - at some point you will lose the data, it's just a question of when. Maybe a topic for another day though. jrfinkel wrote: As I mentioned, all was working well (save for the invalid cert) before the hotfix. Cert errors are normal, and shouldn't interfere with your web access (once you click through the security warning). The NAS uses self-signed certs, and there is no good way to defeat the warning in most browsers.

Admin page keeps refreshing...time off after 6.10.5 hotfix

48 Replies

Sandshark
Sensei
May 18, 2021
An OS re-install is done from the boot menu, not the GUI. See How-do-I-access-the-boot-menu-on-my-ReadyNAS-102-202-212-or-312 . But I'm not sure that will help, as settings like how time is updated are normally retained when the OS is re-installed. A factory default should fix it, but that wipes out your data.

Do you have SSH enabled? It's possible to set the time or go back to 6.10.4 via SSH.

Was your NAS set up to get NNTP time updates? If so, it is curious that's not working right. Gets me wondering if a dead battery might be the cause for some units doing this, as the time at boot would be wrong.
- jrfinkel
  Aspirant
  May 18, 2021
  Thank you for your prompt reply. Yes, as I recall, the NAS was setup to use an NNTP server.
  
  Interestingly, https does not work and reverts to http because of an invalid cert. That MAY be part of the problem.
  
  Running SSH from a Windows Powershell session returns ssh: connect to host 192.168.1.71 port 22: Connection refused
  This is probably because I never set up SSH access and according to documentation, "SSH access is disabled by default." It seems that SSH access can only be opened via the web page, which, of course, is not an option.
  
  Reinstalling the OS is also not an option. I have hundreds of GB of data and I would have to move them to a spare drive, which I do not have. Then I would have to reinstall PHP, PostgreSql, and Plex.
  
  As I mentioned, all was working well (save for the invalid cert) before the hotfix.
  
  Thanks again,
  Joel
  - StephenB
    Guru
    May 18, 2021
    jrfinkel wrote:
    
    Thank you for your prompt reply. Yes, as I recall, the NAS was setup to use an NNTP server.
    
    Then the next step is to see if the time is actually being updated. If you have the log zip file, you can look in connman.log for stuff like this:
    
    May 02 06:20:54 RN102 connmand[1964]: ntp: adjust (slew): +0.000374 sec
    
    Did you set up the NAS to use DHCP? A misconfigured network could result in breaking NTP. For instance, leaving out the DNS server(s) when you configure a static address.
- popster
  Aspirant
  May 22, 2021
  Later today or tomorrow I suppose I will try an OS reinstall from the boot menu. If it simply reinstalls 6.10.5 I'm not sure how successful the process will be, however.
  
  As things stand at the moment, I can't stay connected for more than 10 seconds via the browser interface (multiple browsers, Windows and Android). I can very briefly switch from the admin page to another option, but am disconnected too soon to be able to carry out a command (eg, d/l a log file). I can't log in via Putty as I am denied access and I can't generate any log file via Putty which I thought might help.
  
  Will report back.
  - Sandshark
    Sensei
    May 22, 2021
    Can you get a log file via RAIDar?
popster
Aspirant
May 29, 2021
Ok... I finally had a few minutes to sit down and try to work through this issue...again.

I entered the boot menu and chose to do an OS install. After completing that process I was able to log into the NAS from any browser/computer on my network and all worked as it should...until.

Until I set a new password (OS install resets password to default). Once the new password was accepted, the anomalous behavior returned and I get disconnected every few seconds. Looking at the inspector/console output from Chrome/FF/Edge, the problem appears to lie in the js code attached to a Google Analytics cookie. Why is this on my NAS!? The site loads but when the cookie attempts to set all the browsers report errors and that's when I lose the connection. Why this behavior is absent with the defaults set I have no clue.
- jrfinkel
  Aspirant
  May 31, 2021
  Just for yucks, I tried logging in using Edge on my Android phone. It worked for about 5 minutes but then logged me out when I changed pages. I then tried Chrome on my phone and that failed in the same way.
homer51502001
Aspirant
Jun 19, 2021
NETGEAR - what are you doing, way to evaporate any faith in your product.... the NAS was "stable" for many months, after an OS Reinstall, back to the Wizard (which looked fine - first attempt was done without disks in place, then once that looked ok I rebooted with the 4 disks in situ, again it didnt take the recent OS install) so try again NAS appears on the network but again unable to browse the GUI or the drives using Windows explorer as the admin creds wont take...
- homer51502001
  Aspirant
  Jun 19, 2021
  can we boot using the USB to an older version that is stable??
- StephenB
  Guru
  Jun 19, 2021
  homer51502001 wrote:
  
  after an OS Reinstall ... first attempt was done without disks in place
  
  That is a waste of time, since the OS reinstall just reinstalls the the OS onto the disks. The system boots from the disks.
  
  homer51502001 wrote:
  
  unable to browse ... the drives using Windows explorer as the admin creds wont take...
  
  That is not the usual symptom. Reports here are that issue affects log in to the web ui and ssh - but not file explorer.
  
  If you successfully did the OS reinstall, try using password as the admin password.
  
  Some have been able to downgrade using USB recovery.
  - homer51502001
    Aspirant
    Jun 19, 2021
    hi, yes I have been using the default, that is how I know the GUI keeps reloading as the credentials are used each time, as for not using the disks, well the NAS did boot and I was able to bring up the wizard without disks installed, the reason I took out the disks was my concern that the NAS did something stupid and wipe the sensative data.... so at this time I am using the RAIRar as there is a prompt about delays / unresponsiveness but considering its been up for 7 hours and only at 10% it might be a while before I can test the issue.
    
    at this time, no change - admin page keeps reloading after 20 secs, and in file explorer, NAS is on the network but I get prompted for admin details, so admin / password doesn't work. - is this because the processes are chewing the resources?? you would hope not, but this is Netgear and I have had a NAS fall over before because of a back plane issue and I needed to find an identical model many years later so I wont be surprised...
    
    next step will be support and trying to revert back to a known working fw build.