NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
RN204 crashes shortly after boot
For a couple days, I've been having the issue where deleting large files / lots of files results in a crash where the panel will either display "__out_of_memory + 354" or the RN204 will just become unresponsive with a blank panel. I have to unplug it and then plug it back in in order to get it to restart.
I'm guessing that the cause of this issue is that the system seems to be batching changes to shapshots and it seems to be caused if there are too many changes batched before the actual changes are made to the snapshots. If I wait until the snapshot usage size changes before deleting more files, it doesn't seem to happen.
Now my RN204 is in a state where it's unusable in the normal boot mode (read/write). I'm guessing this is because the snapshot pruner is trying to delete snapshots and this is inducing the above crash. The system works fine in the readonly boot mode, but doesn't stay responsive for long enough in the boot for me to get to the admin page to raise the snapshot pruning percentage to stop the issue from happening.
So here are my questions:
Is there any easy way for me to get this system working correctly without doing a factory default?
If I use the OS reinstall mode, is that likely to fix the issue? Will I lose data? Is it likely that this would result in the system not starting at all any more, even in readonly mode? Is it possible that doing this would result in not then being able to do a factory default? eg. Could I brick my system?
Is there a fix in the works for the large / many file deletion crash?
Assuming I do a factory default, is there some way I can avoid this problem happening again. It didn't seem to occur until the disk got relatively full. If I reduce the snapshot pruning percentage to say 80% or even 70%, and the disk never gets more than 70% or 80% full, will that likely prevent the issue from happening?
Is the cause for the issue known? If so, what is it and how can I avoid it?
Thanks in advance for any advice anyone could provide. In the meantime, I am copying data off the system under the assumption I will be doing a factory default.
Thanks,
Ian
EDIT: I should mention that I'm running firmware 6.5.1 and that this RN204 has 4 6TB disks in it with XRAID2 for about 16TB of storage, and this RN204 is mostly being used to store files that are about 2GB in size each although there are a few very large files around 100GB in size.
My guess is that an OS reinstall won't help. Your issue seems triggered by your volume state, and an OS reinstall doesn't change that.
A factory default destroys the data volume, so that will certainly work.
You could of course try support (though they likely will charge).
7 Replies
Replies have been turned off for this discussion
I understand that I asked quite a few questions in my post. A question in particular that I think would help me at this moment would be about the OS reinstall mode; does anyone think that using the OS reinstall mode will fix this? If that doesn't work, I'm just going to do a factory default anyway, which if I understand correctly is more complete than an OS reinstall.
I don't necessairly need all of my questions answered, but any response at all would be appreciated. I'm gonna be doing the OS reinstall in about 20 minutes unless googling finds some reason why I shouldn't. Gonna try backing up my settings first.My guess is that an OS reinstall won't help. Your issue seems triggered by your volume state, and an OS reinstall doesn't change that.
A factory default destroys the data volume, so that will certainly work.
You could of course try support (though they likely will charge).
Thanks for the response. I think I'm gonna try an OS reinstall anyway and then increase the snapshot pruning percent to 99% and slowly back it down 1% at a time until (hopefully) the issue doesn't occur anymore. I'll post here if I find a solution.
Edit: Actually, I just realized that won't work, since the default pruning percentage is 95% and my current pruning percentage is 96%, so I still won't be able to get to the admin page to change it. Factory default it is. Thanks for the response.
Hi everyone, just wanted to give everyone an update and ask a few questions about this issue. I backed up my data and did a factory default and came out without having lost anything.
This time around I've disabled Bit rot protection and compression on all of my shares, and I've noticed that although the data volume is relatively full, I've not had a single issue with it. Is it possible that this issue is being caused by either (or both) of these options? I would think that compression/decompression would be memory intensive, and/or possibly some of the functions that go along with the CoW functions.
Do we know why this issue happens? Is there a fix in the works? I've found that the RAM for my unit is on the board itself, so it can't be upgraded. If I switched to a unit with more RAM would I be less likely to run into this issue? I really like the ReadyNAS OS and the overall quality of this product and would be willing to switch to a more expensive unit like a RN316, if it would likely aleviate this issue. Also, that's an x86 build, where as the RN204 is ARM, so that may also be a factor.
Any sort of response, even speculation would be appreciated. It would be cool if Netgear could acknowledge or provide details about the cause or any possible fix for this.
ibell63 wrote:
This time around I've disabled Bit rot protection and compression on all of my shares, and I've noticed that although the data volume is relatively full, I've not had a single issue with it. Is it possible that this issue is being caused by either (or both) of these options? I would think that compression/decompression would be memory intensive, and/or possibly some of the functions that go along with the CoW functions.
Certtainly CoW (particularly snapshots) can create performance issues when the volume is too full. Compression/Decompression is of course also going to increase memory and reduce performance.
I'm thinking that more users enable bit-rot protection than use compression, so compression might be a more likely cause.
Thanks for the response. I'm going to continue using it as is and I'll post here if I have issues as the drive fills up. I'm certainly not going to fill it up anymore than 95% full, but I was dissappointed to have such serious issues with the volume when it was only ~85% full last time.
Is there a recommended amount of free space?
Edit: I should note that the volume is currently 87% full with no issues.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
