NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
corinbishop
Jan 14, 2016Guide
Readynas 104 won't boot. Error 354 out_of_memory. After upgrade to 6.4.1 #26323717
installed 6.4.1 from 6.2.5 yesterday. All went ok. Did all the 'calculating'. worked fine.
failed overnight with out_of_memory error 354. now won't boot.
tried reinstallOS. No luck.
tota...
- Feb 15, 2016You could try RO mode, see https://community.netgear.com/t5/Using-your-ReadyNAS/Readynas-104-won-t-boot-Error-354-out-of-memory-After-upgrade-to/m-p/1044151#M103244
thenorthface
Jan 15, 2016Aspirant
Has anybody solved this yet ? It's happened to mine last night after the new firmware update keeps saying out of memory 354 ? Is there a way to go back to the old firmware
corinbishop
Jan 15, 2016Guide
Hiya,
I don't think downgrade is possible.
I've opened a support case with netgear so I'll let you know what happens.
So far they've asked a load of questions about ping/admin panel/raidar etc. They also asked me to try support mode:
My response to them this morning was:
_________________________________________________________________
Hi xxxxxx and thanks for taking on this problem.
I'll try to give as much detail as possible and hopefully it will help:
So:
As explained before, I did the upgrade from 625 to 641. All proceeded as planned, I was able to use the device after restart and it took a couple of hours to clear the 'calculating' status on the volume/share screen. The device continued to work until later that evening when I checked on it and found the device unresponsive. Error message was as described. All lights were on (steady) including the ACT.
I tried to reboot and got the same message on startup. I was unable to ping the machine or connect.
I tried the reinstallOS from the boot menu. It did the reinstall but it froze at the same point in boot up.
The next thing I tried was to boot it up with no network connection (i.e. unplugged everything except power).
This actually worked and the device sat there quite happily saying no-ip with all lights flashing.
I reconnected the network cable, it got an IP address but it froze with the error message 354 in under a minute. I was able to ping the machine before it froze.
I tried this a couple of times with varying levels of time 'on' before freezing again.
At no point until this morning was I able to access the admin panel.
+++++++++++++
After your email:
This morning I booted again (without the network cable) and continually pinged the device. Roughly 1 min after boot (and the no-ip message) I connected the cable, it got an IP and I was able to ping the device.
I quickly tried the admin page and was able to log in. However all I got was the main menu, it wouldn't show logs, status, performance or anything.
Within 1 minute the device then froze again.
I've tried this once more but with no success.
I also tried leaving the device with no network cable connected for longer, however eventually it froze again (just too longer to freeze than when the cable was connected)
++++++++++++++ Support mode:
I tried support mode and it shows the following with no network cable connected:
DebugMode[57550]
0.0.0.0
and with network cable connected
DebugMode[57550]
192.168.0.106
all lights (including ACT) are steady, not blinking.
I am able to ping the device ok.
I've not been able to access any system logs I'm afraid.
____________________________________________________________________
Related Content
NETGEAR Academy

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