All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@suse.de>
To: John Hughes <john@Calva.COM>
Cc: linux-scsi@vger.kernel.org
Subject: Re: ses enclosure stuff not working with Promise Vtrak J610S JBOD
Date: Wed, 04 Nov 2009 10:07:13 -0600	[thread overview]
Message-ID: <1257350834.2697.52.camel@mulgrave.site> (raw)
In-Reply-To: <4AF1A38E.3000009@Calva.COM>

On Wed, 2009-11-04 at 16:53 +0100, John Hughes wrote:
> James Bottomley wrote:
> > On Wed, 2009-11-04 at 14:00 +0100, John Hughes wrote:
> >   
> >> No sign of an enclosure.
> >>
> >> I've tried with a Debian  2.6.26-2-xen-amd64 kernel, and a 2.6.31 I 
> >> build myself.
> >>
> >> Any clues about what I should to to diagnose this problem?
> >>     
> >
> > Tell me what disks you have first.  Currently the matching algorithm
> > only works with SAS disks because we have no VPD translation for SATA.
> > Hopefully I'll be getting a SATA device to put in an enclosure at some
> > point, so I can play with this (at the moment I only have one SATA
> > device and I'm using it for data storage ...).
> >
> > James
> >
> >
> >   
> All but one are SAS.
> 
> # lsscsi
> [0:0:32:0]   enclosu DP       BACKPLANE        1.07  -       
> [0:2:0:0]    disk    DELL     PERC 6/i         1.21  /dev/sda

OK, so this one is a RAID emulation device and likely won't work, but
the rest (apart from the ATA one) should.

Could you tell me what the enclosure page 0 (supported diagnostic pages)
and page 10 (additional information page that allows us to do the
matching) say?  I suspect the enclosure either doesn't support the page
needed for the matching or there's some problem with the way the
information is encoded.

To get this information, you'll need to run sg_ses on the sg device for
the enclosure (the two promise ones).

Thanks,

James



  reply	other threads:[~2009-11-04 16:07 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-04 13:00 ses enclosure stuff not working with Promise Vtrak J610S JBOD John Hughes
2009-11-04 15:17 ` John Hughes
2009-11-04 15:22 ` James Bottomley
2009-11-04 15:53   ` John Hughes
2009-11-04 16:07     ` James Bottomley [this message]
2009-11-04 16:12       ` John Hughes
2009-11-04 16:20         ` James Bottomley
2009-11-04 18:01           ` John Hughes
2009-11-04 18:05             ` James Bottomley
2009-11-04 18:10               ` John Hughes
2009-11-05  9:41             ` John Hughes
2009-11-05 15:30               ` John Hughes
2009-11-05 15:44                 ` James Bottomley
2009-11-04 15:51 ` John Hughes
2009-11-04 16:54   ` John Hughes
2009-11-04 16:55   ` John Hughes

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=1257350834.2697.52.camel@mulgrave.site \
    --to=james.bottomley@suse.de \
    --cc=john@Calva.COM \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.