RAID/HDD 'identify' LED - how to activate

[John Miles]

Thank you - yes, you are correct, no enclosure device detected.
... I miss my xSeries....

John.

On Mon, May 30, 2011 at 12:49 PM, Lennart Sorensen <
lsorense-1wCw9BSqJbv44Nm34jS7GywD8/FfD2ys at public.gmane.org> wrote:

> On Fri, May 27, 2011 at 11:08:22PM -0400, John Miles wrote:
> > Here is the scenario
> > I have a Supermicro 5025M-2U with a 3Ware 9650SE 8 port controller and a
> > Western Digital WDC WD1002FBYS-02A6B0 disk in it that is reporting an
> error.
> >
> > The 3Ware CLI tool 'tw_cli' has a feature that would allow me to set the
> > 'identify' LED to  on or off.
> > Unfortunately, I don't think I am able to turn this lovely light on, as
> the
> > device's "Identify Status = N/A".
> >
> > /cx/px set identify=on|off (9550SX and 9590SE only)
> >     This command sets the LED status of the port. If the identify is set
> to
> > on, the firmware activates the setting of the corresponding LED of the
> port.
> > If the setting of the configuration for LED is blinking for identify=on,
> > this will blink the LED of the port.
> >
> > ******    Note: Enclosure services hardware is also required.  *******
> >
> >     Example:
> >
> >      //localhost> /c0/p5 set identify=on
> >
> >      Setting Port Identify on /c0/p5 to [on] ... Done.
> >
> > I guess, I need to determine if I have 'enclosure service hardware'
>
> Do you have a hotswap cage with LEDs on it?  If not, then you don't
> have that.
>
> > Does anyone have anything to suggest I try to determing if I have
> 'enclosure
> > service hardware'?
> > (not sure what to look for in say, dmesg for that info)
>
> For example:
> dmesg | grep scsi
> [    1.742035] scsi0 : ServeRAID
> [    1.742465] scsi 0:0:0:0: Direct-Access     ServeRA  MAIN
> V1.0 PQ: 0 ANSI: 2
> [    1.753173] scsi 0:1:0:0: Direct-Access     ST375064 0NS
>  .AEP PQ: 0 ANSI: 5
> [    1.766582] scsi 0:1:1:0: Direct-Access     ST375064 0NS
>  .AEP PQ: 0 ANSI: 5
> [    1.785141] scsi 0:1:2:0: Direct-Access     ST375064 0NS
>  .AEP PQ: 0 ANSI: 5
> [    1.802008] scsi 0:1:3:0: Direct-Access     ST375064 0NS
>  .AEP PQ: 0 ANSI: 5
> [    1.864640] scsi: waiting for bus probes to complete ...
> [    1.870021] scsi 0:3:0:0: Enclosure         IBM-ESXS VSC7160
>  1.07 PQ: 0 ANSI: 3
>
> That last one is the enclosure hardware.  It has its own ID on the bus,
> so that the controller can talk to it.  It runs the LEDs on the howswap
> bays and other such things.
>
> So in this case there is the raid, then the individual disks on another
> bus, then the enclosure on yet another bus, as far as the controller
> view to linux is concerned at least.  Linux only creates /dev/sd* for
> the raid device, but there is an sg device for each individual disk,
> and the raid and the enclosure for those wanting to do interesting things.
>
> --
> Len Sorensen
> --
> The Toronto Linux Users Group.      Meetings: http://gtalug.org/
> TLUG requests: Linux topics, No HTML, wrap text below 80 columns
> How to UNSUBSCRIBE: http://gtalug.org/wiki/Mailing_lists
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://gtalug.org/pipermail/legacy/attachments/20110601/200eaa10/attachment.html>