All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Hughes <john@Calva.COM>
To: linux-scsi@vger.kernel.org
Subject: ses enclosure stuff not working with Promise Vtrak J610S JBOD
Date: Wed, 04 Nov 2009 14:00:03 +0100	[thread overview]
Message-ID: <4AF17AD3.6060909@Calva.COM> (raw)

Like Lars Täuber last year I have a Promise Vtrak J610S "just a bunch of 
disks" cabinet, and like him I find that the ses enclosure services 
don't seem to be working right.

If I look in the /sys/class/enclosure hierarchy I don't see the links I 
should for the devices:

# lsscsi | grep PROMISE
[3:0:14:0]   enclosu PROMISE  3U-SAS-16-D BP   0107  -         /dev/sg17
[4:0:14:0]   enclosu PROMISE  3U-SAS-16-D BP   0107  -         /dev/sg32


(Note that's one device with two connections)

# ls -R /sys/class/enclosure/4\:0\:14\:0/
/sys/class/enclosure/4:0:14:0/:
0  10  12  14  2  4  6	8  components  power	  uevent
1  11  13  15  3  5  7	9  device      subsystem

/sys/class/enclosure/4:0:14:0/0:
active	fault  locate  power  status  type  uevent

/sys/class/enclosure/4:0:14:0/0/power:
wakeup

/sys/class/enclosure/4:0:14:0/1:
active	fault  locate  power  status  type  uevent
[...]

No sign of any "device" links in the "bay" directories.

Also the "fault" and "locate" files seem to do nothing, writing to them 
doesn't make any lights flash.

If I try looking from the device side:

# ls /sys/block/sdaa/device
block:sdaa	evt_media_change  modalias     rev		     subsystem
bsg:4:0:11:0	generic		  model        scsi_device:4:0:11:0  timeout
bus		iocounterbits	  power        scsi_disk:4:0:11:0    type
delete		iodone_cnt	  queue_depth  scsi_generic:sg29     uevent
device_blocked	ioerr_cnt	  queue_type   scsi_level	     vendor
driver		iorequest_cnt	  rescan       state

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?

--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

             reply	other threads:[~2009-11-04 13:05 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-04 13:00 John Hughes [this message]
2009-11-04 15:17 ` ses enclosure stuff not working with Promise Vtrak J610S JBOD John Hughes
2009-11-04 15:22 ` James Bottomley
2009-11-04 15:53   ` John Hughes
2009-11-04 16:07     ` James Bottomley
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=4AF17AD3.6060909@Calva.COM \
    --to=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.