From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jon Bendtsen Subject: Re: understanding the sg_ses --raw output? so I can turn on the faulty light Date: Tue, 08 Feb 2011 15:22:59 +0100 Message-ID: <4D5151C3.5090806@jbit.dk> References: <4D500EFC.1040801@jbit.dk> <1297093255.3012.30.camel@mulgrave.site> <4D513D24.800@jbit.dk> <1297174684.3088.11.camel@mulgrave.site> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Return-path: Received: from mgw2.diku.dk ([130.225.96.92]:45079 "EHLO mgw2.diku.dk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752600Ab1BHOXD (ORCPT ); Tue, 8 Feb 2011 09:23:03 -0500 In-Reply-To: <1297174684.3088.11.camel@mulgrave.site> Sender: linux-scsi-owner@vger.kernel.org List-Id: linux-scsi@vger.kernel.org To: James Bottomley Cc: linux-scsi@vger.kernel.org On 08/02/11 15.18, James Bottomley wrote: > On Tue, 2011-02-08 at 13:55 +0100, Jon Bendtsen wrote: >> 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? > > It's what the man page says: the byte for byte output of the diagnostic > mode page minus the first four bytes. > >> 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? > > Well the descriptor format is variable, it's documented in the SES > standard. Which I have not been able to find in a available standard. The organisation wants money to show me. I managed to find a PDF though, see my other post. Thank you for taking your time to answer my questions. > [...] >>> 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? > > well, it depends what the enclosure calls it's slots, but it would be > something like > > echo 1 > /sys/class/enclosure///fault I do not have those > After making sure the ses driver is loaded and bound, of course. Quite > a few fault lights are hard wired, and not amenable to software > interference (others aren't hard wired at all and only work with > software). ok.