Can anyone assist with what this means ? I just put a new system board in and SAS card , been running for a few days now I see these errors

 

 

 

Sep 1 00:52:30 UnRAID kernel: sas: sas_ata_task_done: SAS error 8a

Sep 1 00:52:30 UnRAID kernel: ata15.00: both IDENTIFYs aborted, assuming NODEV

Sep 1 00:52:30 UnRAID kernel: ata15.00: revalidation failed (errno=-2)

Sep 1 00:52:30 UnRAID kernel: mvsas 0000:04:00.0: Phy7 : No sig fis

Sep 1 00:52:34 UnRAID kernel: sas: sas_form_port: phy7 belongs to port6 already(1)!

Sep 1 00:52:35 UnRAID kernel: ata15: hard resetting link

Sep 1 00:52:35 UnRAID kernel: ata15.00: configured for UDMA/133

Sep 1 00:52:35 UnRAID kernel: ata15: EH complete

Sep 1 00:52:35 UnRAID kernel: sas: --- Exit sas_scsi_recover_host: busy: 0 failed: 0 tries: 1

Sep 1 01:02:17 UnRAID kernel: sas: Enter sas_scsi_recover_host busy: 1 failed: 1

Sep 1 01:02:17 UnRAID kernel: sas: trying to find task 0xffff8803e478ad00

Sep 1 01:02:17 UnRAID kernel: sas: sas_scsi_find_task: aborting task 0xffff8803e478ad00

Sep 1 01:02:17 UnRAID kernel: sas: sas_scsi_find_task: task 0xffff8803e478ad00 is aborted

Sep 1 01:02:17 UnRAID kernel: sas: sas_eh_handle_sas_errors: task 0xffff8803e478ad00 is aborted

Sep 1 01:02:17 UnRAID kernel: sas: ata15: end_device-1:6: cmd error handler

Sep 1 01:02:17 UnRAID kernel: sas: ata9: end_device-1:0: dev error handler

Sep 1 01:02:17 UnRAID kernel: sas: ata10: end_device-1:1: dev error handler

Sep 1 01:02:17 UnRAID kernel: sas: ata11: end_device-1:2: dev error handler

Sep 1 01:02:17 UnRAID kernel: sas: ata12: end_device-1:3: dev error handler

Sep 1 01:02:17 UnRAID kernel: sas: ata13: end_device-1:4: dev error handler

Sep 1 01:02:17 UnRAID kernel: sas: ata14: end_device-1:5: dev error handler

Sep 1 01:02:17 UnRAID kernel: sas: ata15: end_device-1:6: dev error handler

Sep 1 01:02:17 UnRAID kernel: ata15.00: exception Emask 0x0 SAct 0x8 SErr 0x0 action 0x6 frozen

Sep 1 01:02:17 UnRAID kernel: ata15.00: failed command: READ FPDMA QUEUED

Sep 1 01:02:17 UnRAID kernel: ata15.00: cmd 60/00:00:e8:64:b9/02:00:20:00:00/40 tag 3 ncq 262144 in

Sep 1 01:02:17 UnRAID kernel: res 40/00:00:01:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)

Sep 1 01:02:17 UnRAID kernel: ata15.00: status: { DRDY }

Sep 1 01:02:17 UnRAID kernel: ata15: hard resetting link

Sep 1 01:02:19 UnRAID kernel: drivers/scsi/mvsas/mv_sas.c 1430:mvs_I_T_nexus_reset for device[6]:rc= 0

Sep 1 01:02:19 UnRAID kernel: sas: sas_ata_task_done: SAS error 8a

Sep 1 01:02:19 UnRAID kernel: sas: sas_ata_task_done: SAS error 8a

Sep 1 01:02:19 UnRAID kernel: ata15.00: both IDENTIFYs aborted, assuming NODEV

Sep 1 01:02:19 UnRAID kernel: ata15.00: revalidation failed (errno=-2)

Sep 1 01:02:19 UnRAID kernel: mvsas 0000:04:00.0: Phy7 : No sig fis

Sep 1 01:02:23 UnRAID kernel: sas: sas_form_port: phy7 belongs to port6 already(1)!

Sep 1 01:02:24 UnRAID kernel: ata15: hard resetting link

Sep 1 01:02:24 UnRAID kernel: ata15.00: configured for UDMA/133

Sep 1 01:02:24 UnRAID kernel: ata15: EH complete

Sep 1 01:02:24 UnRAID kernel: sas: --- Exit sas_scsi_recover_host: busy: 0 failed: 0 tries: 1

The full diagnostics instead of just snippets would be best, but it looks like a loose / bad cable data cable and/or power.  Also a while back, WD redid their shroud on some of their drives which had the effect that cables which have the internal locking "bump" tend to work better than the latching type cables (which tend to not have the internal bump)  http://lime-technology.com/forum/index.php?topic=36065.msg336010#msg336010

I am going to try to DISABLE AHCI and leave it on IDE, as well disable C1 CPU states to see if that helps -- I am guessing it won't but I am out of ideas, besides trying new SAS breakout cables (which I don't have) or purchasing a new PSU