Disk ejected. Would be great to get your help to take a look at the diagnostic whether there is an issue with the disk or "just" yet again with the cable?

tower-diagnostics-20161217-0852.zip

Steve, I'm sorry, but that drive is on the SAS card, using mpt3sas, and that module is the worst for error reporting, only reporting cryptic codes.  I have been unable to find any help or guides or table of codes anywhere online, that could help interpret the response, and help us know what's wrong.

 

There is a higher level and readable response at the end of each error report sequence that I don't remember seeing before, so it may be the start of an interpretation in recent kernels of the mpt3sas codes, but I don't know enough to properly interpret it either.

 

Only 2 variables varied, Sense Key and ASC, so I'll use those:

Sense Key=3, ASC=0x11, "critical medium error"

Sense Key=5, ASC=0x21, "critical target error"

Sense Key=2, ASC=4, "I/O error"

 

The first occurred once and was followed by a sequence of higher level read errors, the second occurred once and was followed by a sequence of write errors, then the last occurred 9 times, followed by both read and write errors.  The word 'medium' does hint of a bad sector issue, so I would run an Extended SMART test on the drive.  The SMART report looked fine though.  The word 'target' could mean almost anything, and I/O errors could be almost anything too.  If the drive was losing the connection in any way, then you would see 'task aborting' messages, and there were none.  Since they all are associated with read and write errors, and cable issues don't do that (they're retried until they succeed), we can assume it's not a cable or connection issue.