I keep getting Call Trace errors, I think it could be my one sas controller which has a Marvel Chipset. I hope someone can shed some light on the issue. Diagnostic Attached. 

sam-the-eagle-diagnostics-20170901-2055.zip

Best google results I came up with imply that you're pulling a drive out at the times of the traces.  If you're not, check all connections to the drives.

 

In particular disks 11 and 12 since they are both returning read errors, and disk 11 has an obscene amount of smart errors implying cabling:

 

199 UDMA_CRC_Error_Count    0x000a   196   196   000    Old_age   Always       -       135075

 

Disk 12 is similar:

199 UDMA_CRC_Error_Count    0x000a   191   191   000    Old_age   Always       -       3755306

 

This all could be marvel related.  LSI controllers are always preferred.  But as an experiment if possible, make sure that the following drives are on the motherboard ports:

 

• 160 Gig: WD-WX20EB9Y7327
• And All the 8TB's

If you don't have enough motherboard ports for all them, don't worry about the 160G.

 

If this reconfigure does work, please reply back as I have a theory trying to test about Marvel Controllers:  

 

These two drives are connected with an LSI adapter. I have two other marvel boards but these drives are not connected to them. I change the drives to new backplane ports to see if that helps.