Hi community,

 

I have a problem with my NAS since some weeks. After some miuntes after starting the system it does a hard shutdown after trying to write to a hard drive. When I restart the system the second hard drive in my parity is deactivated and emulated by the parity drive of the array. When I start the systen in safe mode no crash happens.

 

Extended SMART test of the hard drives didn't lead to a failure.

 

I have to say that I changed memory/storage options of several shares which is most probable one of the problems.

 

Daignostic and syslog files are attached.

 

Thanks for your help!

guethsnas-syslog-20241215-1323.zip guethsnas-syslog-previous-20241215-1324.zip guethsnas-diagnostics-20241215-1424.zip

If the server is shutting down by itself it suggests a hardware issue, PSU or overheating CPU would be the main suspects.

20 minutes ago, JorgeB said:

If the server is shutting down by itself it suggests a hardware issue, PSU or overheating CPU would be the main suspects.

@JorgeB: I think this can be excluded because the system runs properly in unraid safe mode.

 

Not necessarily.  A plugin or Docker/VM could be running and adding more stress to the system, enough to put a marginal component over the edge.

29 minutes ago, sugarhill9 said:

@JorgeB: I think this can be excluded because the system runs properly in unraid safe mode.

 

I understand what you are saying but it does sound like a hardware issue unless something is explicitly issuing a shutdown command.

i would suggest removing the s3 Sleep plugin as it has been known to shutdown the server when you do not expect it to.

ok, I'll try to remove the S3 Sleep plugin.

 

Did you check my Syslog and diagnostics files? Before the last shutdown I had following entries:

The write errors and shutdown problem occured first time after I changed memory/storage options for primary/secondary memory of several shares also for system, domains and Appdata.

36 minutes ago, sugarhill9 said:

The write errors and shutdown problem occured first time after I changed memory/storage options for primary/secondary memory of several shares also for system, domains and Appdata.

None of those should cause problems.   Not sure what caused the write errors but I would think getting the shutdown problem resolved first is a good idea.

Up to now no shutdown occured also with running VM and Docker. I'll now try to reassign the second hard drive to the array and start parity check to look if it's related to the hard drive.

Unlikely that a hard drive issue would cause the server to shutdown, a power related issue could, like a bad PSU.

Since S3 sleep was removed no more crashes occured. @itimpi Thanks a lot for the hint!

 

The parity check went through without failures! Why didn't the S3 Sleep cause shutdowns before? What changed? How do I manage disk shutdown without S3 Sleep?