linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jon Bendtsen <jonbendtsen@jbit.dk>
To: linux-scsi@vger.kernel.org
Subject: understanding the sg_ses --raw output? so I can turn on the faulty light
Date: Mon, 07 Feb 2011 16:25:48 +0100	[thread overview]
Message-ID: <4D500EFC.1040801@jbit.dk> (raw)

Hi

There has earlier been 2 threads on sg_ses 21 may 2007 and 10 june 2010,
but unfortunately neither seemed to include information about how to
understand the --raw output from sg_ses.

When I run this command
	sg_ses --page=2 /dev/sg30 --raw

I get output that looks like:
        00 00 00 00 00 00 00 00  01 00 00 00 01 00 00 00
        01 00 00 00 01 00 00 00  01 00 00 00 01 00 00 00
        01 00 00 00 01 00 00 00  01 00 00 00 01 00 00 00
        01 00 00 00 01 00 00 00  01 00 00 00 01 00 00 00
        01 00 00 00 01 00 00 00  01 00 00 00 01 00 00 00
        01 00 00 00 01 00 00 00  01 00 00 00 01 00 00 00
        01 00 00 00 01 00 00 00  00 00 01 00 01 00 01 00
        00 00 00 40 06 00 00 47  06 00 00 47 06 00 00 47
        00 00 00 00 01 00 2c 00  06 00 00 00 06 00 00 00
        06 00 00 00 06 00 00 00  06 00 00 00 06 00 00 00
        06 00 00 00 06 00 00 00  06 00 00 00 06 00 00 00
        06 00 00 00 06 00 00 00  06 00 00 00 06 00 00 00
        06 00 00 00 06 00 00 00  06 00 00 00 06 00 00 00
        06 00 00 00 06 00 00 00  06 00 00 00 06 00 00 00
        06 00 00 00 06 00 00 00

There are 26 segments starting with 01 00 00 00, and 27 with 06. I think
i have to use the 01 segments, but the number 26 does not fit with my
number of disks unless they count like this: controller, backplane + 24
disks or enclosure port A + port B + 24 disks.

At first i figured i had to set 20 in the last field, but that did not
work. So i tried modifying a 01 00 00 00 to 01 00 02 20 based on this
webpage:
http://storagesecrets.org/2008/12/scsi-enclosure-services-ses-ses-2-management/

I also tried with 06 00 00 00 to 06 00 02 20, still nothing.

I set the data using
	sg_ses --control --page=2 -d - /dev/sg30 < raw.test


Here are the output of lsscsi
[0:0:0:0]    disk    ATA      INTEL SSDSA2M040 2CV1  /dev/sda
[1:0:0:0]    disk    ATA      INTEL SSDSA2M040 2CV1  /dev/sdb
[2:0:0:0]    disk    ATA      Corsair CSSD-F24 2.0   /dev/sdc
[3:0:0:0]    disk    ATA      Corsair CSSD-F24 2.0   /dev/sdd
[5:0:0:0]    disk    ATA      Corsair CSSD-F24 2.0   /dev/sde
[5:0:1:0]    disk    ATA      Corsair CSSD-F24 2.0   /dev/sdf
[6:0:0:0]    disk    ATA      SAMSUNG HE103UJ  1113  /dev/sdg
[6:0:1:0]    disk    ATA      SAMSUNG HE103UJ  1113  /dev/sdh
[6:0:2:0]    disk    ATA      WDC WD1001FALS-0 0K05  /dev/sdi
[6:0:3:0]    disk    ATA      WDC WD1001FALS-0 0K05  /dev/sdj
[6:0:4:0]    disk    ATA      SAMSUNG HE103UJ  1113  /dev/sdk
[6:0:5:0]    disk    ATA      SAMSUNG HE103UJ  1113  /dev/sdl
[6:0:6:0]    disk    ATA      WDC WD10EADS-00L 1A01  /dev/sdm
[6:0:7:0]    disk    ATA      SAMSUNG HE103UJ  1113  /dev/sdn
[6:0:8:0]    disk    ATA      WDC WD1001FALS-0 0K05  /dev/sdo
[6:0:9:0]    disk    ATA      SAMSUNG HE103UJ  1113  /dev/sdp
[6:0:10:0]   disk    ATA      WDC WD1001FALS-0 0K05  /dev/sdq
[6:0:11:0]   disk    ATA      WDC WD1001FALS-0 0K05  /dev/sdr
[6:0:12:0]   disk    ATA      Hitachi HDS72101 A39C  /dev/sds
[6:0:13:0]   disk    ATA      SAMSUNG HD103UJ  1118  /dev/sdt
[6:0:14:0]   disk    ATA      SAMSUNG HD103UJ  1118  /dev/sdu
[6:0:15:0]   disk    ATA      Hitachi HDS72101 A39C  /dev/sdv
[6:0:16:0]   disk    ATA      Hitachi HUA72201 A3EA  /dev/sdw
[6:0:17:0]   disk    ATA      Hitachi HUA72201 A3EA  /dev/sdx
[6:0:18:0]   disk    ATA      WDC WD1002FBYS-0 0C06  /dev/sdy
[6:0:19:0]   disk    ATA      WDC WD1002FBYS-0 0C06  /dev/sdz
[6:0:20:0]   disk    ATA      WDC WD2002FYPS-0 1G01  /dev/sdaa
[6:0:21:0]   disk    ATA      Hitachi HUA72202 A3EA  /dev/sdab
[6:0:22:0]   disk    ATA      WDC WD2003FYYS-0 1D01  /dev/sdac
[6:0:23:0]   disk    ATA      WDC WD2001FASS-0 0101  /dev/sdad
[6:0:24:0]   enclosu LSILOGIC SASX36 A.0          9  -


The first 6 /dev/sd devices are attached using sata to a 00:11.0 SATA
controller: ATI Technologies Inc SB700/SB800 SATA Controller [IDE mode]
where as the last 24 disks is connected using a 06:00.0 SCSI storage
controller: LSI Logic / Symbios Logic SAS1068E PCI-Express Fusion-MPT
SAS (rev 08) found onboard on my SuperMicro H8DI3+-F in a supermicro
SC846E2 chasis. Only 1 SAS cable is attached between the controller and
enclosure backplane even though both support 2 cables.


The same enclosure and disks used to work with a 3ware 9690sa-8i which
had a webpage system to turn on and off those bits. But after a brand
new disk crashed and pulled all the other 23 disks offline from the
controller, then i do not like to continue to use the 3ware 9690sa-8i
controller.


JonB


             reply	other threads:[~2011-02-07 15:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-07 15:25 Jon Bendtsen [this message]
2011-02-07 15:40 ` understanding the sg_ses --raw output? so I can turn on the faulty light James Bottomley
2011-02-08 12:55   ` Jon Bendtsen
2011-02-08 14:18     ` James Bottomley
2011-02-08 14:22       ` Jon Bendtsen
2011-02-08 14:15 ` Jon Bendtsen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4D500EFC.1040801@jbit.dk \
    --to=jonbendtsen@jbit.dk \
    --cc=linux-scsi@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).