NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
System: ReadyNASOS service or process was restarted.
I have a ReadyNAS Pro 6 running Firmware 6.10.3
Recently the system started resyncing every few hours. From the System -> Logs tab, using the web interface:
May 22, 2020 02:58:01 PM
System: ReadyNASOS background service started.
May 22, 2020 02:58:00 PM
Volume: Resyncing started for Volume data.
May 22, 2020 02:57:57 PM
System: ReadyNASOS service or process was restarted.
May 22, 2020 02:12:04 PM
System: Service protocol anti-virus-sche-scan is disabled.
May 22, 2020 02:12:04 PM
System: Service protocol Antivirus is disabled.
May 22, 2020 01:17:32 PM
Volume: Resyncing started for Volume data.
May 22, 2020 01:17:32 PM
System: ReadyNASOS background service started.
May 22, 2020 01:17:29 PM
System: ReadyNASOS service or process was restarted.
May 22, 2020 10:45:11 AM
System: ReadyNASOS background service started.
May 22, 2020 10:45:11 AM
Volume: Resyncing started for Volume data.
May 22, 2020 10:45:07 AM
System: ReadyNASOS service or process was restarted.
May 22, 2020 10:07:40 AM
System: ReadyNASOS background service started.
May 22, 2020 10:07:40 AM
Volume: Resyncing started for Volume data.
May 22, 2020 10:07:37 AM
System: ReadyNASOS service or process was restarted.
May 22, 2020 08:09:08 AM
System: Antivirus scanner definition file was updated to 59.25820.
May 22, 2020 07:48:01 AM
System: ReadyNASOS background service started.
May 22, 2020 07:48:01 AM
Volume: Resyncing started for Volume data.
All the disks appear to be okay (all green) at the Web UI: System -> Performance -> Status.
The CPU/System fans are working 1757/1430 RPM, and the CPU/System are at 38C/54C
Downloading the log .zip file, I found the following in "kernel.log". The system reboots, but I can't figure out why:
May 22 10:44:53 library kernel: eth0: network connection up using port A
May 22 10:44:53 library kernel: interrupt src: MSI
May 22 10:44:53 library kernel: speed: 1000
May 22 10:44:53 library kernel: autonegotiation: yes
May 22 10:44:53 library kernel: duplex mode: full
May 22 10:44:53 library kernel: flowctrl: symmetric
May 22 10:44:53 library kernel: role: slave
May 22 10:44:53 library kernel: tcp offload: enabled
May 22 10:44:53 library kernel: scatter-gather: enabled
May 22 10:44:53 library kernel: tx-checksum: enabled
May 22 10:44:53 library kernel: rx-checksum: enabled
May 22 10:44:53 library kernel: rx-polling: enabled
May 22 10:44:53 library kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
May 22 10:45:17 library kernel: nfsd: last server has exited, flushing export cache
May 22 10:45:17 library kernel: NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory
May 22 10:45:17 library kernel: NFSD: starting 90-second grace period (net ffffffff88d70240)
-- Reboot --
May 22 13:16:58 library kernel: Initializing cgroup subsys cpuset
May 22 13:16:58 library kernel: Initializing cgroup subsys cpu
May 22 13:16:58 library kernel: Initializing cgroup subsys cpuacct
May 22 13:16:58 library kernel: Linux version 4.4.190.x86_64.1 (root@blocks) (gcc version 8.3.0 (Debian 8.3.0-6) ) #1 SMP Mon Oct 28 01:55:46 UTC 2019
May 22 13:16:58 library kernel: Command line: initrd=initrd.gz reason=normal BOOT_IMAGE=kernel
May 22 13:16:58 library kernel: KERNEL supported cpus:
May 22 13:16:58 library kernel: Intel GenuineIntel
May 22 13:16:58 library kernel: Disabled fast string operations
May 22 13:16:58 library kernel: x86/fpu: Supporting XSAVE feature 0x01: 'x87 floating point registers'
May 22 13:16:58 library kernel: x86/fpu: Supporting XSAVE feature 0x02: 'SSE registers'
May 22 13:16:58 library kernel: x86/fpu: Enabled xstate features 0x3, context size is 576 bytes, using 'standard' format.
May 22 13:16:58 library kernel: e820: BIOS-provided physical RAM map:
May 22 13:16:58 library kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009cbff] usable
May 22 13:16:58 library kernel: BIOS-e820: [mem 0x000000000009cc00-0x000000000009ffff] reserved
May 22 13:16:58 library kernel: BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
May 22 13:16:58 library kernel: BIOS-e820: [mem 0x0000000000100000-0x00000000afeaffff] usable
May 22 13:16:58 library kernel: BIOS-e820: [mem 0x00000000afeb0000-0x00000000afebdfff] ACPI data
May 22 13:16:58 library kernel: BIOS-e820: [mem 0x00000000afebe000-0x00000000afeeffff] ACPI NVS
May 22 13:16:58 library kernel: BIOS-e820: [mem 0x00000000afef0000-0x00000000afefffff] reserved
May 22 13:16:58 library kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
May 22 13:16:58 library kernel: BIOS-e820: [mem 0x00000000ffb00000-0x00000000ffffffff] reserved
May 22 13:16:58 library kernel: BIOS-e820: [mem 0x0000000100000000-0x000000024fffffff] usable
May 22 13:16:58 library kernel: NX (Execute Disable) protection: active
Any ideas what could be wrong? Hardware failure? I'd be happy to provide any additional information.
Thanks
13 Replies
Replies have been turned off for this discussion
How much memory is installed in the NAS?
Perhaps try disabling the antivirus software, and see if that makes any difference.
I've got 8 GB or RAM installed. There must be a way to look this up in the logs (also couldn't see this in the web UI), but by ssh-ing into the ReadyNAS:
# free -mh
total used free shared buffers cached
Mem: 7.8G 697M 7.1G 5.3M 4.3M 344M
-/+ buffers/cache: 348M 7.4G
Swap: 1.5G 0B 1.5G
I did disable the Antivirus earlier today (saw some posts on similar topics, where you suggested this), but the rebooting & resyncing continues.
Thanks
Retired_Member wrote:
I've got 8 GB of RAM installed.
Thx. I was asking because some folks with the stock 1 GB have started to run out. Shipping OS-6 ReadyNAS all have at least 2 GB, and you of course are well over that.
The thought about AV was similarly motivated - wondering if you were running out of resources. That isn't likely to be the cause of your issue.
What disks are you using?
Have you looked through the logs for disk events (insertions/removal)? Maybe use journalctl since you have ssh enabled. smartctl -x might also give some clues on the disks (especially if yours support the error logging). FWIW, I had some WD60EFRX drives that started throwing UNC errors that showed up in smartctl -x, but not in the smart stats.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
