Need help with "RECEIVE DIAGNOSTIC RESULTS"

[Yan Sh]

Hi, guys!

I need you help in finding out the problem.

We built a storage on the following platform:

1. Supermicro 846E16-R1200B(X8DTE-F)
2. CPU: Intel(R) Xeon(R) CPU L5640 @ 2.27GHz x 2
3. RAM: 48Gb ECC

Huawei OceanStor S2300 http://www.ebay.com/itm/Huawei-OceanStor-S2300-/201812997673?hash=item2efcfdf629:g:O5oAAOSwXYtYxldW
is connected via LSI SAS 9200-8e (IT mode)
and filled with WD Gold 4tb x23

FreeNAS-9.10.2-U2
RAIDZ3 (11 hdd) x2 + 1 hot spare.

Now we are getting the RECEIVE DIAGNOSTIC RESULTS in dmesg.

Please help to find out where is the problem and solve it, or just not to worry about it.

Code:

kernel log messages:
		(ses1:mps1:0:8:0): RECEIVE DIAGNOSTIC RESULTS. CDB: 1c 01 02 80 00 00 length 32768 SMID 931 terminated ioc 804b scsi 0 state c xfer 0
		(ses1:mps1:0:8:0): RECEIVE DIAGNOSTIC RESULTS. CDB: 1c 01 02 80 00 00 length 32768 SMID 952 terminated ioc 804b scsi 0 state c xfer 0
		(ses1:mps1:0:8:0): RECEIVE DIAGNOSTIC RESULTS. CDB: 1c 01 02 80 00 00 le ngth 32768 SMID 794 terminated ioc 804b scsi 0 state c xfer 0
		(ses1:mps1:0:8:0): RECEIVE DIAGNOSTIC RESULTS. CDB: 1c 01 02 80 00 00 length 32768 SMID 442 terminated ioc 804b scsi 0 state c xfer 0
		(ses1:mps1:0:8:0): RECEIVE DIAGNOSTIC RESULTS. CDB: 1c 01 02 80 00 00 length 32768 SMID 947 terminated ioc 804b scsi 0 state c xfer 0
		(ses1:mps1:0:8:0): RECEIVE DIAGNOSTIC RESULTS. CDB: 1c 01 02 80 00 00 length 32768 SMID 273 terminated ioc 804b scsi 0 state c xfer 0
		(ses1:mps1:0:8:0): RECEIVE DIAGNOSTIC RESULTS. CDB: 1c 01 02 80 00 00 length 32768 SMID 210 terminated ioc 804b scsi 0 state c xfer 0
		(ses1:mps1:0:8:0): RECEIVE DIAGNOSTIC RESULTS. CDB: 1c 01 02 80 00 00 length 32768 SMID 161 terminated ioc 804b scsi 0 state c xfer 0
		(ses1:mps1:0:8:0): RECEIVE DIAGNOSTIC RESULTS. CDB: 1c 01 02 80 00 00 length 32768 SMID 1020 terminated ioc 804b scsi 0 state c xfer 0
		(ses1:mps1:0:8:0): RECEIVE DIAGNOSTIC RESULTS. CDB: 1c 01 02 80 00 00 length 32768 SMID 517 terminated ioc 804b scsi 0 state c xfer 0
-- End of security output --

Code:

~# camcontrol devlist
<LSI CORP SAS2X36 0717>			at scbus0 target 9 lun 0 (pass0,ses0)
<PMCSIERA SXP 36x6Gsec RevC>	   at scbus1 target 8 lun 0 (pass1,ses1)
<ATA WDC WD4002FYYZ-0 1M02>		at scbus1 target 32 lun 0 (pass2,da0)
<ATA WDC WD4002FYYZ-0 1M02>		at scbus1 target 33 lun 0 (pass3,da1)
<ATA WDC WD4002FYYZ-0 1M02>		at scbus1 target 34 lun 0 (pass4,da2)
<ATA WDC WD4002FYYZ-0 1M02>		at scbus1 target 35 lun 0 (pass5,da3)
<ATA WDC WD4002FYYZ-0 1M02>		at scbus1 target 36 lun 0 (pass6,da4)
<ATA WDC WD4002FYYZ-0 1M02>		at scbus1 target 37 lun 0 (pass7,da5)
<ATA WDC WD4002FYYZ-0 1M02>		at scbus1 target 38 lun 0 (pass8,da6)
<ATA WDC WD4002FYYZ-0 1M02>		at scbus1 target 39 lun 0 (pass9,da7)
<ATA WDC WD4002FYYZ-0 1M02>		at scbus1 target 40 lun 0 (pass10,da8)
<ATA WDC WD4002FYYZ-0 1M02>		at scbus1 target 41 lun 0 (pass11,da9)
<ATA WDC WD4002FYYZ-0 1M02>		at scbus1 target 42 lun 0 (pass12,da10)
<ATA WDC WD4002FYYZ-0 1M02>		at scbus1 target 43 lun 0 (pass13,da11)
<ATA WDC WD4002FYYZ-0 1M02>		at scbus1 target 44 lun 0 (pass14,da12)
<ATA WDC WD4002FYYZ-0 1M02>		at scbus1 target 45 lun 0 (pass15,da13)
<ATA WDC WD4002FYYZ-0 1M02>		at scbus1 target 46 lun 0 (pass16,da14)
<ATA WDC WD4002FYYZ-0 1M02>		at scbus1 target 47 lun 0 (pass17,da15)
<ATA WDC WD4002FYYZ-0 1M02>		at scbus1 target 48 lun 0 (pass18,da16)
<ATA WDC WD4002FYYZ-0 1M02>		at scbus1 target 49 lun 0 (pass19,da17)
<ATA WDC WD4002FYYZ-0 1M02>		at scbus1 target 50 lun 0 (pass20,da18)
<ATA WDC WD4002FYYZ-0 1M02>		at scbus1 target 51 lun 0 (pass21,da19)
<ATA WDC WD4002FYYZ-0 1M02>		at scbus1 target 52 lun 0 (pass22,da20)
<ATA WDC WD4002FYYZ-0 1M02>		at scbus1 target 53 lun 0 (pass23,da21)
<ATA WDC WD4002FYYZ-0 1M02>		at scbus1 target 54 lun 0 (pass24,da22)
<TOSHIBA-VT180 1.00>			   at scbus3 target 0 lun 0 (pass25,ada0)

dmesg.txt

 

[Yan Sh]

UP

 

[mav@]

"RECEIVE DIAGNOSTIC RESULTS" requests is probably result of FreeNAS polling enclosure status. Errors there is probably result of some SAS transport of enclosure problem.

 

[Ericloewe]

Wait a second, you only mention one LSI SAS controller, but you clearly have at least two, since the errors are coming from mps1.

The problem is going to be related to the backplane attached to mps1. sas2flash -listall should help to identify the relevant HBA and from there, you can easily trace the cable to the offending backplane.

 

[Yan Sh]

Wait a second, you only mention one LSI SAS controller, but you clearly have at least two, since the errors are coming from mps1.

The problem is going to be related to the backplane attached to mps1. sas2flash -listall should help to identify the relevant HBA and from there, you can easily trace the cable to the offending backplane.

Thanks for your reply.
You are correct about two LSI boards. But it doesn't make sence. One is not operational right now.
I actually know what HBA is reporrting an error. But don't know what is the problem. And how to fix it.
I tried to change the cables between LSI and HDD enclosure. But it didn't help.

 

[Yan Sh]

UP

 

[Yan Sh]

UP