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 a ReadyNAS 3138 that crashed today. When I couldn't ping it I checked on the device, which is in a server room behind a locked door, and it was just off. When I started up, I had no error messages, and no log of the device having been shutdown.
I'm running firmware 6.6.0.
This NAS is being used in an important business application, and I'd like to review the release notes of all the firmware versions since 6.6.0 to see if my problem might be resolved. The people in a company who ask "Why did this happen?" like to know why afterall.
Why are release notes not available? The forum for "Firmware Releases" has links that are all dead.
Downloading the logs and reviewing those would help to possibly identify what issue you ran into. Many of the logs have timestamped entries.
The information you've provided so far is not enough to identify the cause of the crash. Without knowing the cause one can only guess if the cause was a software issue addressed by a firmware update or something else.
When URLs are significantly changed an unfortunate side effect is the breaking of old links. Note the zip file download contains both the firmware .img file and also a copy of the Release Notes. The Release Notes typically provide a list of the key changes since the previous production firmware release.
When I visit the "Logs" page on the ReadyNAS it doesn't give me a lot of information. Prior to the crash, there had been no log entry here for 5 days (and the last one was "Resyncing".
Then, after we discovered the ReadyNAS was off, we turned it on, and the next log entries were:
Thu Jul 13 2017 2:50:57
System: ReadyNASOS background service started.
Thu Jul 13 2017 2:50:56
System: ReadyNASOS service or process was restarted
However, when I use the "Download Logs" function, I get a zip file with a ton of logs. I picked through all these looking for events that are timestamped in the hour or so before the crash. The ones that seem most relevant are kernel.log, systemd-journal.log, system.log, and readynasd.log.
Reviewing these, I can tell that:
The NAS has been behaving pretty well up until yesterday.
Yesterday it rebooted at the following times:
July 13 - 02:50:48
July 13 - 08:21:51
July 13 - 21:30:11
July 14 - 02:17:02
But in every case, the logs don't provide anything useful because:
- The prior log entry, before the reboot, was different for each of the above events.
- The prior log entry, before the reboot, was hours before the above event
Jul 13 15:17:34 WTPNAS001 readynasd[2961]: Cannot open /var/lib/apt/lists/apt.readynas.com_packages_readynasos_dists_6.6.0_apps_binary-amd64_Packages Jul 13 15:17:34 WTPNAS001 readynasd[2961]: Cannot open /var/lib/apt/lists/egnyte-cdn.egnyte.com_storagesync_netgear6_en-us_dists_6.6_egnyte_binary-amd64_Packages Jul 13 15:58:59 WTPNAS001 readynasd[2961]: NTP is enabled. Jul 13 20:39:07 WTPNAS001 readynasd[2961]: Volume NASVOLUME is resynced. -- Reboot -- Jul 13 21:30:11 WTPNAS001 readynasd[2961]: readynasd log started
readynasd.log Example 2
Jul 13 21:45:39 WTPNAS001 readynasd[2961]: ERROR: Radar: Maximum iteration exceeded Jul 14 02:09:40 WTPNAS001 readynasd[2961]: Volume NASVOLUME is resynced. -- Reboot -- Jul 14 02:17:02 WTPNAS001 readynasd[2973]: readynasd log started
readynasd.log Example
Jul 13 02:45:46 WTPNAS001 nmbd[2935]: ***** Samba name server WTPNAS001 is now a local master browser for workgroup WORKGROUP on subnet 192.168.1.200 ***** -- Reboot -- Jul 13 02:50:46 WTPNAS001 rsyncd[2834]: rsyncd version 3.1.1 starting, listening on port 873 Jul 13 02:50:46 WTPNAS001 wsdd2[2836]: starting.
systemd-journal.log Example
Jul 13 21:17:01 WTPNAS001 CRON[15383]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Jul 13 21:17:01 WTPNAS001 CRON[15376]: pam_unix(cron:session): session closed for user root -- Reboot -- Jul 13 21:30:07 WTPNAS001 systemd-journald[1421]: Runtime journal (/run/log/journal/) is 8.0M, max 195.5M, 187.5M free.
kernel.log
Jul 06 13:47:35 WTPNAS001 kernel: igb 0000:00:14.0 eth0: igb: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: RX -- Reboot -- Jul 13 02:50:43 WTPNAS001 kernel: Initializing cgroup subsys cpuset
