NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Richard-P
Mar 29, 2021Aspirant
Readynas 104 - Very slow, almost unusable
Hi, I'm using a readynas 104 with 6.10.4 Hotfix 1 OS. It's extremely slow, almost unusable and I can't get any work done, which is a real problem. The latest log says 'System: ReadyNASOS backgroun...
StephenB
Mar 29, 2021Guru - Experienced User
Richard-P wrote:I'm using a readynas 104 with 6.10.4 Hotfix 1 OS.
It's extremely slow, almost unusable and I can't get any work done, which is a real problem.
Start by downloading the full log zip file from the log page. Then look in disk-info.log and see if there are disk errors in the smart stat counts.
Also, did the speed drop recently? Or has it been slow for a while?
Did you try simply rebooting the NAS?
Richard-P
Mar 29, 2021Aspirant
Hi Stephen,
Thanks for replying so quickly.
There doesn't appear to be any disk errors.
The speed issue started on Friday . Until then there hasn't been any issues with it.
I've tried re-booting the nas a coule of times but it doesn't help, unfortunately.
Thanks,
R
- rn_enthusiastMar 29, 2021Virtuoso
Hi Richard-P
Take that log zip file you downloaded and upload that to Google drive, Dropbox or similar. Then PM me a link to download it and I can take a look for you, in those logs. Might be able to see what is going on.
Cheers
- Richard-PMar 29, 2021Aspirant
That's really good of you, thanks.
- rn_enthusiastMar 30, 2021Virtuoso
Hi Richard-P
Thanks for the logs.
Your unit is running into an "out of memory" condition over and over, every 10-20 mins. This is obviously a problem. The odd thing is, that this seems related to clam-av (the antivirus service), which was disabled on the RN100 series a while back.
Mar 28 12:50:34 ReadyNAS kernel: Out of memory: Kill process 4975 (clamd) score 1411 or sacrifice child Mar 28 12:50:34 ReadyNAS kernel: Killed process 4975 (clamd) total-vm:691048kB, anon-rss:210748kB, file-rss:436kB Mar 28 13:07:08 ReadyNAS kernel: enclosure_monit invoked oom-killer: gfp_mask=0x24201ca, order=0, oom_score_adj=-1000 Mar 28 13:07:09 ReadyNAS kernel: enclosure_monit cpuset=/ mems_allowed=0 Mar 28 13:07:09 ReadyNAS kernel: CPU: 0 PID: 2524 Comm: enclosure_monit Tainted: P O 4.4.190.armada.1 #1 Mar 28 13:07:09 ReadyNAS kernel: Hardware name: Marvell Armada 370/XP (Device Tree) Mar 28 13:07:09 ReadyNAS kernel: [<c0015270>] (unwind_backtrace) from [<c001173c>] (show_stack+0x10/0x18) Mar 28 13:07:09 ReadyNAS kernel: [<c001173c>] (show_stack) from [<c03849d0>] (dump_stack+0x78/0x9c) Mar 28 13:07:09 ReadyNAS kernel: [<c03849d0>] (dump_stack) from [<c00d5e20>] (dump_header+0x4c/0x1b4) Mar 28 13:07:09 ReadyNAS kernel: [<c00d5e20>] (dump_header) from [<c00a09a0>] (oom_kill_process+0xd0/0x45c) Mar 28 13:07:09 ReadyNAS kernel: [<c00a09a0>] (oom_kill_process) from [<c00a10b0>] (out_of_memory+0x310/0x374) Mar 28 13:07:09 ReadyNAS kernel: [<c00a10b0>] (out_of_memory) from [<c00a49d4>] (__alloc_pages_nodemask+0x6e0/0x7dc) Mar 28 13:07:09 ReadyNAS kernel: [<c00a49d4>] (__alloc_pages_nodemask) from [<c009faa4>] (filemap_fault+0x344/0x464) Mar 28 13:07:09 ReadyNAS kernel: [<c009faa4>] (filemap_fault) from [<c01548a0>] (ext4_filemap_fault+0x2c/0x44) Mar 28 13:07:09 ReadyNAS kernel: [<c01548a0>] (ext4_filemap_fault) from [<c00ba4c4>] (__do_fault+0x60/0xdc) Mar 28 13:07:09 ReadyNAS kernel: [<c00ba4c4>] (__do_fault) from [<c00bd1a0>] (handle_mm_fault+0x4e0/0xc04) Mar 28 13:07:09 ReadyNAS kernel: [<c00bd1a0>] (handle_mm_fault) from [<c0017cb8>] (do_page_fault+0x134/0x2b0) Mar 28 13:07:09 ReadyNAS kernel: [<c0017cb8>] (do_page_fault) from [<c0009368>] (do_PrefetchAbort+0x34/0x9c) Mar 28 13:07:09 ReadyNAS kernel: [<c0009368>] (do_PrefetchAbort) from [<c00125dc>] (ret_from_exception+0x0/0x24) Mar 28 13:07:09 ReadyNAS kernel: Exception stack(0xdb277fb0 to 0xdb277ff8)
This service shouldn't even appear in the processes list, but it does.S root 3471 1 3471 0 1 80 0 8 2601 pipe_w 04:17 ? 00:00:14 /usr/bin/freshclam --quiet D root 3477 3471 3477 2 1 80 0 64756 175427 wait_o 04:18 ? 00:08:42 /usr/bin/freshclam --quiet R root 8502 1 8502 14 1 98 18 230996 158682 - 11:16 ? 00:02:26 /usr/sbin/clamd --foreground=true --config-file=/etc/clamav/clamd.conf
It is enabled on your NAS, in the default services list:
ANTIVIRUS=1 ANTIVIRUS_SCHE_SCAN=0
Something is amiss with this. I don't get how the clam daemon is running at this point, unless you started it yourself? Do you use SSH and command line (CLI) on this NAS? You are on 6.10.4 and have been updating regularly:
[2019/07/13 15:10:30 UTC] Updated from ReadyNASOS 6.10.0 (ReadyNASOS) to 6.10.1 (ReadyNASOS). [2020/03/07 09:06:53 UTC] Updated from ReadyNASOS 6.10.1 (ReadyNASOS) to 6.10.2 (ReadyNASOS). [2020/03/18 08:02:56 UTC] Updated from ReadyNASOS 6.10.2 (ReadyNASOS) to 6.10.3 (ReadyNASOS). [2020/12/19 09:37:52 UTC] Updated from ReadyNASOS 6.10.3 (ReadyNASOS) to 6.10.4 (ReadyNASOS). [2021/01/03 14:22:58 UTC] Updated from ReadyNASOS 6.10.4 (ReadyNASOS) to 6.10.4 (ReadyNASOS). [2021/03/27 09:26:47 UTC] Updated from ReadyNASOS 6.10.4 (ReadyNASOS) to 6.10.4 (ReadyNASOS).
Netgear disabled the AV service on the RN100 series NAS, due to resource and performance issues and I think that happened around 6.10.0. So... how your AV service is running, I don't know :) But that is your performance problem right there. You need to disable that AV service. You can do it from the CLI:
systemctl stop clamav-daemon
Check it is stopped:
systemctl status clamav-daemon
You also need to turn it off in the /etc/default/services file (set it to "0"), so that it will not start again upon next NAS reboot.
Do you know how to access the NAS CLI over SSH, in order to fix this?
Cheers
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!