RN104 Boot problems.

[RoyKve]

Hey!

So.. this RN104 is starting to really piss me off tbh..

First i upgraded to a new firmware (several months ago) then i got the 300something out of memory error right after boot..
Went online and tried to find a solution to the problem without any luck. Shut down the RN104 and decided to wait since there was many more with the same problem...

Now i found the solution where u start it up in Read only mode. And this seemed to work.. and i signed on to the web interface where i got prompted to update to newest firmware 6.4.2...

And i tought this would fix my problems? how wrong was i?..

Now its stuck in Booting.. with a blue blinking led.. and its been like this for several hours..

I can Ping the device.. responds with 1ms each time..
I can use SSH.. and it only "hang".. not giving me login screen or error with connection refused or something like that..

I tried downloading Raidar to see if it can find the device.. it didnt..

I dont have backup of the Data on the RN104.. and there are a ton of images i dont wanna loose on it.. this is also the reason i decided to wait untill someone came up with a fix..
and YES! i probably should have taken the backup when i got it back up in Read only mode.. but i didnt.. so.

Model nr: RN10400 

Anyone got a solution to this? or should i just wait for it?

[StephenB]

What firmware were you running before it prompted for the update?

[RoyKve]

6.4.1

[JennC]

Hello RoyKve,

Can you try contacting support center as they might be able to set up a remote session to your NAS to see what's happening?

Welcome to the community!

Regards,

[Retired_Member]

@RoyKve wrote:

I dont have backup of the Data on the RN104.. and there are a ton of images i dont wanna loose on it.. this is also the reason i decided to wait untill someone came up with a fix..
and YES! i probably should have taken the backup when i got it back up in Read only mode.. but i didnt.. so.

---

I'm not judging, just trying to help, but if you have a lot of images/photos, you should have a backup at all times, not just when an issue is starting to show.

I have lost data before and I wish that to nobody! Now, I'm more careful, my photos are on several location, at all times.

Anyway, you should contact NETGEAR Support, I'm sure, they'll be able to help you.

[chiki_munze]

Hello, did you find solution? I'm suing similar model with latest firmware (6.4.2). Power Off/On is scheduled during the night. From time to time it happens that NAS can't boot. There is a message "booting" on lcd screen but it can stay for hours. Only solution is to disconnect NAS from power. Not sure what is the issue?

[BrianL2]

Hi chiki_munze,

Which ReadyNAS model are you using? Have you checked the 6.5.0 Beta Firmware? It has fixed shutdown issues on R6 models.

Let us know what happens.

Kind regards,

BrianL
NETGEAR Community Team

[JennC]

Hello chiki_munze,

We’d greatly appreciate hearing your feedback letting us know if the information we provided has helped resolve your issue or if you need further assistance. 
If your issue is now resolved we encourage you to mark the appropriate reply as the “Accept as Solution” so others can be confident in benefiting from the solution.

The Netgear community looks forward to hearing from you and being a helpful resource in the future!

Regards,

[chiki_munze]

I looked on website, made few searchs on forum but coudn't find where to download this new beta firmware?

[StephenB]

---

@chiki_munze wrote:

...made few searchs on forum but coudn't find where to download this new beta firmware?

---

Here's a hint:  Open "ReadyNAS Network Storage" and then look in the  "ReadyNAS Beta Release" section.  

https://community.netgear.com/t5/ReadyNAS-Beta-Release/ReadyNASOS-6-5-0-RC3/m-p/1059936#U1059936

If you use ReadyCLOUD, then I suggest waiting a few days - I think it is close to being released, and that should make the migration to the new ReadyCloud a bit simpler..

[RoyKve]

 Hey.

I have not been able to continue the searching on this box. (Vacations and such)

The latest FW update didnt do anything about the boot problem.. only changed the display from "booting..." to "boooting... 64% ######" and to 75% after second boot.

Ive bought myself a hdd that is big enough to backup all the data on the readynas.. and im going to transfer everything on it and format the drives to see if that works out when the drive arrives.

Also checked logs.

Last thing in the Kernel log is 

"May 20 02:35:05 aasheim-fil kernel: connmand invoked oom-killer: gfp_mask=0x200da, order=0, oom_score_adj=0"

May 20 02:31:53 aasheim-fil kernel: md/raid:md127: raid level 5 active with 4 out of 4 devices, algorithm 2
May 20 02:31:53 aasheim-fil kernel: RAID conf printout:
May 20 02:31:53 aasheim-fil kernel: --- level:5 rd:4 wd:4
May 20 02:31:53 aasheim-fil kernel: disk 0, o:1, dev:sda3
May 20 02:31:53 aasheim-fil kernel: disk 1, o:1, dev:sdb3
May 20 02:31:53 aasheim-fil kernel: disk 2, o:1, dev:sdc3
May 20 02:31:53 aasheim-fil kernel: disk 3, o:1, dev:sdd3
May 20 02:31:53 aasheim-fil kernel: created bitmap (15 pages) for device md127
May 20 02:31:53 aasheim-fil kernel: md127: bitmap initialized from disk: read 1 pages, set 0 of 29735 bits
May 20 02:31:53 aasheim-fil kernel: md127: detected capacity change from 0 to 5986292072448
May 20 02:31:53 aasheim-fil kernel: Adding 1046524k swap on /dev/md1. Priority:-1 extents:1 across:1046524k
May 20 02:31:53 aasheim-fil kernel: BTRFS: device label 0e351c12:data devid 1 transid 257599 /dev/md127
May 20 02:31:54 aasheim-fil kernel: BTRFS info (device md127): setting nodatasum
May 20 02:32:07 aasheim-fil kernel: IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
May 20 02:32:16 aasheim-fil kernel: mvneta d0070000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off
May 20 02:32:16 aasheim-fil kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
May 20 02:32:18 aasheim-fil kernel: mvneta d0070000.ethernet eth0: Link is Down
May 20 02:32:18 aasheim-fil kernel: IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
May 20 02:32:23 aasheim-fil kernel: mvneta d0070000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off
May 20 02:32:23 aasheim-fil kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
May 20 02:32:25 aasheim-fil kernel: mvneta d0070000.ethernet eth0: Link is Down
May 20 02:32:25 aasheim-fil kernel: IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
May 20 02:32:30 aasheim-fil kernel: mvneta d0070000.ethernet eth0: Link is Up - 100Mbps/Full - flow control off
May 20 02:32:30 aasheim-fil kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
May 20 02:35:05 aasheim-fil kernel: connmand invoked oom-killer: gfp_mask=0x200da, order=0, oom_score_adj=0

Im guessing this is the reason for the system to go into halt..

But how do i fix it?

[RoyKve]

searched google for a solution.

This actually booted the nas.. Display got stuck at "booting... 99%" and i instantly logged in via SSH and used uptime to check load..

It started at 4 and worked it way up to 13 untill it finally gave  "__out_of_memory+330" in the display of the nas.

This is what i did.

edited /etc/sysctl.conf and added these two lines:

vm.overcommit_memory = 2
vm.overcommit_ratio = 80

link to site where i found a "solution": http://www.hskupin.info/2010/06/17/how-to-fix-the-oom-killer-crashe-under-linux/

I dont know what more to do to be honest..