RECEIVE DIAGNOSTIC RESULTS. CDB: 1c 01 02 80 00 00

Status
Not open for further replies.
B

bstev

Explorer
Joined
Dec 16, 2016
Messages
53
A few days ago I expanded my storage on my R510 running FREENAS-9.10.2-U3 by adding the below hardware;
SAS9207-8E
Two Mini-SAS SFF cables
MD1200
two 10TB HDD's

All went well, is functional, and shows to be healthy. But I keep getting strange data in my "daily security run output" now.

I did some research and ran some commands to try and figure out what is happening. First it was looking like one of my 10TB drives but now from the reports then best I can tell is I may have a Mini SAS cable connection issue or an issue with one of the SAS module in the MD1200.
Are there other commands to run for diagnosing further, or does any one have some advice?


The daily report I received after adding the hardware was:

Code:

freenas.local kernel log messages:

> mps1: <Avago Technologies (LSI) SAS2308> port 0x7000-0x70ff mem 0xfd2f0000-0xfd2fffff,0xfd280000-0xfd2bffff irq 17 at device 0.0 on pci27

> mps1: Firmware: 20.00.02.00, Driver: 21.01.00.00-fbsd

> mps1: IOCCapabilities: 5285c<ScsiTaskFull,DiagTrace,SnapBuf,EEDP,TransRetry,EventReplay,HostDisc>

> mps1: SAS Address for SATA device = 86373f2995979796

> mps1: SAS Address for SATA device = 8c3a3a2995979796

> mps1: SAS Address from SATA device = 86373f2995979796

> mps1: SAS Address from SATA device = 8c3a3a2995979796

> (probe0:mps1:0:8:0): REPORT LUNS. CDB: a0 00 00 00 00 00 00 00 00 10 00 00

> (probe0:mps1:0:8:0): CAM status: SCSI Status Error

> (probe0:mps1:0:8:0): SCSI status: Check Condition

> (probe0:mps1:0:8:0): SCSI sense: UNIT ATTENTION asc:29,0 (Power on, reset, or bus device reset occurred)

> (probe0:mps1:0:8:0): Retrying command (per sense data)

> (probe3:mps1:0:11:0): REPORT LUNS. CDB: a0 00 00 00 00 00 00 00 00 10 00 00

> (probe3:mps1:0:11:0): CAM status: SCSI Status Error

> (probe3:mps1:0:11:0): SCSI status: Check Condition

> (probe3:mps1:0:11:0): SCSI sense: UNIT ATTENTION asc:29,0 (Power on, reset, or bus device reset occurred)

> (probe3:mps1:0:11:0): Retrying command (per sense data)

> ses0 at mps1 bus 0 scbus4 target 8 lun 0

> ses0: <DELL MD1200 1.05> Fixed Enclosure Services SPC-3 SCSI device

> ses0: 600.000MB/s transfers

> ses0: Command Queueing enabled

> ses0: SCSI-3 ENC Device

> ses1 at mps1 bus 0 scbus4 target 11 lun 0

> ses1: <DELL MD1200 1.05> Fixed Enclosure Services SPC-3 SCSI device

> ses1: 600.000MB/s transfers

> ses1: Command Queueing enabled

> ses1: SCSI-3 ENC Device

> da2 at mps0 bus 0 scbus3 target 8 lun 0

> da2: <SEAGATE ST3600057SS ES66> Fixed Direct Access SPC-3 SCSI device

> da2: Serial Number 6SL72FX4

> da2: 600.000MB/s transfers

> da2: Command Queueing enabled

> da2: 572325MB (1172123568 512 byte sectors)

> da3 at mps0 bus 0 scbus3 target 9 lun 0

> da3: <SEAGATE ST3600057SS ES66> Fixed Direct Access SPC-3 SCSI device

> da3: Serial Number 6SLAN99V

> da3: 600.000MB/s transfers

> da3: Command Queueing enabled

> da3: 572325MB (1172123568 512 byte sectors)

> da7 at mps0 bus 0 scbus3 target 13 lun 0

> da7: <SEAGATE ST3600057SS ES64> Fixed Direct Access SPC-3 SCSI device

> da7: Serial Number 6SL1LDL8

> da7: 600.000MB/s transfers

> da7: Command Queueing enabled

> da7: 572325MB (1172123568 512 byte sectors)

> da15 at mps1 bus 0 scbus4 target 9 lun 0

> da15: <ATA WDC WD100PURZ-85 0A80> Fixed Direct Access SPC-4 SCSI device

> da15: Serial Number 7JHJEEUC			

> da15: 600.000MB/s transfers

> da15: Command Queueing enabled

> da15: 9537536MB (19532873728 512 byte sectors)

