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@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
