FreeBSD 10.3/11.0 SCSI errors with Symbios Logic SAS3008 PCI-Express Fusion-MPT SAS-3

[Kenneth D. Merry]

On Fri, Oct 13, 2017 at 20:12:02 +0000, Shiva Bhanujan wrote:
> Hello,
> 
> I have a FreeBSD 10.3 install in a HVM on XenServer 6.5. The HBA330 SAS-3 controller is in pcipassthrough mode to the FreeBSD VM. When I try to access the disks (/dev/da0...) using gpart, I get SCSI errors, like the following:
> 
> 
> 
> (da0:mpr0:0:0:0): CAM status: SCSI Status Error
> 
> (da0:mpr0:0:0:0): SCSI status: Check Condition
> 
> (da0:mpr0:0:0:0): SCSI sense: ILLEGAL REQUEST asc:20,0 (Invalid command operation code)
> 

The error message above is missing the SCSI CDB.  We need that in order to
figure out what command the drive is complaining about.

The error message means that FreeBSD is sending a SCSI command that the
drive doesn't support.  That can be benign, or it can cause a problem.

So, what error does gpart give you when you have this problem?

> I get the same errors w/ FreeBSD 11.0 also.  Running 10.3 natively also has the same result.
> 


> Please note, that these errors don't show up on a Fusion-MPT SAS-2 controller, or a MegaRAID SAS 2208 controller. Additionally, FreeBSD 10.2 doesn't have any SCSI errors on the HBA330 SAS-3 controller either.
> 
> 
> 
> 
> Is there a different version of the mpr driver I should be using? I haven't checked the differences between the mpr driver in 10.2 vs 10.3 and 11.0. I do see that there are others who have experienced these issues. Can somebody please provide me some pointers
>  as to why this is occurring? Or if there are some driver changes that I might be able to incorporate?
> 

In general, the latest mpr(4) driver is the best one.  The driver itself
generally doesn't send SCSI commands (there are a few exceptions), but
rather passes them through from the upper layers of CAM.

> Please note, that I have gone through the mail titled "scsi error at SEAGATE ST1200MM0088 TT31" and have started sg_format on all the SEAGATE disks.    Having said that, I still need to figure out what would happen, if the disks were written to using FreeBSD 10.2, which doesn't seem to have SCSI errors, and when I try to upgrade to 10.3.  Any help is appreciated.
> 

Send the full error messages, and we may be able to figure out what's going
on.

Ken
-- 
Kenneth Merry
ken at FreeBSD.ORG