Readynas 104 won't boot. Error 354 out_of_memory. After upgrade to 6.4.1 #26323717

---

corinbishop wrote:

did a memory test from boot menu. fails at 00:00:01 
I'm guessing that's not good?

---

Not good.

I think you should contact support (likely an RMA is in your future).

Hi thenorthface,

I have sent you a PM.

The two examples of this problem in this thread are the first I've seen of this.

Generally OOM would suggest either running too much on the NAS or a memory leak.

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.
____________________________________________________________________

---

kohdee wrote:

Could you possibly send me a picture of the LCD with that error message? I'm compiling a list of LCD error messages since 6.4.1 and putting them on the KB.

 

Out of memory on a RN104 is really easy to do, being that RN104 has 512M RAM and 256M of it is used by the system to boot, but if you're failing instantly in the boot, it does sound like bad RAM, which is only replacable by RMA of chassis 
If you have a spare disk to test on and it works out fine, then it might be something software related. 

---

sure. pic attached. 

(note that it's currently error 390, previously it was 354 but I've not seen 354 come up for quite a while)

I'm thinking it's possible a RAM problem. Just seems strange it only appeared after upgrade to 641.  Depends on the scope of the upgrade perhaps. It's non-downgradable so perhaps there's a change to the lower level of the hardware drivers/software/firmware etc. 

I have done the mem test again and it does fail at 00:00:01 !!!

Nothing back from netgear in the last few days after I sent them a crash dump they gathered via tech support mode. 

I think at this stage an RMA would be the best option to rule out hardware. I do have spare disks but I'm not convinced that a single disk with a small amount of data is really going to be conclusive as it could still be a problem with the larger file structure. The only one unusual thing I have is I had upgraded a failed disk recently from a 3TB to 4TB with a view to changing all the disks to eventually increasing the volume size XRAID styleee...

So it's gone from 3TB x4 to, 4TB+3TBx3.

It shouldn't really make any difference with xraid but who knows, it might have been a situation that was not looked at in the new firmware.

Hi folks. 

Support have decided to disable quotas and see how I go. So far, so good. System is stable and I'm giving the unit a good thrashing - starting with syncing all the data changes Id made on the backup unit since the failure. The comparison alone will take a while.

If anyone else can suggest any other tests I could give it then let me know.

cheers

---

LifeVibes wrote:

We have the same problem with one of our NAS here at work, so it’s not the only one.
So good to hear there might be workarounds and that it doesn’t seem to be a HW (memory) problem. Found it already a bit too coincidental that the mem failure would’ve just happened after fw upgrade. So prolly will save us RMA hassle.
Luckily the NAS was only rarely used until now for some less important backups. But it will normally get also another purpose in the very near future so would like to get it fully working again soon.

Symptoms are (almost exactly) the same as described above:
After fw upgrade from 6.2.5 to 6.4.1 system became unusable, normal boot never finishes and results in an out of memory error 354 after half an hour or so. Only hard power off (unplug) possible.
RAIDar sees the NAS booting "System starting up...", and then after a while "Management service is offline", and then after about 20 min it disappears and then shortly after also the OOM 354 error is displayed on the NAS.
During the period where it shows "Management service is offline" it shows the option buttons: Admin Page, Browse, Locate, Download Logs, Diagnostics
All of the buttons seem to work ok for a while, except for Admin Page:
Not able to access admin page: After supplying user/pw "Connecting to ReadyNAS Admin Page..." and then after a while "ReadyNAS Admin Page is offline."
Can perform locate (LEDs on), shares seem to be accessible for a short while and I can download logs a few times and Diagnostics are ok.
 
Tried several things:
Mem test displays 00:00:01 immediately after launching it and staying there forever. Hard reboot needed (power unplug). Don’t know if this display is pattern #, test time or error #.
Tried USB OS (re)install and OS reinstall from Boot Menu, didn’t help.

Tried the boot without network cable, as above, but has the same OOM result. So this is slightly different from above.
What does kinda work is booting in "Volume read only" mode from boot menu.
In this mode the NAS seems to boot and work normal, except for the fact you can’t write to it or delete anything of course and that the calculation (of used/free space) doesn’t seem to end.
Was able to do full backup (1.5T) and later a full CRC check of the backed up data on NAS. NAS was on for about a week like this and no problems.
Also scrub, balance and defrag don’t give errors, altho wonder how this can really work on a RO volume.

 

Yesterday tried to flash 6.4.2 RC1 but same problem still exists. Except that the error # now also is 390 instead of 354.
Volume RO is still the only mode where we can still do something.
There are no quota on the shares, so cant disable that. :(

Config:
RN10400
2 x 4TB (X-raid Raid-1) 60% Free
very basic config:
Services: SMB, HTTP, HTTPS (AV disabled)
no apps
no quota
besides admin only one extra user.
3 shares: one with about 1.5T data with snapshots and bit rot enabled. Only 36 snapshots, so not really a large number. Permissions: admin + user.
2 test ones, currently empty, (snapshots disabled, bit rot enabled). Permissions: anonymous.

---

Your situation is identical to mine so I suspect something else has been done that's not been detailed. Unless it's specificly this special version of 642+quotas off?

Can you send me your logs (see the Sending Logs link in my sig)? There will be some information in that, that will help with answering that question.

Also the Readynas 104, having trouble with the 354 out of memory message. Thought it was because i was racking up the date on my NAS but it states there is still like 4 tb of space.

I do have 4x4 tb WD Red installed. 

Anyone have any news if there is a fix yet.

Kind regards.