SATA affiliation missing from SATA phys

Krasimir Velkov moerke at abv.bg
Wed Feb 13 18:02:29 UTC 2019


 Hey guys,  
 I have a couple of freebsd 12.0 controllers (each has an LSI 9300-8e HBA) and one JBOD box with a single LSI 3x40 SAS EXPANDER.
The JBOD box is connected to both controllers and according to all information I found on the Internet, SATA disks CANNOT be accessed
by two SAS Initiators at the same time and have SATA affiliations. The problem is that the aforementioned affiliations are not being honored
and both initiators end up accessing the SATA disks which leads to an affiliation conflict and one of the initiators freezing. Here is an example for a SATA disk:
 
   smp_rep_phy_sata --phy=0 /dev/ses4  Report phy SATA response:  
 expander change count: 83  
 phy identifier: 0  
 STP I_T nexus loss occurred: 0  
 affiliations supported: 0  
 affiliation valid: 0  
 STP SAS address: 0x500304801eeba8c0  
 register device to host FIS:  
 
 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  
 affiliated STP initiator SAS address: 0x0  
 STP I_T nexus loss SAS address: 0x0  
 affiliation context: 0  
 current affiliation contexts: 0  
 maximum affiliation contexts: 0    
  there is no affiliated STP initiator SAS address and sending operations to the phy works for both initiator hosts. I found absolutely no information
on how to enable/disable SATA affiliation for the SAS EXPANDER.
 Tried issuing commands with both camcontrol and smp_phy_control without
any success:  
   camcontrol smppc /dev/ses4 -vvv -p 0 -o sataportsel  camcontrol: error sending command  (pass6:mpr5:0:200:0): PHY CONTROL. 40 91 00 00 00 00 00 00 00 00 07 00 00 ...  (pass6:mpr5:0:200:0): CAM status: SMP Status Error  (pass6:mpr5:0:200:0): SMP status: SMP Function Failed (0x2)   
  I have absolutely no idea how to proceed. Has anybody bumped into something similar?  
  Thanks,  Krasimir Velkov 


More information about the freebsd-scsi mailing list