NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

SLK-Purdue's avatar
SLK-Purdue
Luminary
Aug 03, 2021

AGAIN - URGENT - Auto-update repeatable failure killing nvram!!!

I now have a REPEATABLE failure from the auto-update to v2.7.3.22.

 

I completely reset my config (1 RBR50 and 3 RBS50) to v2.5.1.16 yesterday with full firmware reload and factory reset.  Last night the config auto-updated again to v2.7.3.22 and AGAIN my config parameters (nvram) are corrupted.   Dumping the config parameters via the WebUI produces a file that can not be reloaded wia the WebUI because of errors.   Decoding the cfg file shows non-ASCII junk in the file.   This is the same results as my last auto-upgrade last Saturday.

 

NETGEAR - PLEASE STOP THE AUTO-UPDATE!!   This is breaking my configuration.

9 Replies

  • FURRYe38's avatar
    FURRYe38
    Guru - Experienced User
    Aug 03, 2021

    What happens if you factory reset the RBS and RBR with v22 loaded and setup from scratch then back a new back up config to file? 

    • SLK-Purdue's avatar
      SLK-Purdue
      Luminary
      Aug 03, 2021
      Factory reset is not a viable option for me at this time as I have a complex config with static DHCP and port forwarding that would be a complete pain to enter by hand. I do have some additional data, however. I have a repeatable scenarion 1. Firmware load and factory reset to v2.5.1.16 2. load parameters 3. come up with router only and go to update page on WebUI 4. v2.7.3.22 available 5. do update 6. nvram has junk THen Factory reset and firmware load v2.7.3.22 Come up and load old parameter file nvram OK and running difficult to absolutely confirm without telnet but look good Bottom line - something is not right doing auto-update with existing parameter file. Seems to support what others are saying too.
      • SLK-Purdue's avatar
        SLK-Purdue
        Luminary
        Aug 03, 2021
        Factory reset is not a viable option for me at this time as I have a complex config with static DHCP and port forwarding that would be a complete pain to enter by hand. I do have some additional data, however. I have a repeatable scenarion 1. Firmware load and factory reset to v2.5.1.16 2. load parameters 3. come up with router only and go to update page on WebUI 4. v2.7.3.22 available 5. do update 6. nvram has junk THen Factory reset and firmware load v2.7.3.22 Come up and load old parameter file nvram OK and running difficult to absolutely confirm without telnet but look good Bottom line - something is not right doing auto-update with existing parameter file. Seems to support what others are saying too.