This topic has been marked solved and closed to new posts due to inactivity. We hope you'll join the conversation by posting to an open topic or starting a new one.
I have an RN314 with an EDA500 connected. I recently updated to 6.6.1 and the update seemed to be alright and the NAS restarted without problems. Then I also had some work done on my house and our power was tripped, and even though the UPS was screaming, nobody shut the nas down so it was just powered off after a while.
After that, the NAS has had trouble booting. It kept getting stuck at various percentages and when it did boot, I got corrupted journal messages and then no space left on device messages. The NAS behaved a little better if I disconnected the EDA500, but it still eventually showed the the same error messages.
After one boot I noticed an error in the logs that looked like it could be disk failures, but on other forums people seeing that message suggested changing the sata cables for a drive. So I have tried replacing the esata cable to my EDA500, and I've even started an RMA process for one of the disks in the EDA500 because removing it seems to reduce the problems as well.
I don't even know how I ended up on one of the threads about the antivirus app no longer being available on 6.6.1 because of the AV changes, but it did get me thinking because I noticed the /var/lib/clamav folder and it was one of the bigger folders at over 200MB. I have now disabled the AV and suddenly no more journal corruption messages or no space left on device messages either and no other strange errors appearing when I do dmesg | tail now.
I'm not that pleased that I have to disable AV, but in order to keep the NAS running it's my only option.
Engineering has identified a cause for the issues reported on the community. The root cause is that ClamAV uses up the /tmp directory space when scanning files transferred over SAMBA. The symptom is especially acute in models that have small RAM and low CPU bandwidth.
A possible fix has been identified and is being tested.
There may be other issues. Engineering is still in the process of investigating.
NETGEAR may release a beta version of the software next week here on the community site.
I have the same on my RN104. Without AV enabled all is fine, enabling AV leads to situation where the box is supersnailing along. Yes, that is since upgrading to 6.6.1. There seem to be some room for improvements. Thank you very much.
Engineering has identified a cause for the issues reported on the community. The root cause is that ClamAV uses up the /tmp directory space when scanning files transferred over SAMBA. The symptom is especially acute in models that have small RAM and low CPU bandwidth.
A possible fix has been identified and is being tested.
There may be other issues. Engineering is still in the process of investigating.
NETGEAR may release a beta version of the software next week here on the community site.