> da14 at mps0 bus 0 scbus3 target 23 lun 0

> da14: <ATA INTEL SSDSC2BA20 FJ03> Fixed Direct Access SPC-4 SCSI device

> da14: Serial Number BTTV6033019M200GGN

> da14: 600.000MB/s transfers

> da14: Command Queueing enabled

> da14: 23841MB (48828125 512 byte sectors)

> da16 at mps1 bus 0 scbus4 target 10 lun 0

> da16: <ATA WDC WD100PURZ-85 0A80> Fixed Direct Access SPC-4 SCSI device

> da16: Serial Number 7JHJKHPC			

> da16: 600.000MB/s transfers

> da16: Command Queueing enabled

> da16: 9537536MB (19532873728 512 byte sectors)

> cd0 at ata1 bus 0 scbus1 target 0 lun 0

> cd0: <NECVMWar VMware IDE CDR10 1.00> Removable CD-ROM SCSI device

> cd0: Serial Number 10000000000000000001

> cd0: 33.300MB/s transfers (UDMA2, ATAPI 12bytes, PIO 65534bytes)

> cd0: 514MB (263618 2048 byte sectors)

> cd0: quirks=0x40<RETRY_BUSY>

> ses1: da16,pass18: SAS Device Slot Element: 2 Phys at Slot 0

> ses0: da15,pass17: SAS Device Slot Element: 2 Phys at Slot 1

> ses0:  phy 0: SATA device

> ses0:  phy 0: parent 500c04f26142d53f addr 500c04f26142d520

> ses0:  phy 1: SAS device type 0 id 1

> ses1:  phy 0: SATA device

> ses1:  phy 0: parent 500c04f26142d53f addr 500c04f26142d521

> ses1:  phy 1: SAS device type 0 id 1

> ses1:  phy 1: protocols: Initiator( None ) Target( None )

> ses1:  phy 1: parent 0 addr 0

> ses0:  phy 1: protocols: Initiator( None ) Target( None )

> ses0:  phy 1: parent 0 addr 0

> mps1: mpssas_prepare_remove: Sending reset for target ID 10

> da16 at mps1 bus 0 scbus4 target 10 lun 0

> mps1: da16: Unfreezing devq for target ID 10

> <ATA WDC WD100PURZ-85 0A80> s/n 7JHJKHPC			 detached

> (da16:mps1:0:10:0): Periph destroyed

> mpssas_get_sata_identify: error reading SATA PASSTHRU; iocstatus = 0x47

> mps1: SAS Address for SATA device = 8c3a3a2995979796

> mps1: SAS Address from SATA device = 8c3a3a2995979796

> da16 at mps1 bus 0 scbus4 target 10 lun 0

> da16: <ATA WDC WD100PURZ-85 0A80> Fixed Direct Access SPC-4 SCSI device

> da16: Serial Number 7JHJKHPC			

> da16: 600.000MB/s transfers

> da16: Command Queueing enabled

> da16: 9537536MB (19532873728 512 byte sectors)

> ses1: da16,pass18: SAS Device Slot Element: 2 Phys at Slot 0

> ses1:  phy 0: SATA device

> ses1:  phy 0: parent 500c04f26142d53f addr 500c04f26142d521

> ses1:  phy 1: SAS device type 0 id 1

> ses1:  phy 1: protocols: Initiator( None ) Target( None )

> ses1:  phy 1: parent 0 addr 0


-- End of security output --


Now the report I receive each day is just:

Code:
freenas.local kernel log messages:

>			 (ses0:mps1:0:8:0): RECEIVE DIAGNOSTIC RESULTS. CDB: 1c 01 02 80 00 00 length 32768 SMID 899 command timeout cm 0xfffffe0000a60bf0 ccb 0xfffff80061802800

>			 (noperiph:mps1:0:4294967295:0): SMID 2 Aborting command 0xfffffe0000a60bf0

> mps1: Sending reset from mpssas_send_abort for target ID 8

> mps1: Unfreezing devq for target ID 8

>			 (ses0:mps1:0:8:0): RECEIVE DIAGNOSTIC RESULTS. CDB: 1c 01 02 80 00 00 length 32768 SMID 828 command timeout cm 0xfffffe0000a5aec0 ccb 0xfffff8057e213800

>			 (noperiph:mps1:0:4294967295:0): SMID 3 Aborting command 0xfffffe0000a5aec0

> mps1: Sending reset from mpssas_send_abort for target ID 8

> mps1: Unfreezing devq for target ID 8


-- End of security output --


Code:
[root@freenas ~]# zpool status
  pool: Data																														
 state: ONLINE																													
  scan: scrub repaired 0 in 5h3m with 0 errors on Sun Apr  1 05:03:40 2018														
