Starting dsm_sa_datamgr32d FAILED

De Wetenschapper wetenschapper at gmail.com
Thu Apr 26 10:49:29 CDT 2007


Thanks for your anwsers.

A status update:

I'm also using OSMA 5.2

Yes, I installed from the Dell yum repository

 /opt/dell/srvadmin/dataeng/bin/dsm_sa_datamgr32d is the binary that wont
start

tried it with strace -o /tmp/trace.log -f
/opt/dell/srvadmin/dataeng/bin/dsm_sa_datamgr32d
but it generated a file which was way to long to process +10000 lines ...
I investigated some missing files but they where also missing on a RHEL4 on
which it is working.

I tried to outcomment ral32
however it was not 0x0F...
[Data Populators]
popalias.0x00=ral32
popalias.0x01=dcrac532
popalias.0x02=dcadpt32
popalias.0x03=dcesmp32
popalias.0x04=dciemp32
popalias.0x05=dcienv32
popalias.0x06=dcipm932
popalias.0x07=dcip1032
popalias.0x08=dcsbpp32
popalias.0x09=dctvm32
popalias.0x0A=dcwfm32
popalias.0x0B=dccoop32
popalias.0x0C=dclra32
popalias.0x0D=dcosp32
popalias.0x0E=dcsecp32
popalias.0x0F=dcifru32
popalias.0x10=dcdrac32
popalias.0x11=dcrac432

I tried to outcomment vil3=nrsvil

but it still doesn't start.

I don't have a LSI storage controller
but I do have Fiber HBA's
[root at mars ini]# lspci
00:00.0 Host bridge: Intel Corporation 5000X Chipset Memory Controller Hub
(rev 12)
00:02.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x4
Port 2 (rev 12)
00:03.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x4
Port 3 (rev 12)
00:04.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x8
Port 4-5 (rev 12)
00:05.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x4
Port 5 (rev 12)
00:06.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x8
Port 6-7 (rev 12)
00:07.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x4
Port 7 (rev 12)
00:10.0 Host bridge: Intel Corporation 5000 Series Chipset Error Reporting
Registers (rev 12)
00:10.1 Host bridge: Intel Corporation 5000 Series Chipset Error Reporting
Registers (rev 12)
00:10.2 Host bridge: Intel Corporation 5000 Series Chipset Error Reporting
Registers (rev 12)
00:11.0 Host bridge: Intel Corporation 5000 Series Chipset Reserved
Registers (rev 12)
00:13.0 Host bridge: Intel Corporation 5000 Series Chipset Reserved
Registers (rev 12)
00:15.0 Host bridge: Intel Corporation 5000 Series Chipset FBD Registers
(rev 12)
00:16.0 Host bridge: Intel Corporation 5000 Series Chipset FBD Registers
(rev 12)
00:1c.0 PCI bridge: Intel Corporation 631xESB/632xESB/3100 Chipset PCI
Express Root Port 1 (rev 09)
00:1d.0 USB Controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI
USB Controller #1 (rev 09)
00:1d.1 USB Controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI
USB Controller #2 (rev 09)
00:1d.2 USB Controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI
USB Controller #3 (rev 09)
00:1d.7 USB Controller: Intel Corporation 631xESB/632xESB/3100 Chipset EHCI
USB2 Controller (rev 09)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev d9)
00:1f.0 ISA bridge: Intel Corporation 631xESB/632xESB/3100 Chipset LPC
Interface Controller (rev 09)
00:1f.1 IDE interface: Intel Corporation 631xESB/632xESB IDE Controller (rev
09)
01:00.0 PCI bridge: Intel Corporation 80333 Segment-A PCI Express-to-PCI
Express Bridge
01:00.2 PCI bridge: Intel Corporation 80333 Segment-B PCI Express-to-PCI
Express Bridge
02:0e.0 RAID bus controller: Dell PowerEdge Expandable RAID controller 5
04:00.0 PCI bridge: Broadcom: Unknown device 0103 (rev c3)
05:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5708
Gigabit Ethernet (rev 12)
06:00.0 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express Upstream
Port (rev 01)
06:00.3 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express to PCI-X
Bridge (rev 01)
07:00.0 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express Downstream
Port E1 (rev 01)
07:01.0 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express Downstream
Port E2 (rev 01)
08:00.0 PCI bridge: Broadcom: Unknown device 0103 (rev c3)
09:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5708
Gigabit Ethernet (rev 12)
0c:00.0 Fibre Channel: QLogic Corp. QLA2432 Fibre Channel Adapter (rev 02)
0e:00.0 Fibre Channel: QLogic Corp. QLA2432 Fibre Channel Adapter (rev 02)
10:0d.0 VGA compatible controller: ATI Technologies Inc ES1000 (rev 02)

So what do I try next?

Thanks,
Jan



