Discussion:
Regarding ses in FreeBSD 9.2
(too old to reply)
Joar Jegleim
2014-01-29 17:03:17 UTC
Permalink
Forgive me for cross-listing, this one was initially sent to questions.
Hardware seem to be more accurate .

See bellow regarding my issue, I get those once every minute.

The messages seem to be from ses0, which according to man ses is 'SCSI
Environmental Services driver' .
Does anybody know any utility I can use against the ses SCSI
Environmental Services driver (?)



---------- Forwarded message ----------
From: Joar Jegleim <***@gmail.com>
Date: 27 January 2014 13:33
Subject: Regarding ses in FreeBSD 9.2
To: freebsd-questions <freebsd-***@freebsd.org>


Hi,

I just upgraded a server from 9.1-RELEASE -> 9.2-RELEASE
I noticed I get these about once every minute in /var/log/messages, as
well as to the console:

Jan 27 13:26:11 store01 kernel: ses0: pass25,ses0: SAS Device Slot
Element: 1 Phys at Slot 23, Not All Phys
Jan 27 13:26:11 store01 kernel: ses0: phy 0: SAS device type 0 id 0
Jan 27 13:26:11 store01 kernel: ses0: phy 0: protocols: Initiator(
None ) Target( None )
Jan 27 13:26:11 store01 kernel: ses0: phy 0: parent 5001438017e2f4ff addr 0
Jan 27 13:26:11 store01 kernel: ses0: pass25,ses0: SAS Device Slot
Element: 1 Phys at Slot 24, Not All Phys
Jan 27 13:26:11 store01 kernel: ses0: phy 0: SAS device type 0 id 0
Jan 27 13:26:11 store01 kernel: ses0: phy 0: protocols: Initiator(
None ) Target( None )
Jan 27 13:26:11 store01 kernel: ses0: phy 0: parent 5001438017e2f4ff addr 0
Jan 27 13:26:11 store01 kernel: ses0: pass25,ses0: Element descriptor:
'900080050002'
Jan 27 13:26:11 store01 kernel: ses0: pass25,ses0: SAS Expander: 36
Physses0: phy 0: connector 26 other 1
Jan 27 13:26:11 store01 kernel: ses0: phy 1: connector 27 other 2
Jan 27 13:26:11 store01 kernel: ses0: phy 2: connector 28 other 3
Jan 27 13:26:11 store01 kernel: ses0: phy 3: connector 29 other 4
Jan 27 13:26:11 store01 kernel: ses0: phy 4: connector 30 other 5
Jan 27 13:26:11 store01 kernel: ses0: phy 5: connector 31 other 6
Jan 27 13:26:11 store01 kernel: ses0: phy 6: connector 32 other 7
Jan 27 13:26:11 store01 kernel: ses0: phy 7: connector 33 other 8
Jan 27 13:26:11 store01 kernel: ses0: phy 8: connector 34 other 9
Jan 27 13:26:11 store01 kernel: ses0: phy 9: connector 35 other 10
Jan 27 13:26:11 store01 kernel: ses0: phy 10: connector 36 other 11
Jan 27 13:26:11 store01 kernel: ses0: phy 11: connector 37 other 12
Jan 27 13:26:11 store01 kernel: ses0: phy 12: connector 38 other 13
Jan 27 13:26:11 store01 kernel: ses0: phy 13: connector 39 other 14
Jan 27 13:26:11 store01 kernel: ses0: phy 14: connector 40 other 15
Jan 27 13:26:11 store01 kernel: ses0: phy 15: connector 41 other 16
Jan 27 13:26:11 store01 kernel: ses0: phy 16: connector 42 other 17
Jan 27 13:26:11 store01 kernel: ses0: phy 17: connector 43 other 18
Jan 27 13:26:11 store01 kernel: ses0: phy 18: connector 44 other 19
Jan 27 13:26:11 store01 kernel: ses0: phy 19: connector 45 other 20
Jan 27 13:26:11 store01 kernel: ses0: phy 20: connector 46 other 21
Jan 27 13:26:12 store01 kernel: ses0: phy 21: connector 47 other 22
Jan 27 13:26:12 store01 kernel: ses0: phy 22: connector 48 other 23
Jan 27 13:26:12 store01 kernel: ses0: phy 23: connector 49 other 24
Jan 27 13:26:12 store01 kernel: ses0: phy 24: connector 50 other 25
Jan 27 13:26:12 store01 kernel: ses0: phy 25: connector 59 other 255
Jan 27 13:26:12 store01 kernel: ses0: phy 26: connector 60 other 255
Jan 27 13:26:12 store01 kernel: ses0: phy 27: connector 61 other 255
Jan 27 13:26:12 store01 kernel: ses0: phy 28: connector 62 other 255
Jan 27 13:26:12 store01 kernel: ses0: phy 29: connector 63 other 255
Jan 27 13:26:12 store01 kernel: ses0: phy 30: connector 64 other 255
Jan 27 13:26:12 store01 kernel: ses0: phy 31: connector 65 other 255
Jan 27 13:26:12 store01 kernel: ses0: phy 32: connector 66 other 255
Jan 27 13:26:12 store01 kernel: ses0: phy 33: connector 255 other 255
Jan 27 13:26:12 store01 kernel: ses0: phy 34: connector 255 other 255
Jan 27 13:26:12 store01 kernel: ses0: phy 35: connector 255 other 255

I suspect it has something to to with an LSI HBA I've installed on that box,

LSI SAS 9207-4i4e SGL

The card was installed and ran on the 9.1-RELEASE install, and ses
didn't post those messages then ...

Does anyone know if these messages are to worry about ? and how I may
stop them ?

The LSI card is connected via external sas to an MSA storage shelf
with 20 midline disks + 2 ssd disks + one sas disk.




--
----------------------
Joar Jegleim
Homepage: http://cosmicb.no
Linkedin: http://no.linkedin.com/in/joarjegleim
fb: http://www.facebook.com/joar.jegleim
AKA: CosmicB @Freenode

----------------------
--
----------------------
Joar Jegleim
Homepage: http://cosmicb.no
Linkedin: http://no.linkedin.com/in/joarjegleim
fb: http://www.facebook.com/joar.jegleim
AKA: CosmicB @Freenode

----------------------
Michael Fuckner
2014-01-29 19:03:56 UTC
Permalink
Post by Joar Jegleim
Does anybody know any utility I can use against the ses SCSI
Environmental Services driver (?)
sysutils/sg3_utils should do, but long time since I last did.

Kind regards,
Michael!
Joar Jegleim
2014-01-30 18:32:52 UTC
Permalink
okay, thnx Michael, I'll check it out
Post by Michael Fuckner
Post by Joar Jegleim
Does anybody know any utility I can use against the ses SCSI
Environmental Services driver (?)
sysutils/sg3_utils should do, but long time since I last did.
Kind regards,
Michael!
_______________________________________________
http://lists.freebsd.org/mailman/listinfo/freebsd-hardware
--
----------------------
Joar Jegleim
Homepage: http://cosmicb.no
Linkedin: http://no.linkedin.com/in/joarjegleim
fb: http://www.facebook.com/joar.jegleim
AKA: CosmicB @Freenode

----------------------
Loading...