James Bottomley <James.Bottomley@xxxxxxxxxxxxxxxxxxxxx> schrieb: > On Mon, 2008-04-21 at 11:01 +0200, Lars Täuber wrote: > > # ls /sys/class/enclosure/*/ > > /sys/class/enclosure/6:0:16:0/: > > 0 10 12 14 2 4 6 8 components subsystem > > 1 11 13 15 3 5 7 9 device uevent > > > > /sys/class/enclosure/6:0:33:0/: > > 0 10 12 14 2 4 6 8 components subsystem > > 1 11 13 15 3 5 7 9 device uevent > > > > This is two times the same enclosure. > > That's unusual .. to have two devices managing the same enclosure, but > if you only have 16 slots and not 32, I suppose it must be so. I use both external connections to both expanderboards of the enclosure just for redundancy. > > monosan:/sys/class/enclosure/6:0:16:0/0 # ls -l > > insgesamt 0 > > -rw-r--r-- 1 root root 4096 21. Apr 10:48 active > > -rw-r--r-- 1 root root 4096 21. Apr 10:48 fault > > -rw-r--r-- 1 root root 4096 21. Apr 10:48 locate > > -rw-r--r-- 1 root root 4096 21. Apr 10:48 status > > lrwxrwxrwx 1 root root 0 21. Apr 10:46 subsystem -> ../../../enclosure_component > > -r--r--r-- 1 root root 4096 21. Apr 10:48 type > > --w------- 1 root root 4096 21. Apr 10:48 uevent > > > > There seems to be no device link if I understood you correctly. > > Is the subdirctory numbering somehow in relation to the SCSI ID? > > If the slot is populated a device link should appear (this > is the tricky bit because the ses driver uses VPD inquiries to match up > the reported disk, assuming the enclosure reports it, to the actual one. > These work for SAS disks, but not for SATA ones). So this will never work for the SATA discs in our enclosure, right? Or is there a chance with asking LSI to do something in their firmware? Seems I have no chance to get to know which slot contains the failed drive without a shutdown. Bad luck. But thanks alot anyway. Best regards Lars -- 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