config:																															
																																	
		NAME											STATE	 READ WRITE CKSUM												
		Data											ONLINE	   0	 0	 0												
		  mirror-0									  ONLINE	   0	 0	 0												
			gptid/9b6cf4aa-365d-11e7-83a9-000c2941216a  ONLINE	   0	 0	 0												
			gptid/9c1cd20b-365d-11e7-83a9-000c2941216a  ONLINE	   0	 0	 0												
		  mirror-1									  ONLINE	   0	 0	 0												
			gptid/f3057558-4700-11e7-bb4c-000c29887eee  ONLINE	   0	 0	 0												
			gptid/f3bf48d3-4700-11e7-bb4c-000c29887eee  ONLINE	   0	 0	 0												
		  mirror-3									  ONLINE	   0	 0	 0												
			gptid/a0ea9ff9-4af1-11e7-9a9c-000c29887eee  ONLINE	   0	 0	 0												
			gptid/a1a2e051-4af1-11e7-9a9c-000c29887eee  ONLINE	   0	 0	 0												
		  mirror-4									  ONLINE	   0	 0	 0												
			gptid/f0d66a30-4fbe-11e8-b4f1-000c29887eee  ONLINE	   0	 0	 0												
			gptid/f153d39f-4fbe-11e8-b4f1-000c29887eee  ONLINE	   0	 0	 0												
		logs																														
		  gptid/487cf760-4af1-11e7-9a9c-000c29887eee	ONLINE	   0	 0	 0												
																																	
errors: No known data errors																										
																																	
  pool: Main																														
 state: ONLINE																													
  scan: scrub repaired 0 in 0h3m with 0 errors on Sun Apr 29 00:04:00 2018														
config:																															
																																	
		NAME											STATE	 READ WRITE CKSUM												
		Main											ONLINE	   0	 0	 0												
		  mirror-0									  ONLINE	   0	 0	 0												
			gptid/357c1c22-46f2-11e7-ae19-000c29887eee  ONLINE	   0	 0	 0												
			gptid/3736e15b-46f2-11e7-ae19-000c29887eee  ONLINE	   0	 0	 0												
		  mirror-1									  ONLINE	   0	 0	 0												
			gptid/390a2c35-46f2-11e7-ae19-000c29887eee  ONLINE	   0	 0	 0												
			gptid/3acb69e1-46f2-11e7-ae19-000c29887eee  ONLINE	   0	 0	 0												
		  mirror-2									  ONLINE	   0	 0	 0												
			gptid/9783402a-d5cf-11e7-949e-000c29887eee  ONLINE	   0	 0	 0												
			gptid/3e3a18f9-46f2-11e7-ae19-000c29887eee  ONLINE	   0	 0	 0												
																																	
errors: No known data errors																										
																																	
  pool: freenas-boot																												
 state: ONLINE																													
  scan: scrub repaired 7.50K in 0h1m with 0 errors on Sat Apr 21 03:46:07 2018													
config:																															
																																	
		NAME		STATE	 READ WRITE CKSUM
		freenas-boot  ONLINE	   0	 0	 0																					
		  mirror-0  ONLINE	   0	 0	 0																					
			da0p2   ONLINE	   0	 0	 0																					
			da1p2   ONLINE	   0	 0	 0																					
																																	
errors: No known data errors



[root@freenas ~]# sas2flash -listall																								
LSI Corporation SAS2 Flash Utility																								
Version 16.00.00.00 (2013.03.01)																									
Copyright (c) 2008-2013 LSI Corporation. All rights reserved																		
																																	
		Adapter Selected is a LSI SAS: SAS2008(B2)																				
																																	
Num   Ctlr			FW Ver		NVDATA		x86-BIOS		 PCI Addr														
----------------------------------------------------------------------------														
																																	
0  SAS2008(B2)	 20.00.07.00	14.01.00.08	07.11.10.00	 00:03:00:00														
1  SAS2308_2(D1)   20.00.02.00	14.01.00.06	07.39.00.00	 00:1b:00:00														
																																	
		Finished Processing Commands Successfully.																				
		Exiting SAS2Flash.

