I am having an issue where my parity disks are showing up as disabled. I have unassigned and reassigned and now letting the parity sync go though but I would like to figure out why this happened. I have been having a few issues as of late it started with my Plex docker container not opening up the GUI. After doing a database repair it seems that the problem had been corrected but now I have having the same problem again. Any help with these issues would be much appreciated. 

 

Thanks! 

tower-diagnostics-20221227-1738.zip

Diags are after rebooting so we cannot see what happened, disks looks mostly fine, after the sync finishes run a non correcting parity check.

So I ran a non correcting parity check and at some point during it something again happened. I was not able to reach the GUI for unraid. Plex not running, IP was not pingable, and when I connected a monitor I didn't get anything. So again rebooted. Is there a way for me to get diagnostics when I cannot reach the GUI?

Also whatever is happening has again trashed most of my docker containers. I had to fix the plex database again (corrupted). NGINX container and SABnzbd containers also showing errors when trying to open. The other containers function fine it seems. 

 

Edited December 29, 20223 yr by Paradiselost1983

You can enable the syslog server and post that after the troubles.

Thanks! Ill post them as soon as it crashes again. It seems to be a daily occurrence.  

So its been a while but the parity disks are both showing disabled again when I went to login. Here is the syslog and diagnostic log from today. Can anyone make sense of this for me?

 

syslog

tower-diagnostics-20230125-1146.zip

SSD drive is filliping up the log with ATA errors, replace cables to see if they go away and post new diags after array start.

Replaced the cables. Everything seems to be back to normal. Logs attached. 

tower-syslog-20230128-1244.zip

Edited January 28, 20233 yr by Paradiselost1983

Looks good for now.

Thanks again for all your help!