Unraid keeps becoming unresponsive after about 30mins

[rattfink]

My system becomes unresponsive after about 30-60mins uptime it seems.

 

I disabled Sonarr and Plex plugins thinking those might be causing it and to free up RAM but this morning it's once again unresponsive.

 

Attached is a syslog.txt.

 

I also notice a message on the server screen when I login at the console something like "Make sure all modules are loaded for your kernal".  I took some screenshots with my camera but turned out very blurry.  If you think you need to see those messages (hopefully contained within the syslog anyways) let me know and I'll try and get better pictures.

syslog.txt

[rattfink]

unresponsive again... This is redic.  Not sure what to do.

 

Currently I can access the shares over the network but the website is unresponsive.

 

Shouldn't the website be the one thing that's always up?

[BRiT]

You're having what looks to be hardware issues on your SATA drives or CABLES. Try reseating and replacing the sata cables and power cables. Also do a SMART test on the respective drives.

 

Mar 25 14:35:19 Tower kernel: mvsas 0000:02:00.0: Phy0 : No sig fis

Mar 25 14:35:21 Tower kernel: sas: sas_form_port: phy0 belongs to port2 already(1)!

Mar 25 14:35:46 Tower kernel: ata5: lost interrupt (Status 0x50)

Mar 25 14:35:46 Tower kernel: ata5.01: exception Emask 0x10 SAct 0x0 SErr 0x48d0002 action 0x0 frozen

Mar 25 14:35:46 Tower kernel: ata5.01: SError: { RecovComm PHYRdyChg CommWake 10B8B LinkSeq DevExch }

Mar 25 14:35:46 Tower kernel: ata5.01: failed command: READ DMA

Mar 25 14:35:46 Tower kernel: ata5.01: cmd c8/00:f0:f7:34:00/00:00:00:00:00/f0 tag 0 dma 122880 in

Mar 25 14:35:46 Tower kernel:        res 40/00:00:00:00:00/00:00:00:00:00/50 Emask 0x14 (ATA bus error)

Mar 25 14:35:46 Tower kernel: ata5.01: status: { DRDY }

Mar 25 14:35:46 Tower kernel: ata5.00: hard resetting link

Mar 25 14:35:47 Tower kernel: ata5.01: hard resetting link

Mar 25 14:35:47 Tower kernel: ata5.00: SATA link up 3.0 Gbps (SStatus 123 SControl 300)

Mar 25 14:35:47 Tower kernel: ata5.01: SATA link up 3.0 Gbps (SStatus 123 SControl 300)

Mar 25 14:35:47 Tower kernel: ata5.00: configured for UDMA/133

Mar 25 14:35:48 Tower kernel: ata5.01: configured for UDMA/133

Mar 25 14:35:48 Tower kernel: ata5.01: device reported invalid CHS sector 0

Mar 25 14:35:48 Tower kernel: ata5: EH complete

Mar 25 14:35:52 Tower kernel: mvsas 0000:02:00.0: Phy0 : No sig fis

 

The suspected bad hardware:

Mar 25 14:34:10 Tower kernel: ata5.00: ATA-9: WDC WD30EZRX-00D8PB0,      WD-WMC4N0H1Z0FK, 80.00A80, max UDMA/133

Mar 25 14:34:10 Tower kernel: ata5.01: ATA-7: WDC WD5000AAKS-00TMA0,      WD-WCAPW4350413, 12.01C01, max UDMA/133

 

[rattfink]

Thanks, will try checking all those drives out.

[rattfink]

I reset (disconnected/reconnected) the two drives in question along with the cabling.  Everything responding nicely after the first night; thanks for checking my syslog.