Hello, 

 

my server crashes regularly, but I can't say exactly when it started.

 

Hopefully the syslog in the appendix will give you a starting point.

In addition, I have attached the last diagnostic log I have.

 

The server is not reachable any more, has no image output, after disconnecting the power and restarting it usually works again, until the server is not reachable again and shows the same symptoms.

 

I'd like to rule out the possibility that it's UnRAID.

 

Currently I have no internet because of a malfunction, could that have anything to do with it? I still use the test license.

syslog tower-diagnostics-20191016-1703.zip

Edited November 1, 20196 yr by aurevo

You can't start the array on a trial license without internet, but that wouldn't cause a crash.

 

Which motherboard and CPU? Has it passed at least 24 hours of memtest without error?

20 minutes ago, jonathanm said:

You can't start the array on a trial license without internet, but that wouldn't cause a crash.

 

Which motherboard and CPU? Has it passed at least 24 hours of memtest without error?

CPU: Intel Core i5-6400T
Motherboard: MSI Z270-A PRO

 

The Internet is currently available again and I have updated to UnRAID Pro.

 

Before I had done the steps I wanted to turn the NAS off again and the fans only went on and off for a short time and the power button only lit up for a short time and this repeated itself again and again.

 

I have now removed a RAM bar for testing purposes to see if it was the right one.

 

I hadn't run Memtest yet.

Edited November 1, 20196 yr by aurevo

Disk you are assigning as disk3 is getting disabled:

Oct 16 17:03:10 Tower kernel: ata1: link is slow to respond, please be patient (ready=0)
Oct 16 17:03:40 Tower kernel: ata1: COMRESET failed (errno=-16)
Oct 16 17:03:40 Tower kernel: ata1: limiting SATA link speed to 3.0 Gbps
Oct 16 17:03:45 Tower kernel: ata1: COMRESET failed (errno=-16)
Oct 16 17:03:45 Tower kernel: ata1: reset failed, giving up
Oct 16 17:03:45 Tower kernel: ata1.00: disabled

Looks like a white label drive, there was recently another user with similar issue with an identical disk.

12 hours ago, johnnie.black said:

Disk you are assigning as disk3 is getting disabled:

Oct 16 17:03:10 Tower kernel: ata1: link is slow to respond, please be patient (ready=0)
Oct 16 17:03:40 Tower kernel: ata1: COMRESET failed (errno=-16)
Oct 16 17:03:40 Tower kernel: ata1: limiting SATA link speed to 3.0 Gbps
Oct 16 17:03:45 Tower kernel: ata1: COMRESET failed (errno=-16)
Oct 16 17:03:45 Tower kernel: ata1: reset failed, giving up
Oct 16 17:03:45 Tower kernel: ata1.00: disabled

Looks like a white label drive, there was recently another user with similar issue with an identical disk.

 

The user with the white label hard drive was probably me.

 

The disk is already removed and the array is rebuilt without a disk and parity is restored.

 

The log was from before this point.

12 hours ago, aurevo said:

The log was from before this point.

I didn't look at the diags date, why did you post 2 week old diags?

 

Looking at the syslog you don't have an internet connection, trial key requires internet connection at array start.

4 hours ago, johnnie.black said:

I didn't look at the diags date, why did you post 2 week old diags?

 

Looking at the syslog you don't have an internet connection, trial key requires internet connection at array start.

 

These were the latest logs I had at the time and had attached to them for comparison purposes.

If the logs are useless, we ignore them.

 

As mentioned in the last post, I have now upgraded the trial to a Pro license and have Internet again.

 

Attached the new diagnostics from today. Maybe you can see anything, but I think it was the RAM as you said.

tower-diagnostics-20191103-1407.zip

Only issue I'm seeing currently is that you have a corrupt docker image, delete and recreate.