I'm not sure what is going on but twice in a two days my GUI has locked. It seems to start with Plex so I'm wondering if that is what the culprit is. But still weird that this is occurring. And this happened after upgrading to 6.7. I can still access the Dockers by going directly to their specified ports but I cannot access the unRAID GUI.

 

I have attached my syslog as I can still access the server. 

 

Any advice is much appreciated!

20190612_syslog

You have an unassigned disk causing a series of ATA errors, check disk/connections.

 

There are also what look like several ECC corrected memory errors, likely a bad DIMM.

4 hours ago, johnnie.black said:

You have an unassigned disk causing a series of ATA errors, check disk/connections.

 

There are also what look like several ECC corrected memory errors, likely a bad DIMM.

Thanks. Do you think it's because that unassigned disk is my largest disk ? Do you know if it's possible to mix parity? Right now my two parity drives are 6TB and my unassigned disk is 8TB. I just put it in the unassigned so I could use it since I don't have two. 

 

Thanks again for responding so quickly. 

15 minutes ago, cpom1 said:

Do you think it's because that unassigned disk is my largest disk ?

No, it's a hardware problem, connection or the disk itself, you can post the complete diagnostics so we can see SMART reports.

1 hour ago, johnnie.black said:

No, it's a hardware problem, connection or the disk itself, you can post the complete diagnostics so we can see SMART reports.

Thanks. Here is the diagnostic I left running. 

unserver-diagnostics-20190612-2320.zip

Zip is empty, just the folders.

31 minutes ago, johnnie.black said:

Zip is empty, just the folders.

sigh. idk why its doing that. i just run diagnostics in terminal/putty right? 

Yes, or tools -> diagnostics on the GUI.

On 6/13/2019 at 10:13 AM, johnnie.black said:

Yes, or tools -> diagnostics on the GUI.

Okay. So I have removed the stick that was reported as faulty. I also swapped the disk to a different port. Today the issue happened again. Idk if it's Plex or what. I don't get why this is happening. I've attached the diagnostic from the GUI this time. Thanks. 

unserver-diagnostics-20190622-1730.zip

Nothing out of the normal on the logs, though they are just after rebooting, you can try enabling the syslog server, it might catch something when/before it crashes.

5 hours ago, johnnie.black said:

Nothing out of the normal on the logs, though they are just after rebooting, you can try enabling the syslog server, it might catch something when/before it crashes.

grrrr. it happened again and this time it was only nginx. when i run the diagnostic command in putty it doesnt get all the logs; it just says "Starting diagnostics collection..."

 

I have copied the syslog and attached 

syslog

Now there are some nginx timeout errors, but no idea what's causing them, you could try safe mode and/or running without dockers for some time, then if no issues re-enable one by one.