Debian Wheezy and OMSA 6.5.0-1
alessandro.faglia at serioplast.com
Tue Mar 27 13:54:43 CDT 2012
On Tue, Mar 27, 2012 at 7:12 PM, <Jared_Dominguez at dell.com> wrote:
> I see the same ACPI error lines from dmesg on my system with an H200, so I
> think it's noise or at least unrelated.
> Alessandro: lsiutil will not see the H200 , so you will need to use the
> sas2ircu utility instead if you want to use an LSI tool. This is also
> available from hwraid.le-vert.net, although I don't know if or when it
> will ever be directly available from LSI. If you can, install the sas2ircu
> package and run `sas2ircu list`. Let us know what the output is.
-- Controller informations --
-- ID | Model
c0 | SAS2008
-- Arrays informations --
-- ID | Type | Size | Status
c0u0 | RAID1 | 476G | Okay (OKY)
-- Disks informations
-- ID | Model | Status
c0u0p0 | WDC WD5003ABYX-1 (WDWMAYP2771069) | Optimal (OPT)
c0u0p1 | WDC WD5003ABYX-1 (WDWMAYP2801914) | Optimal (OPT)
# sas2ircu list
LSI Corporation SAS2 IR Configuration Utility.
Version 5.00.00.00 (2010.02.09)
Copyright (c) 2009 LSI Corporation. All rights reserved.
Adapter Vendor Device SubSys SubSys
Index Type ID ID Pci Address Ven ID Dev ID
----- ------------ ------ ------ ----------------- ------ ------
0 SAS2008 1000h 72h 00h:05h:00h:00h 1028h 1f1dh
SAS2IRCU: Utility Completed Successfully.
Now I'm wondering why OMSA cannot see such controller. Perhaps I have to
follow an advise I read in the thread, by using some wrappers. Else I have
to develop some kind of script that is going to scan the output for
problematic words and report via cron.
Thanks to everybody for your help.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Linux-PowerEdge