Re: MPTSAS: ("activate status led" | "find disc") in external enclosure

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi James,

James Bottomley <James.Bottomley@xxxxxxxxxxxxxxxxxxxxx> schrieb:
> On Fri, 2008-04-18 at 12:41 +0200, Lars Täuber wrote:
> > Is there a standard way to lit the led in the enclosure with linux means or anything alike?
> > The enclosure does not tell the serial numbers of the included disc.
> > The HBA is an LSI SAS 3801X.
> 
> It depends on whether you have the HBA configured in RAID mode or not.
> If you have, then it takes absolute control of the enclosure management
> at the moment and I don't think you can get to it.

our HBA has no RAID option.

> If you run the HBA as a pure SAS one, then the promise website says this
> enclosure is ses2 compliant, so you should just be able to insert the
> ses module and have enclosure management (2.6.24+ kernels).  This relies
> on the HBA exposing the enclosure device, but I think mptsas only eats
> it for RAID configurations.

I tried 2.6.24.5 but the ses seems to be introduced in 2.6.25.
 
> to see what's in the enclosure, just do
> 
> ls /sys/class/enclosure/*/

# 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.
 
> each of the subdirectories has a slot label (name taken from SES) to
> locate the enclosure, just echo 1 to the locate file and it will flash
> the lights.  If it has a disk, there should be a device link in the slot
> directory (might not be, this depends on ses working correctly and VPD
> inquiries identifying the right disk).

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?

Thanks
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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [SCSI Target Devel]     [Linux SCSI Target Infrastructure]     [Kernel Newbies]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Linux IIO]     [Samba]     [Device Mapper]
  Powered by Linux