From: Jon Bendtsen <jonbendtsen@jbit.dk>
To: linux-scsi@vger.kernel.org
Subject: Re: understanding the sg_ses --raw output? so I can turn on the faulty light
Date: Tue, 08 Feb 2011 13:55:00 +0100 [thread overview]
Message-ID: <4D513D24.800@jbit.dk> (raw)
In-Reply-To: <1297093255.3012.30.camel@mulgrave.site>
On 07/02/11 16.40, James Bottomley wrote:
> On Mon, 2011-02-07 at 16:25 +0100, Jon Bendtsen wrote:
>> 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.
>
> It's a hex dump of the diagnostic mode page.
I know that. What I meant was which segments in the hex dump correlate
to which segments in the text version of the dianostic mode page?
How long are the segments? 8 bytes? The way it is formatted something
could hint that? Or is it just 4 bytes which another formatting suggests?
>> 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
>
> So I don't really plan to parse a huge hex dump, but my instinct would
> be you got something wrong.
I probably do that, which is why I asked how to understand the hex dump.
> I'd firstly validate that your lights can be flashed with the ses
> driver ... if they can, then look for a mistake in the hex dump.
How can I validate that my lights can be flashed with the SES driver?
JonB
next prev parent reply other threads:[~2011-02-08 13:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-07 15:25 understanding the sg_ses --raw output? so I can turn on the faulty light Jon Bendtsen
2011-02-07 15:40 ` James Bottomley
2011-02-08 12:55 ` Jon Bendtsen [this message]
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=4D513D24.800@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).