On 4/26/07, Patrick_Boyd at dell.com <Patrick_Boyd at dell.com> wrote:
>
> I will look into this. For now in the /opt/dell/srvadmin/sm/stsvc.ini
> file you can disable our enumeration of Non-RAID Controllers by
> commenting out the following line vil3=nrsvil with a semicolon. This
> should allow you to add the ral line back in so that you can still
> manage and monitor your PERC controller and MD1000.
>
> If you are feeling generous the following information will help me to
> debug this:
> 1. A debug log from the storage component. You can enable this by
> setting the debug flag to on and the debugmask to 3's in the stsvc.ini
> file mentioned above.
> 2. What OS are you running?
> 3. Complete lspci -v output from your LSI SCSI card.
>
> Thanks,
> Patrick Boyd
>
>
>
> -----Original Message-----
> From: Mansell, Gary [mailto:Gary.Mansell at ricardo.com]
> Sent: Thursday, April 26, 2007 10:09 AM
> To: Boyd, Patrick
> Cc: linux-poweredge-Lists
> Subject: RE: Starting dsm_sa_datamgr32d FAILED
>
> Hi,
>
> Dell UK supplied me these to get around the problem with the Adaptec
> cards that they originally supplied:
>
> 12:04.0 SCSI storage controller: LSI Logic / Symbios Logic 53c1030 PCI-X
> Fusion-MPT Dual Ultra320 SCSI (rev 08)
> 12:04.1 SCSI storage controller: LSI Logic / Symbios Logic 53c1030 PCI-X
> Fusion-MPT Dual Ultra320 SCSI (rev 08)
>
>
>
>
>
> On Thu, 2007-04-26 at 10:04 -0500, Patrick_Boyd at Dell.com wrote:
> > Out of curiosity which LSI SCSI HBA are you using? We've tested with
> all
> > of them that Dell ships without any issues.
> >
> > -----Original Message-----
> > From: linux-poweredge-bounces at dell.com
> > [mailto:linux-poweredge-bounces at dell.com] On Behalf Of Mansell, Gary
> > Sent: Thursday, April 26, 2007 9:56 AM
> > To: linux-poweredge-Lists
> > Subject: Re: Starting dsm_sa_datamgr32d FAILED
> >
> > Hi,
> >
> > I have experienced the same problem with OMSA 5.2
> >
> > It has occurred on my machine since I applied the latest firmware
> > updates for my PE2950 and MD1000. In my case it seems to be related to
> a
> > conflict between my LSI HBA SCSI Card and the Firmware upgrade. If I
> > remove the LSI card from the system OMSA 5.2 works fine.
> >
> > Unfortunately removing the LSI SCSI HBA means that I cannot perform
> > backups !!! The Overland Neo2000 tape library will not work with
> Adaptec
> > SCSI HBA's !!!
> >
> > Another solution is to comment out the following line in one of the
> OMSA
> > config files - this stops OMSA 5.2 running the Storage component and
> > hence you get no reporting.
> >
> > Edit /opt/dell/srvadmin/dataeng/ini/dcdmdy32.ini and comment out the
> > line:
> >
> > popalias.0x0F=ral32
> >
> > by putting a semi colon in front of it.
> >
> > restart OMSA with srvadmin-services.sh restart
> >
> >
> > Hope that helps
> >
> > Gary
> > - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
> -
> > - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
> -
> > - - - - - - - - - - - - -
> > This e-mail and any files transmitted with it are confidential and
> > intended solely for the use of the individual or entity to whom they
> are
> > addressed.If you have received this e-mail in error please notify the
> > sender immediately and delete this e-mail from your system.Please note
> > that any views or opinions presented in this e-mail are solely those
> of
> > the author and do not necessarily represent those of Ricardo (save for
> > reports and other documentation formally approved and signed for
> release
> > to the intended recipient).Only Directors are authorised to enter into
> > legally binding obligations on behalf of Ricardo. Ricardo may monitor
> > outgoing and incoming e-mails and other telecommunications systems.
> > By replying to this e-mail you give consent to such monitoring.The
> > recipient should check e-mail and any attachments for the presence of
> > viruses. Ricardo accepts no liability for any damage caused by any
> virus
> > transmitted by this e-mail. "Ricardo" means Ricardo plc and its
> > subsidiary companies.
> > Ricardo plc is a public limited company registered in England with
> > registered number 00222915.
> > The registered office of Ricardo plc is Shoreham Technical Centre,
> > Shoreham-by Sea, West Sussex, BN43 5FG.
> > - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
> -
> > - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
> -
> > - - - - - - - - - - - - -
> >
> > _______________________________________________
> > Linux-PowerEdge mailing list
> > Linux-PowerEdge at dell.com
> > http://lists.us.dell.com/mailman/listinfo/linux-poweredge
> > Please read the FAQ at http://lists.us.dell.com/faq
>
> _______________________________________________
> Linux-PowerEdge mailing list
> Linux-PowerEdge at dell.com
> http://lists.us.dell.com/mailman/listinfo/linux-poweredge
> Please read the FAQ at http://lists.us.dell.com/faq
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.us.dell.com/pipermail/linux-poweredge/attachments/20070426/7ad1f8d7/attachment-0001.htm 


More information about the Linux-PowerEdge mailing list