[OpenIndiana-discuss] mapping target number to disk?

[Rich]

That's news to me. Are you sure you're running the correct executable?

# ./sas2ircu.SunOS
LSI Corporation SAS2 IR Configuration Utility.
Version 13.00.00.00 (2012.02.17)
Copyright (c) 2009-2012 LSI Corporation. All rights reserved.

SAS2IRCU: No command specified.
  sas2ircu <controller #> <command> <parameters> ...
    where <controller #> is:
      Number between 0 and 255
    where <command> is:
      DISPLAY    - display controller, volume and physical device info
      LIST       - Lists all available LSI adapters (does not need ctlr #>
      CREATE     - create an IR volume
      DELETE     - Delete entire RAID configuration on the selected controller
      DELETEVOLUME  - Delete a specific RAID Volume on the selected controller
      HOTSPARE   - make drive a hot spare
      STATUS     - display current volume status info
      CONSTCHK   - Start Consistency Check operation on the specified IR Volume
      ACTIVATE   - Activate an Inactive IR volume
      LOCATE     - Locate a disk drive on an enclosure
      LOGIR      - Upload or Clear IR Log data
      BOOTIR     - Select an IR Boot Volume as primary boot device
      BOOTENCL   - Select an Enclosure/Bay as primary boot device
      HELP       - Display help information
    where <parameters> are:
      Command specific values; enter "sas2ircu <controller #> <command>"
      to get command specific help
# file ./sas2ircu.SunOS
./sas2ircu.SunOS:       ELF 32-bit LSB executable 80386 Version 1,
dynamically linked, stripped
# uname -a
SunOS [hostname] 5.11 oi_151a4 i86pc i386 i86pc Solaris

- Rich

On Mon, Jun 11, 2012 at 10:06 AM, Dan Swartzendruber <dswartz at druber.com> wrote:
> thanks, i got it.  unfortunately, the solaris x86 executable doesn't seem to
> run under openindiana.  Here is the result:
>
> root at nas:/tank/windows/dswartz# file sas2ircu
> sas2ircu:       ELF 32-bit LSB executable 80386 Version 1, dynamically
> linked, stripped
> root at nas:/tank/windows/dswartz# ./sas2ircu
> Killed
>
> Maybe I am dense, but I am not sure I see the point of having kernel
> messages identifying a specific HW item that is impossible (or at the very
> least extremely difficult and/or non-intuitive) to chase back to the
> specific device that is having issues.  Ugh, not how I wanted to start
> Monday :(
>
> -----Original Message-----
> From: Jim Klimov [mailto:jimklimov at cos.ru]
> Sent: Monday, June 11, 2012 9:20 AM
> To: Discussion list for OpenIndiana
> Cc: Dan Swartzendruber
> Subject: Re: [OpenIndiana-discuss] mapping target number to disk?
>
> 2012-06-11 17:10, Dan Swartzendruber ?????:
>>
>> How do I map 'target 9' to a drive?  Google was not remotely helpful - the
>> only thread I found recommended downloading lsiutil (which I can't find
>> anywhere).  I installed sasinfo, which prints a lot of info, but nothing
>> obviously useful to me.  Any help appreciated...
>
> There were some references in zfs-discuss list last month,
> I think the URL should be like this (I did not check myself):
>
> =====
> http://www.lsi.com/channel/products/storagecomponents/Pages/LSISAS9211-8i.as
> px
>
> select * SUPPORT & DOWNLOADS
> download  SAS2IRCU_P13
> =====
>
> HTH,
> //Jim Klimov
>
>
> _______________________________________________
> OpenIndiana-discuss mailing list
> OpenIndiana-discuss at openindiana.org
> http://openindiana.org/mailman/listinfo/openindiana-discuss