I went from 10 drives to 18 drives, most of the new drives (2tb & 3tb) are used, pulled from one of my colo servers (got 5tb drives in the servers now). Yet 4 of them are not showing up... I have checked the bays and one of the new.used drives that does show up works in all the hot swap bays....

 

I did notice this but I am not sure its related

Oct 26 22:01:32 Tower kernel: be2net 0000:01:00.0: PCIe error reporting enabled
Oct 26 22:01:32 Tower kernel: mpt3sas version 13.100.00.00 loaded
Oct 26 22:01:32 Tower kernel: ahci 0000:00:1f.2: version 3.0
Oct 26 22:01:32 Tower kernel: be2net 0000:01:00.0: FW version is 3.103.397.31
Oct 26 22:01:32 Tower kernel: be2net 0000:01:00.0: Adapter does not support HW error recovery
Oct 26 22:01:32 Tower kernel: be2net 0000:01:00.1: be2net version is 11.1.0.0
Oct 26 22:01:32 Tower kernel: be2net 0000:01:00.1: PCIe error reporting enabled
Oct 26 22:01:32 Tower kernel: mpt2sas_cm0: Current Controller Queue Depth(1596),Max Controller Queue Depth(1720)
Oct 26 22:01:32 Tower kernel: be2net 0000:01:00.1: FW version is 3.103.397.31
Oct 26 22:01:32 Tower kernel: be2net 0000:01:00.1: Adapter does not support HW error recovery
Oct 26 22:01:32 Tower kernel: mpt2sas_cm1: Current Controller Queue Depth(1880),Max Controller Queue Depth(2015)
Oct 26 22:01:33 Tower kernel: be2net 0000:01:00.0: be2net version is 11.1.0.0
Oct 26 22:01:33 Tower kernel: be2net 0000:01:00.0: PCIe error reporting enabled
Oct 26 22:01:34 Tower kernel: be2net 0000:01:00.0: FW version is 3.103.397.31
Oct 26 22:01:34 Tower kernel: be2net 0000:01:00.0: Adapter does not support HW error recovery
Oct 26 22:01:34 Tower kernel: be2net 0000:01:00.1: be2net version is 11.1.0.0
Oct 26 22:01:34 Tower kernel: be2net 0000:01:00.1: PCIe error reporting enabled
Oct 26 22:01:34 Tower kernel: be2net 0000:01:00.1: FW version is 3.103.397.31
Oct 26 22:01:34 Tower kernel: be2net 0000:01:00.1: Adapter does not support HW error recovery

One of the drives is giving me errors but until the preclear is done I am not going to remove it

tower-diagnostics-20171026-2233.zip

Nothing obvious, one of the LSI controllers is using a very old firmware, you should update it, but you'll need to start narrowing down the problem more on your own, e.g., connect one of undetected disks to the onboard controller and see if it works there.