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

Forum Discussion

Chase_Karr's avatar
Apr 13, 2024
Solved

Problem upgrading ReadyNAS Ultra 4 to OS 6

I have encountered a problem upgrading my Netgear ReadyNAS Ultra 4 (Model Number RNDU4000, with four 2-TB drives) to OS 6 and am looking for suggestions.

 

Before attempting the upgrade I replaced the original 1-GB memory module with a 2-GB memory module and ran memory test for 28 hours, zero errors. Also made sure the BIOS was the latest version (2011-08-23).

 

I followed StephenB's conversion procedure found at https://community.netgear.com/t5/Using-your-ReadyNAS-in-Business/ReadyNas-OS4-to-OS6-Files-Needed/td-p/2022710, downloading the two files from the links provided in that thread.

 

Sometime after starting Step 4 in the instructions a message "ERR: Could not properly extract" appeared. I do not remember if this was before or after a message indicating upgrade progress, something indicating FW was being written? It could have been both before and after.

 

Then the device went to "Booting 99%", let it sit for a couple of hours with no change before forcing a powerdown by holding the power button.

 

Subsequent tries to reboot end at various points from 90% to 98%. Pressing the power button the display reads "quotarpc.service" as best as I can read it.

 

It has been noticed that when rebooting now there is a message "Welcome to the ReadyNAS World !" that appears very briefly early in the process; that message was not observed prior to the upgrade attempt. Maybe I just missed it? Or does that mean OS 6 is partially installed?

 

The display then shows "Booting...", "Starting network", "Checking root FS", and finally the ascending percentages.

 

Any guidance would be appreciated!

  • StephenB's avatar
    StephenB
    Apr 13, 2024

    Chase_Karr wrote:

     

     

    Now what?


    It could be an issue with the disk, so perhaps test it in a PC with vendor tools.

     

    You could also try a factory default from the front panel (either with the current disk or a different one).

10 Replies

Replies have been turned off for this discussion
    • Chase_Karr's avatar
      Chase_Karr
      Tutor

      Thanks for your response, Sandshark!

       

      Following your suggestion and the instructions in the link provided, starting usbrecovery.exe on a Windows 10 PC resulted in an error message that said in part "The application has failed to start because its side-by-side configuration is incorrect." Checking Windows' Event Viewer led me to install "Microsoft Visual C++ 2005 SP1 Redistributable Package", which fixed that problem.

       

      Used a 1-GB USB drive and created the recovery USB. It was noticed that usbrecovery.exe would not "see" R4toR6_6.9.5.bin even when it was the only BIN file in the directory. Renamed R4toR6_6.9.5.bin to RAIDiator-x86-R4toR6_6.9.bin then it appeared and was selected. Usbrecover.exe reported "Not responding" for a few seconds during the process, but then later said "Done".

       

      Followed the instructions from the link you provided, but after holding the Backup button for 15 seconds (by a watch) the device started its normal boot process. Tried longer times in five-second increments, same results until I held the Backup button for 30 seconds. Never saw anything on the LCD that said anything about USB Recovery mode, just the far left block in the upper row blinking on and off.

       

      But then a bit over 60 seconds after releasing the Backup button the device powered down, just as predicted in the instructions! (The instructions did not suggest a time to power down.)

       

      Removed the USB drive and tried booting normally, but no joy, it still stalls out at 80-plus percent and showing "quotarpc.service" on the display.

       

      Downloaded R4toR6_6.9.5.bin again from the same link as before and re-created the recovery USB, same results.

       

      Now what?

      • StephenB's avatar
        StephenB
        Guru - Experienced User

        Chase_Karr wrote:

         

         

        Now what?


        It could be an issue with the disk, so perhaps test it in a PC with vendor tools.

         

        You could also try a factory default from the front panel (either with the current disk or a different one).

NETGEAR Academy

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

Join Us!

ProSupport for Business

Comprehensive support plans for maximum network uptime and business peace of mind.

 

Learn More