Server crashes on newly set up array

[jedimastergrant]

I am a newb so please forgive me.  My tech savvy friend helped me set up my Unraid server a few weeks ago and it has not been stable.  I am having seemingly random crashes every day or two.  After he attempted to fix the issues he asked me to post my diagnostics file on the forums and see if you all have any ideas.  I have attempted to attach it.  Please let me know what else I can give you.  And sorry for the language barrier.  

Thanks!

 

Edited April 10 by ChatNoir
removed all individual files from the diagnostics zip file

[ChatNoir]

Hi @jedimastergrant,

The diagnostics come in a single zip file. It is possible that your browser or OS tries to 'help' by showing all the individual files.

Please attach the .zip file instead to your next post in the thread.

[jedimastergrant]

newmiracle-diagnostics-20240409-1444.zip

[itimpi]

You appear to be using macvlan docker networking?    To avoid instability you need to either switch to ipvlan for docker networking, or (if you want to continue using macvlan) disable bridging on the eth0 interface.

[jedimastergrant]

Thank you.  I did make the change to disable bridging. 

 

This morning I encountered a failed device.  The array is still running.  I think we pre cleared all of the drives.  I have attached the diagnostics.  

newmiracle-diagnostics-20240412-0920.zip

[JorgeB]

Looks like a SATA cable problem, replace it and try again.

 

 

[jedimastergrant]

I lost connection again to the Web UI this morning.  I checked at the console and it was still running.  I shut the console down to replace the SATA cable and restarted but still got the same error message with that drive.  I have not restarted the array yet.  I have attached the new diagnostics.

newmiracle-diagnostics-20240413-0852.zip

[JorgeB]

Once a device is disabled it needs to be rebuilt, if the emulated disk is mounting and contents look correct you can rebuild on top:

 

https://docs.unraid.net/unraid-os/manual/storage-management#rebuilding-a-drive-onto-itself

[jedimastergrant]

Thanks for the advice.  I rebuilt that device as you instructed.  I think it was pre cleared but I decided to pre clear it just to make sure that it was good.  So I switched the drive out with another and started the rebuild process and pre clearing.  And I had another crash.  I have attached the diagnostics.  

newmiracle-diagnostics-20240418-1955.zip

[JorgeB]

Previous syslog shows multiple apps crashing, suggest starting by running memtest.

[jedimastergrant]

I ran memtest about a week ago for 24 hours and passed.  I have attached a screen shot.  This processor was overclocked in the past but now it is not.  Could this be an issue?  I have checked the bios to make sure but i could be missing something.  I have an i8600k i can swap out with it as well.  Could also do some checking on the NVME and i think i have others to replace it as well. 

[JorgeB]

41 minutes ago, jedimastergrant said:

 Could this be an issue?

Possibly, could still be a RAM issue since memtest is only definitive if it finds errors, since you have multiple sticks try with just one, if the same try with a different one, that will basically rule out bad RAM.

 

 

 

[jedimastergrant]

I ran both stick individually on mem test and did not find errors.  I ran the server for around 4-5 days before the latest crash.  I did not have any dockers running.  I did not start the array either.  I have attached the diagnostics.  

newmiracle-diagnostics-20240425-1710.zip

[JorgeB]

9 hours ago, jedimastergrant said:

I ran both stick individually on mem test and did not find errors.

Did you run the server with either stick and it still crashed?

[jedimastergrant]

I ran mem test with one stick at a time.   I put both sticks back.  I started the server but did not start the array and it crashed after several days.  

 

[JorgeB]

I meant run the server with just one stick, if it crashes run it with the other one, that will basically rule out RAM, memtest doesn't always catch everything.

[jedimastergrant]

Oh I see.  Thanks for the clarification.