I have a Readynas Pro 4 (modelname RNDP4000). I have four 3TB disks and had the readynas running good for about 2 years.
About two weeks ago the readynas started to crash. After a fresh restart it responds to ping but when I try to access a shared folder it stops responding to ping and I am unable to access frontview or the shared drives.
I tried to understand the logs that I downloaded from frontview but I can not see why the crash happened.
Here are some info from the httpd_error.log:
[Wed Jan 21 12:01:31 2015] [notice] caught SIGTERM, shutting down [Wed Jan 21 12:02:39 2015] [warn] RSA server certificate CommonName (CN) `192.168.1.106' does NOT match server name!? [Wed Jan 21 12:02:41 2015] [warn] RSA server certificate CommonName (CN) `192.168.1.106' does NOT match server name!? [Wed Jan 21 12:02:43 2015] [warn] RSA server certificate CommonName (CN) `192.168.1.106' does NOT match server name!? [Wed Jan 21 12:02:43 2015] [notice] Apache/2.2.6 (Debian) mod_ssl/2.2.6 OpenSSL/0.9.8c DAV/2 mod_apreq2-20051231/2.6.0 mod_perl/2.0.2 Perl/v5.8.8 configured -- resuming normal operations
Here are some info from the system.log. I think the crash happened in this time-period:
Jan 21 11:43:24 NAS kernel: ata6.00: configured for UDMA/133 Jan 21 11:43:24 NAS kernel: ata6: EH complete Jan 21 11:43:24 NAS kernel: EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: acl,user_xattr,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv1 Jan 21 11:43:24 NAS exportfs[2151]: /etc/exports [1]: Neither 'subtree_check' or 'no_subtree_check' specified for export "*:/IPCAM". Assuming default behaviour ('no_subtree_check'). NOTE: this default has changed since nfs-utils version 1.0.x Jan 21 11:43:24 NAS exportfs[2151]: /etc/exports [2]: Neither 'subtree_check' or 'no_subtree_check' specified for export "*:/backup". Assuming default behaviour ('no_subtree_check'). NOTE: this default has changed since nfs-utils version 1.0.x Jan 21 11:43:24 NAS exportfs[2151]: /etc/exports [3]: Neither 'subtree_check' or 'no_subtree_check' specified for export "*:/documents". Assuming default behaviour ('no_subtree_check'). NOTE: this default has changed since nfs-utils version 1.0.x Jan 21 11:43:24 NAS exportfs[2151]: /etc/exports [4]: Neither 'subtree_check' or 'no_subtree_check' specified for export "*:/media". Assuming default behaviour ('no_subtree_check'). NOTE: this default has changed since nfs-utils version 1.0.x Jan 21 11:43:24 NAS exportfs[2151]: /etc/exports [5]: Neither 'subtree_check' or 'no_subtree_check' specified for export "*:/software". Assuming default behaviour ('no_subtree_check'). NOTE: this default has changed since nfs-utils version 1.0.x Jan 21 11:43:24 NAS exportfs[2151]: /proc/fs/nfs/exports:1: unknown keyword "test-client-(rw" Jan 21 11:43:24 NAS rpc.statd[2155]: Version 1.1.2 Starting Jan 21 11:43:24 NAS sm-notify[2157]: sm-notify running as root. chown /var/lib/nfs/sm to choose different user Jan 21 11:43:24 NAS Backgrounding to notify hosts... Jan 21 11:43:24 NAS rpc.statd[2155]: statd running as root. chown /var/lib/nfs/sm to choose different user Jan 21 11:43:24 NAS kernel: svc: failed to register lockdv1 RPC service (errno 97). Jan 21 11:43:24 NAS kernel: NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory Jan 21 11:43:25 NAS kernel: NFSD: starting 90-second grace period Jan 21 11:43:34 NAS syslogd 1.4.1#18: restart. Jan 21 11:43:34 NAS ifplugd(eth1)[2568]: client: apache-ssl: Could not reliably determine the server's fully qualified domain name, using 192.168.1.239 for ServerName Jan 21 11:43:34 NAS ifplugd(eth1)[2568]: client: (98)Address already in use: make_sock: could not bind to address 0.0.0.0:80 Jan 21 11:43:34 NAS ifplugd(eth1)[2568]: client: no listening sockets available, shutting down Jan 21 11:43:34 NAS ifplugd(eth1)[2568]: client: Unable to open logs Jan 21 11:43:36 NAS ifplugd(eth1)[2568]: client: apache-ssl: Could not reliably determine the server's fully qualified domain name, using 192.168.1.239 for ServerName Jan 21 11:43:36 NAS ifplugd(eth1)[2568]: client: (98)Address already in use: make_sock: could not bind to address 0.0.0.0:80 Jan 21 11:43:36 NAS ifplugd(eth1)[2568]: client: no listening sockets available, shutting down Jan 21 11:43:36 NAS ifplugd(eth1)[2568]: client: Unable to open logs Jan 21 11:43:36 NAS RAIDiator: nic.agent: "nice -n 5 /usr/sbin/apache-ssl -f /etc/frontview/apache/httpd.conf" failed to start. Jan 21 11:43:37 NAS exportfs[2830]: /etc/exports [1]: Neither 'subtree_check' or 'no_subtree_check' specified for export "*:/IPCAM". Assuming default behaviour ('no_subtree_check'). NOTE: this default has changed since nfs-utils version 1.0.x Jan 21 11:43:37 NAS ifplugd(eth1)[2568]: client: exportfs: /etc/exports [1]: Neither 'subtree_check' or 'no_subtree_check' specified for export "*:/IPCAM". Jan 21 11:43:37 NAS ifplugd(eth1)[2568]: client: Assuming default behaviour ('no_subtree_check'). Jan 21 11:43:37 NAS ifplugd(eth1)[2568]: client: NOTE: this default has changed since nfs-utils version 1.0.x Jan 21 11:43:37 NAS exportfs[2830]: /etc/exports [2]: Neither 'subtree_check' or 'no_subtree_check' specified for export "*:/backup". Assuming default behaviour ('no_subtree_check'). NOTE: this default has changed since nfs-utils version 1.0.x Jan 21 11:43:37 NAS ifplugd(eth1)[2568]: client: exportfs: /etc/exports [2]: Neither 'subtree_check' or 'no_subtree_check' specified for export "*:/backup". Jan 21 11:43:37 NAS ifplugd(eth1)[2568]: client: Assuming default behaviour ('no_subtree_check'). Jan 21 11:43:37 NAS exportfs[2830]: /etc/exports [3]: Neither 'subtree_check' or 'no_subtree_check' specified for export "*:/documents". Assuming default behaviour ('no_subtree_check'). NOTE: this default has changed since nfs-utils version 1.0.x Jan 21 11:43:37 NAS ifplugd(eth1)[2568]: client: NOTE: this default has changed since nfs-utils version 1.0.x Jan 21 11:43:37 NAS exportfs[2830]: /etc/exports [4]: Neither 'subtree_check' or 'no_subtree_check' specified for export "*:/media". Assuming default behaviour ('no_subtree_check'). NOTE: this default has changed since nfs-utils version 1.0.x Jan 21 11:43:37 NAS exportfs[2830]: /etc/exports [5]: Neither 'subtree_check' or 'no_subtree_check' specified for export "*:/software". Assuming default behaviour ('no_subtree_check'). NOTE: this default has changed since nfs-utils version 1.0.x Jan 21 11:43:37 NAS ifplugd(eth1)[2568]: client: exportfs: /etc/exports [3]: Neither 'subtree_check' or 'no_subtree_check' specified for export "*:/documents". Jan 21 11:43:37 NAS ifplugd(eth1)[2568]: client: Assuming default behaviour ('no_subtree_check'). Jan 21 11:43:37 NAS ifplugd(eth1)[2568]: client: NOTE: this default has changed since nfs-utils version 1.0.x Jan 21 11:43:37 NAS ifplugd(eth1)[2568]: client: exportfs: /etc/exports [4]: Neither 'subtree_check' or 'no_subtree_check' specified for export "*:/media". Jan 21 11:43:37 NAS ifplugd(eth1)[2568]: client: Assuming default behaviour ('no_subtree_check'). Jan 21 11:43:37 NAS ifplugd(eth1)[2568]: client: NOTE: this default has changed since nfs-utils version 1.0.x Jan 21 11:43:37 NAS ifplugd(eth1)[2568]: client: exportfs: /etc/exports [5]: Neither 'subtree_check' or 'no_subtree_check' specified for export "*:/software". Jan 21 11:43:37 NAS ifplugd(eth1)[2568]: client: Assuming default behaviour ('no_subtree_check'). Jan 21 11:43:37 NAS ifplugd(eth1)[2568]: client: NOTE: this default has changed since nfs-utils version 1.0.x Jan 21 11:43:37 NAS ifplugd(eth1)[2568]: client: Running ntpd to synchronize clock. Jan 21 11:43:37 NAS chronyd[2834]: chronyd version 1.24 starting Jan 21 11:43:37 NAS chronyd[2834]: Initial txc.tick=10000 txc.freq=0 (0.00000000) txc.offset=0 => hz=100 shift_hz=7 Jan 21 11:43:37 NAS chronyd[2834]: set_config_hz=0 hz=100 shift_hz=7 basic_freq_scale=1.28000000 nominal_tick=10000 slew_delta_tick=833 max_tick_bias=1000 Jan 21 11:43:37 NAS chronyd[2834]: Linux kernel major=2 minor=6 patch=37 Jan 21 11:43:37 NAS chronyd[2834]: calculated_freq_scale=1.00000000 freq_scale=1.00000000 Jan 21 11:43:37 NAS ifplugd(eth1)[2568]: Program executed successfully. Jan 21 11:43:39 NAS RAIDiator: Systemet är aktivt. Jan 21 11:43:40 NAS avahi-daemon[3092]: Found user 'avahi' (UID 20) and group 'avahi' (GID 20). Jan 21 11:43:40 NAS avahi-daemon[3092]: Successfully dropped root privileges. Jan 21 11:43:40 NAS avahi-daemon[3092]: avahi-daemon 0.6.23 starting up. Jan 21 11:43:40 NAS avahi-daemon[3092]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns! Jan 21 11:43:40 NAS avahi-daemon[3092]: Loading service file /etc/avahi/services/readynas.service. Jan 21 11:43:40 NAS avahi-daemon[3092]: Loading service file /etc/avahi/services/transmission.service. Jan 21 11:43:40 NAS chronyd[2834]: System's initial offset : 0.225373 seconds slow of true (slew) Jan 21 11:43:40 NAS avahi-daemon[3092]: Joining mDNS multicast group on interface eth1.IPv4 with address 192.168.1.239. Jan 21 11:43:40 NAS avahi-daemon[3092]: New relevant interface eth1.IPv4 for mDNS. Jan 21 11:43:40 NAS avahi-daemon[3092]: Network interface enumeration completed. Jan 21 11:43:40 NAS avahi-daemon[3092]: Registering new address record for 192.168.1.239 on eth1.IPv4. Jan 21 11:43:40 NAS avahi-daemon[3092]: Registering HINFO record with values 'X86_64'/'LINUX'. Jan 21 11:43:40 NAS ipwatchd[3096]: IPwatchD started Jan 21 11:43:41 NAS avahi-daemon[3092]: Server startup complete. Host name is NAS.local. Local service cookie is 3367287522. Jan 21 11:43:41 NAS avahi-daemon[3092]: Service "NAS (Transmission)" (/etc/avahi/services/transmission.service) successfully established. Jan 21 11:43:41 NAS avahi-daemon[3092]: Service "ReadyNAS Discovery [NAS]" (/etc/avahi/services/readynas.service) successfully established. Jan 21 12:01:27 NAS shutdown[4417]: shutting down for system halt Jan 21 12:01:27 NAS init: Switching to runlevel: 0 Jan 21 12:01:28 NAS kernel: ata1.00: configured for UDMA/133 Jan 21 12:01:28 NAS kernel: ata1: EH complete Jan 21 12:01:28 NAS kernel: sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA Jan 21 12:01:28 NAS kernel: ata2.00: configured for UDMA/133 Jan 21 12:01:28 NAS kernel: ata2: EH complete Jan 21 12:01:28 NAS kernel: sd 1:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA Jan 21 12:01:28 NAS kernel: ata5.00: configured for UDMA/133 Jan 21 12:01:28 NAS kernel: ata5: EH complete Jan 21 12:01:28 NAS kernel: sd 4:0:0:0: [sdc] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA Jan 21 12:01:28 NAS kernel: ata6.00: configured for UDMA/133 Jan 21 12:01:28 NAS kernel: ata6: EH complete Jan 21 12:01:28 NAS kernel: sd 5:0:0:0: [sdd] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA Jan 21 12:01:31 NAS RAIDiator: Systemstart är schemalagd till 01/22/2015 05:00 Jan 21 12:01:31 NAS kernel: nfsd: last server has exited, flushing export cache Jan 21 12:01:31 NAS exiting on signal 15 Jan 21 12:02:31 NAS syslogd 1.4.1#18: restart. Jan 21 12:02:31 NAS kernel: klogd 1.4.1#18, log source = /proc/kmsg started. Jan 21 12:02:31 NAS kernel: Initializing cgroup subsys cpu Jan 21 12:02:31 NAS kernel: Linux version 2.6.37.6.RNx86_64.2.4 (jmaggard@calzone) (gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)) #1 SMP Wed Aug 20 11:41:34 PDT 2014 Jan 21 12:02:31 NAS kernel: Command line: initrd=initrd.gz reason=normal BOOT_IMAGE=kernel Jan 21 12:02:31 NAS kernel: BIOS-provided physical RAM map: Jan 21 12:02:31 NAS kernel: BIOS-e820: 0000000000000000 - 000000000009a400 (usable) Jan 21 12:02:31 NAS kernel: BIOS-e820: 000000000009a400 - 00000000000a0000 (reserved) Jan 21 12:02:31 NAS kernel: BIOS-e820: 00000000000e4000 - 0000000000100000 (reserved) Jan 21 12:02:31 NAS kernel: BIOS-e820: 0000000000100000 - 000000003f6b0000 (usable) Jan 21 12:02:31 NAS kernel: BIOS-e820: 000000003f6b0000 - 000000003f6be000 (ACPI data) Jan 21 12:02:31 NAS kernel: BIOS-e820: 000000003f6be000 - 000000003f6e0000 (ACPI NVS) Jan 21 12:02:31 NAS kernel: BIOS-e820: 000000003f6e0000 - 0000000040000000 (reserved) Jan 21 12:02:31 NAS kernel: BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved) Jan 21 12:02:31 NAS kernel: BIOS-e820: 00000000ffe00000 - 0000000100000000 (reserved) Jan 21 12:02:31 NAS kernel: NX (Execute Disable) protection: active Jan 21 12:02:31 NAS kernel: DMI present. Jan 21 12:02:31 NAS kernel: DMI: NETGEAR ReadyNAS/ReadyNAS , BIOS 080016 08/23/2011
I have a Mac mini that I want to connect with. Also a windows 7 laptop.
I have CIFS, NFS and AFP active on the ReadyNas.
To try and solve the issue today, I reinstalled the OS from the boot menu. That did not help, I still have the same problem. So i ran the boot menu, memory test 3 times for 4h. No errors. I also did a boot menu - disk check (took 14 hours). Did not help.
Can some one please helt me understand the logs? Is there another log file / more data that i needed to understand why the Readynas stops responding? :cry:
Sorry. You are correct. The log file i posted is after the OS reinstallation. The only thing active after reinstallation is NFS (if I am not mistaken). Does that narrow it down to NFS problems or not I wonder. I still have the problem with the ReadyNas freezing. I dont have any shares active that I can access now but the ReadyNas still freezes. E.g. when I try to install and upload a plug-in in frontview it stops responding.
Maybe I should do a OS reinstall again and after that make the ReadyNas freeze and then post new log-files?
