NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Unexpected shutdown issue
Hi, My ReadyNAS RN-4312X shuts down unexpectedly at midnight. I couldn't find any logs either. It's officially shutting down. What could be the reasons for this? I have the following OS version...
Hi StephenB,
I found log entries similar to the following lines :
file name : status.log
-------------------------
[22/01/07 03:17:44 MSK] warning:volume:LOGMSG_HEALTH_VOLUME Volume rzk.data health changed from Redundant to Degraded.
[22/01/07 03:17:44 MSK] warning:system:LOGMSG_SENT_ALERT_MESG_FAILED Alert message failed to send.
[22/01/07 03:21:44 MSK] crit:disk:LOGMSG_DISK_FAIL_HALT System will be shut down in 30 minutes because of disk failure.
[22/01/07 03:25:51 MSK] info:system:LOGMSG_READYNASD_ABORTED ReadyNASOS service or process (enclosure_monit) was restarted.
[22/01/07 03:25:53 MSK] info:system:LOGMSG_START_READYNASD ReadyNASOS background service started.
[22/01/07 09:19:25 MSK] info:system:LOGMSG_READYNASD_ABORTED_NOINFO ReadyNASOS service or process was restarted.
[22/01/07 09:19:27 MSK] info:system:LOGMSG_START_READYNASD ReadyNASOS background service started.
Shutdown time approx. 03:30 or 04:00 ...
fatihturan wrote:
[22/01/07 03:21:44 MSK] crit:disk:LOGMSG_DISK_FAIL_HALT System will be shut down in 30 minutes because of disk failure.
There is a setting in the web ui to shut down the system when there is a disk failure. Look in system->settings->alerts, it is likely set there.
You should also look in system.log and kernel.log to get more information on the disk failure.
Hi StephenB,
Thank you for all your informations and quickly answers.
I've last question, what's the mean the following log message and is this very critical a message ?
System: ReadyNASOS service or process (enclosure_monit) was restarted.
Kind Regards,
Fatih
fatihturan wrote:
System: ReadyNASOS service or process (enclosure_monit) was restarted.
I don't know why that process was restarted. Looking into the more comprehensive logs around that time (system.log, kernel.log, systemd-journal.log) would likely give more clues.
This could be a side effect of the disk failure, so I suggest that you focus on understanding what disk failed first.
Thank you very much for your help, have a nice day.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