[root@freenas ~]# camcontrol devlist																								
<NECVMWar VMware IDE CDR10 1.00>   at scbus1 target 0 lun 0 (pass0,cd0)															
<VMware Virtual disk 1.0>		  at scbus2 target 0 lun 0 (pass1,da0)															
<VMware Virtual disk 1.0>		  at scbus2 target 1 lun 0 (pass2,da1)															
<SEAGATE ST3600057SS ES66>		 at scbus3 target 8 lun 0 (pass3,da2)															
<SEAGATE ST3600057SS ES66>		 at scbus3 target 9 lun 0 (pass4,da3)															
<ATA WDC WD60PURX-64T 0A80>		at scbus3 target 10 lun 0 (pass5,da4)															
<SEAGATE ST3600057SS ES64>		 at scbus3 target 11 lun 0 (pass6,da5)															
<SEAGATE ST3600057SS ES64>		 at scbus3 target 12 lun 0 (pass7,da6)															
<SEAGATE ST3600057SS ES64>		 at scbus3 target 13 lun 0 (pass8,da7)															
<SEAGATE ST3600057SS ES64>		 at scbus3 target 15 lun 0 (pass9,da8)															
<ATA WDC WD60PURX-64T 0A80>		at scbus3 target 17 lun 0 (pass10,da9)														 
<ATA WDC WD60PURX-64T 0A80>		at scbus3 target 18 lun 0 (pass11,da10)														
<ATA WDC WD60PURX-64T 0A80>		at scbus3 target 20 lun 0 (pass12,da11)														
<ATA WDC WD60PURX-64T 0A80>		at scbus3 target 21 lun 0 (pass13,da12)														
<ATA WDC WD60PURX-64T 0A80>		at scbus3 target 22 lun 0 (pass14,da13)														
<ATA INTEL SSDSC2BA20 FJ03>		at scbus3 target 23 lun 0 (pass15,da14)														
<DELL MD1200 1.05>				 at scbus4 target 8 lun 0 (pass16,ses0)														 
<ATA WDC WD100PURZ-85 0A80>		at scbus4 target 9 lun 0 (pass17,da15)														 
<ATA WDC WD100PURZ-85 0A80>		at scbus4 target 10 lun 0 (da16,pass18)														
<DELL MD1200 1.05>				 at scbus4 target 11 lun 0 (pass19,ses1)
 
Last edited by a moderator:
Ericloewe

Ericloewe

Server Wrangler
Moderator
Joined
Feb 15, 2014
Messages
20,194
Your backplane seems to be acting up. Investigate firmware updates.
 
B

bstev

Explorer
Joined
Dec 16, 2016
Messages
53
Thanks for the advice Ericloewe

I assume you mean firmware updates on the MD1200, not the HBA I just added?

This MD1200, PSU's, and SAS controllers are used units I purchased a few weeks back. The cables and HBA are new though. This is my first experience with a MD1200 and I only find firmware updates using windows or Linux redhat, so that may not be an easy one to try. And not sure if the updates will pass through the HBA card I have. I now this part is more a topic for another forum...

What did you see in the log that lead you to the backplane, as opposed to one of the SAS controllers or cable connections?
 
Ericloewe

Ericloewe

Server Wrangler
Moderator
Joined
Feb 15, 2014
Messages
20,194
You should be able to just boot a live ISO, install the firmware and be done with it. The SAS controller used shouldn't make a difference, but you never know with these vendors...

As for the log, the driver errors weren't for any disks, but for the backplane, ses0, target number 8 on mps1. ses is the SCSI Enclosure Services driver, meaning chassis, backplanes and that kind of stuff.
 
B

bstev

Explorer
Joined
Dec 16, 2016
Messages
53
ses0 and ses1 are my redudant connections to my MD1200. So this is the part my mind does not follow with the backplane or firmeware being the cause. ses0 and ses1 have in common the backplane and MD1200 enclosure, but ses0 and ses1 have independent SAS cables and connecting to independent SAS controllers mounted in the MD1200. This is where my brain keeps going towards the ses0 SAS controller (mounted in the MD1200) or the cable for ses0.

Thanks for the live CD tip too, I was figuring I would need to setup a flashdrive for it and keep it setup for future firmware changes.
 
Ericloewe

Ericloewe

Server Wrangler
Moderator
Joined
Feb 15, 2014
Messages
20,194
Your disks aren't using multipath, so it's unlikely that you have two independent SAS expanders in use. Some weird misconfiguration could be the source of the error, however.
 
Status
Not open for further replies.

Similar threads

Y
  • Locked
Need help with "RECEIVE DIAGNOSTIC RESULTS"
Replies
6
Views
2K
Yan Sh
Y
S
All disks "GPT rejected -- may not be recoverable" after migrating from bare-metal to ESXi Passthrough
Replies
4
Views
2K
sunshine931
S
VioletDragon
SOLVED mps0: mpssas_prepare_remove: Sending reset for target ID 15 CAM status: CCB request aborted by the host
2 3
Replies
53
Views
6K
VioletDragon
VioletDragon
J
HP DL380 host + DL180 as external storage
Replies
0
Views
813
jensl
J
k1n6b0b
  • Locked
run_interrupt_driven_hooks: still waiting after XX seconds for xpt_config - HBA NetApp / PMC-Sierra
Replies
1
Views
2K
dlavigne
D
Top