Hi,

 

I'm running 4.7 and I noticed that I'm now getting the following errors about once a day.  There were a few days that didn't get the error at all, but it occurs most days and never at the same time.  Time seems to be random.  I pasted the few lines after, but I'm focusing on the errors lines.

 

 

Jun 18 14:04:19 Tower kernel: mdcmd (520): spinup 8 (Routine)

Jun 18 14:04:27 Tower kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen (Errors)

Jun 18 14:04:27 Tower kernel: ata1.00: failed command: IDLE (Minor Issues)

Jun 18 14:04:27 Tower kernel: ata1.00: cmd e3/00:00:00:00:00/00:00:00:00:00/40 tag 0 (Drive related)

Jun 18 14:04:27 Tower kernel:res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) (Errors)

Jun 18 14:04:27 Tower kernel: ata1.00: status: { DRDY } (Drive related)

Jun 18 14:04:27 Tower kernel: ata1: hard resetting link (Minor Issues)

Jun 18 14:04:33 Tower kernel: ata1: link is slow to respond, please be patient (ready=0) (Drive related

)Jun 18 14:04:34 Tower kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) (Drive related)

Jun 18 14:04:34 Tower kernel: ata1.00: configured for UDMA/133 (Drive related)

Jun 18 14:04:34 Tower kernel: ata1: EH complete (Drive related)

Jun 18 14:47:11 Tower sSMTP[19545]: Creating SSL connection to host

 

SMART log looks good and I have no performance issues, that I'm aware of anyways.

 

Should I be concerned with this?

I have something similar in my Syslog and it just started happening when I added a new disk to my array:

 

Apr 21 21:29:01 Tower kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Apr 21 21:29:01 Tower kernel: ata10.00: status: { DRDY }
Apr 21 21:29:01 Tower kernel: ata10: hard resetting link
Apr 21 21:29:02 Tower kernel: ata10: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Apr 21 21:29:02 Tower kernel: ata10.00: configured for UDMA/133
Apr 21 21:29:02 Tower kernel: ata10: EH complete

See The_Analysis_of_Drive_Issues in my sig. Search for timeout.

Thanks dgaschk.  I just experienced my first write error leading to a red balled disk.  It's the one I just added and it was put in a slot that was previously occupied by another disk that was running for almost 2 years without issue.  I only switched the disk positions because I was having an issue preclearing the Hitachi disk from a connection with my AOC-MV8-SASLP card.  At this point, the issues I'm having seem to be pointing to this new disk so I guess I'll start the RMA process.  Thanks again.