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

Forum Discussion

desantj's avatar
desantj
Aspirant
Apr 20, 2021

RN104 "Boot from USB Failed!" and Cannot Access Boot Menu

Hi, my RN104 was successfully updated to FW 6.10.4 when the FW became available.  It's functioned fine until now.  I normally have it powered off and I know it does power on by itself occasionally (about every 2-3 weeks).  I came into the room to find the unit powered on, backup button light and power button light both flashing rapidly, and the display reading "Boot from USB Failed!"  The only way to power it off is by removing the power cord (forced shutdown) - the power button has no effect.  When I reattach the power cord, the unit immediately powers on with the same flasing lights and message on the screen.  I'm unable to access/get into the Boot Menu via the RESET button method, even if I press and hold in the RESET button and reattach the power cord.  I've also attempted to build and use a USB Recovery Tool (kb29952) and haven't had success with it. 

 

The first one (32 GB USB drive) is sensed and appears to perform a recovery...it finishes and powers off in under 1 minute after the "ReadyNAS USB Recovery" message appears on the screen.  Powering it back on with the power button returns it to the original failure state (flashing lights and failure message). 

 

The second one (2 GB USB drive) doesn't seem to boot - the display never changes from "Boot from USB" no matter how long I depress the Backup button. 

 

The 3rd one (8 GB USB drive) is sensed, appears to perform a recovery, and powers the unit off in under 1 minute, just like the first USB drive...powering the unit back on returns the same failure (flashing lights and message).  The 1st and 3rd USB drives were formatted as FAT32, the 2nd one was already formatted as FAT.  I went back, reformatted the 2nd USB drive as FAT32, rebuilt it as a USB Recovery Drive, and tried again...same as before, it doesn't appear to be read and the display remains at "Boot from USB".  I'm also unable to access the Boot Menu after using any of the 3 USB drives and powering the unit back on while holding in the RESET button. 

 

It appears the ReadyNAS hardware is failed but I wanted to see if anyone else has any suggestions on what to try.  The ReadyNAS unit is connected to a Windows PC running Windows 10 Pro x64 OS, version 20H2.  I do have access to a Windows 10 PC running Windows 10 Pro x86 OS, version 20H2.  I may try building the USB Recovery drives on it later this week.

 

Thanks for your time and suggestions!  

4 Replies

Replies have been turned off for this discussion
  • Sandshark's avatar
    Sandshark
    Sensei - Experienced User

    How does it behave when you power on without the drives?

    • desantj's avatar
      desantj
      Aspirant

      Hi, it behaves the same way with or without the drives installed in it.  

       

      I also tried StephenB's suggestion to create the USB Recovery Stick in enhanced (Administrator) mode.  I got the same results - the unit accesses the USB Recovery Stick and apparently runs the recovery program; unit powers off within a minute; restarting the unit provides the same failures.

       

      I did some Google'ing and saw that the unit used a CR2032 battery, like a computer motherboard uses a coin battery to hold BIOS/CMOS settings.  I disassembled the unit and installed a known good CR22032 battery, reassembled the unit, and tried the USB Recovery Stick again.  Same results.  I also tried holding in the RESET button to call up the Boot Menu - no luck there.

       

      The unit that failed (Unit A) is about 8 years old.  I have an identical unit (Unit B) that I have 4 1TB drives in.  I plan to remove those drives from Unit B, install the 4 4TB drives from Unit A, and see how Unit B reacts.  With luck, I haven't lost the data on the drives from Unit A and having those drives in Unit B will work fine.

       

      The Google'ing also showed me the flash memory is soldered to the board.  I was hoping it was installed in a socket, but it's not so I'm not going to try and replace it.  

      • mdgm's avatar
        mdgm
        Virtuoso
        You could try having a look around using the serial console I guess; or booting off USB without the firmware image .img file and telnetting in and having a look. Though it does sound like it’s probably some hardware issue.