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

Forum Discussion

b_rake's avatar
b_rake
Aspirant
Aug 09, 2017
Solved

RN104 stuck after OS reinstall

TL;DR - My RN104 was stuck on root fs check at 48% ->  rebooted to the same thing but stuck at 46% -> initiated OS reinstall from boot menu -> Now the screen is stuck at kfree+14c

 

Background:

I received an alert saying that my RN104 was using about 90% of it's space (8 out of 10TB). After finding out that I have 6TB of snapshots, I deleted all of the 2015 and 2016 snapshots for my shares and initiated a balance. I lost access to the box a while after. 

 

When I got home from work (hours later) the screen had "Out of Memory" and with that powercycled it as is usually necessary when servers go OOM. and left it at that. Hours later, I checked the box again and it just said 48%. Left it for the night and checked the next day around noon, still 48% curser not blinking. I hard powercycled again and watched it come up, it said something about doing a root filesystem check then the % numbers started climbing. This time it got stuck at 46% (which it got to fairly quickly). I left it for 2 days and it still had not moved, still stuck at 46% without the curser blinking. 

 

At this point i opted to re-install the OS from the boot menu. That seemed to go through the motions properly as far as I could tell, however it got stuck with the screen just displaying  kfree+14c and has been sitting there for a day. 

 

So does anyone have any ideas about steps I can take now? Is it safe to powercycle the box and see what happens when it boots up/attempt OS reinstall again?

Can I toss the drives in a normal linux box, assemble the array, and fsck from there/potentially grab a copy of important stuff so I can factory reset? 

 

Thanks guys, any advice would be great. 

  • So I got impatient and powercycled the box. Holding the power button nor reset button did anything so I ended up pulling power. The box booted, and completed the fsck it was stuck on previously. 

     

    My fw version was 6.7.4 btw (or at least that's what it booted in to when the OS reinstalled)

4 Replies

Replies have been turned off for this discussion
    • b_rake's avatar
      b_rake
      Aspirant

      Hey, thanks for the response.  I'm not sure off of the top of my head which version, It was one of the later minor releases of 6.7 tree. When I logged in after getting the space usage alert, I did have an updat waiting, however I didn't do it, thinking that I'd get disk usage under control before attempting a firmware upgrade and sadly didn't note the version I was coming from/to. Is there a way that I could verify the minor version while in this state? 

      • b_rake's avatar
        b_rake
        Aspirant

        So I got impatient and powercycled the box. Holding the power button nor reset button did anything so I ended up pulling power. The box booted, and completed the fsck it was stuck on previously. 

         

        My fw version was 6.7.4 btw (or at least that's what it booted in to when the OS reinstalled)

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