Hi, try stopping omsa before running the firmware update:
# srvadmin-services.sh stop Paul ----- Original Message ----- From: "Albretch Mueller" <[email protected]> To: [email protected] Sent: Wednesday, January 27, 2010 10:25:02 AM (GMT-0600) America/Chicago Subject: How could I install/update ESM? After updating the BIOS on my PE 1850 ~ # getSystemId Libsmbios: 0.12.1 System ID: 0x016C Service Tag: xxx Express Service Code: xxx Product Name: PowerEdge 1850 BIOS Version: A07 Vendor: Dell Computer Corporation Is Dell: 1 ~ I couldn't find an exact match for the ESM software I should use. I was adviced to use: ~ BMC_FRMW_LX_R223068.BIN ~ but it is giving me the following errors: ~ Dell Update Package 6.2 (BLD_288) Copyright (c) 2003-2009 Dell, Inc. All Rights Reserved. Release Title: Dell BMC Firmware, v.1.83, A10 Release Date: June 30, 2009 Default Log File Name: R223068 Supported System(s): PowerEdge 1850 Description: BMC firmware Supported Device(s): BMC Firmware Fixes / Enhancements: Fix the incorrect entity instance number of CPUs and PSUs shown in the inventory info of VMware ESX. Important Device Information: * Do not run other applications while executing Dell Update Packages. * The software contained in a Dell Update Package for Linux is an aggregate of third party programs as well as Dell programs. Use of the software is subject to designated license terms. All Software that is designated as "under the terms of the GNU GPL" may be copied, distributed and/or modified in accordance with the terms and conditions of the GNU General Public License, Version 2, June 1991. All software that is designated as "under the terms of the GNU LGPL" (or "Lesser GPL") may be copied, distributed and/or modified in accordance with the terms and conditions of the GNU Lesser General Public License, Version 2.1, February 1999. Under these GNU licenses, you are also entitled to obtain the corresponding source files by contacting Dell at 1-800-WWW-DELL. Please refer to the Open Manage Open Source DVD. There may be a nominal fee charged to you for the physical act of transferring a copy. Collecting inventory... .......Τρι 26 Ιαν 2010 11:05:11 μμ EET warning: srvadmin-omilcore-6.1.0-426.i386.rpm: Header V3 DSA signature: NOKEY, key ID 23b66a9d error: Failed dependencies: rpm >= 4.0.4 is needed by srvadmin-omilcore-6.1.0-426.i386 pciutils is needed by srvadmin-omilcore-6.1.0-426.i386 /bin/sh is needed by srvadmin-omilcore-6.1.0-426.i386 warning: srvadmin-ipmi-6.1.0-426.DUP.i386.rpm: Header V3 DSA signature: NOKEY, key ID 23b66a9d error: Failed dependencies: /bin/sh is needed by srvadmin-ipmi-6.1.0-426.DUP.i386 warning: srvadmin-hapi-6.1.0-426.i386.rpm: Header V3 DSA signature: NOKEY, key ID 23b66a9d error: Failed dependencies: srvadmin-omilcore = 6.1.0 is needed by srvadmin-hapi-6.1.0-426.i386 srvadmin-ipmi = 6.1.0 is needed by srvadmin-hapi-6.1.0-426.i386 /bin/sh is needed by srvadmin-hapi-6.1.0-426.i386 libc.so.6 is needed by srvadmin-hapi-6.1.0-426.i386 libdl.so.2 is needed by srvadmin-hapi-6.1.0-426.i386 libm.so.6 is needed by srvadmin-hapi-6.1.0-426.i386 libpthread.so.0 is needed by srvadmin-hapi-6.1.0-426.i386 libc.so.6(GLIBC_2.0) is needed by srvadmin-hapi-6.1.0-426.i386 libc.so.6(GLIBC_2.1) is needed by srvadmin-hapi-6.1.0-426.i386 libc.so.6(GLIBC_2.2) is needed by srvadmin-hapi-6.1.0-426.i386 libc.so.6(GLIBC_2.3) is needed by srvadmin-hapi-6.1.0-426.i386 libdl.so.2(GLIBC_2.0) is needed by srvadmin-hapi-6.1.0-426.i386 libdl.so.2(GLIBC_2.1) is needed by srvadmin-hapi-6.1.0-426.i386 libm.so.6(GLIBC_2.0) is needed by srvadmin-hapi-6.1.0-426.i386 libpthread.so.0(GLIBC_2.0) is needed by srvadmin-hapi-6.1.0-426.i386 libpthread.so.0(GLIBC_2.1) is needed by srvadmin-hapi-6.1.0-426.i386 libpthread.so.0(GLIBC_2.2) is needed by srvadmin-hapi-6.1.0-426.i386 Executing: rpm -e srvadmin-hapi error: package srvadmin-hapi is not installed Executing: rpm -e srvadmin-ipmi error: package srvadmin-ipmi is not installed Executing: rpm -e srvadmin-omilcore error: package srvadmin-omilcore is not installed removeDrivers returning 1 . Running validation... This Update Package is not compatible with your system configuration. ~ =================> Dell Update Package application started <============= Command: Date: Tue 26 Jan 2010 11:05:07 EST ========================================================================= Release ID: R223068 Update Package version: 6.2 (BLD_288) Collecting inventory... <SVMInventory lang="en"><System systemID="16C"/><OperatingSystem majorVersion="2.6" minorVersion="19" spMajorVersion="0" spMinorVersion="0" ></OperatingSystem><Device componentID="159" display="BIOS" impactsTPMmeasurements="TRUE"><Display>BIOS</Display><Application componentType="BIOS" version="A07" display="BIOS" /></Device></SVMInventory> MovePayload: Entry MovePayload: Processing payload directory. MovePayload: Moving bmcflsh.dat MovePayload: Exiting. Running validation... This Update Package is not compatible with your system configuration. ==============================> Update Result <========================== Update was not applied ========================================================================= Exit code = 5 (Qualification error) <?xml version="1.0" encoding="UTF-16"?> <SoftwareComponent schemaVersion="1.0" packageID="R223068" releaseID="R223068" dateTime="2009-06-30T14:11:47-05:00" releaseDate="June 30, 2009" vendorVersion="1.83" dellVersion="A10" packageType="LLXP" xmlGenVersion="1.0.3555"> <Name> <Display lang="en"><![CDATA[Dell BMC Firmware, v.1.83, A10]]></Display> </Name> <ComponentType value="FRMW"> <Display lang="en"><![CDATA[Firmware]]></Display> </ComponentType> <Description> <Display lang="en"><![CDATA[BMC firmware]]></Display> </Description> <LUCategory value="BMC"> <Display lang="en"><![CDATA[Server Firmware BMC]]></Display> </LUCategory> <Category value="ES"> <Display lang="en"><![CDATA[Embedded Server Management]]></Display> </Category> <SupportedDevices> <Device componentID="5814" embedded="1"> <Display lang="en"><![CDATA[BMC Firmware]]></Display> </Device> </SupportedDevices> <SupportedSystems display="1"> <Brand key="3" prefix="PE"> <Display lang="en"><![CDATA[PowerEdge]]></Display> <Model systemID="016C"> <Display lang="en"><![CDATA[1850]]></Display> </Model> </Brand> </SupportedSystems> <InstallInstruction fileName="BMC_FRMW_LX_R223068.BIN" typeCode="LLXP"> <Display lang="en"><![CDATA[Dell Update Package Instructions for BMC_FRMW_LX_R223068.BIN: Installation 1. Read over the release information presented by executing the "./BMC_FRMW_LX_R223068.BIN --version" command from the shell. 2. Download and install any prerequisites identified in the above step before proceeding. 3. If it is a BIOS update package, install any necessary Embedded Systems Management firmware prior to this BIOS update. 4. Run the update by executing "./BMC_FRMW_LX_R223068.BIN" from the shell. 5. Follow the remaining prompts to perform the update. ]]></Display> </InstallInstruction> <RevisionHistory> <Display lang="en"><![CDATA[Fix the incorrect entity instance number of CPUs and PSUs shown in the inventory info of VMware ESX.]]></Display> </RevisionHistory> <ImportantInfo URL="http://support.dell.com/support/downloads/format.aspx?releaseid=R223068&c=us&l=en&s=gen&cs";> <Display lang="en"><![CDATA[############################################################### Important Information for Update Packages for Microsoft Windows ############################################################### * Do not run other applications while executing Dell Update Packages. * When upgrading the BMC/ESM firmware or the BP firmware on PowerEdge x8xx or x9xx servers with the Windows Server 2003 R2 IPMI driver installed, the update may take up to 20 minutes to complete. To speed up the time it takes to perform such updates on PowerEdge x8xx or x9xx servers, you can uninstall the R2 IPMI driver before performing the firmware upgrade operation using the command "rundll32 ipmisetp.dll, RemoveTheDevice" from a command prompt. After the firmware flash is complete, you can install the driver again by executing the command "rundll32 ipmisetp.dll, AddTheDevice". On PowerEdge x9xx servers, the driver can be re-installed by performing a "Scan for hardware changes" in the Device Manager. * When upgrading the BMC/ESM firmware on PowerEdge x8xx or x9xx servers with the Windows Server 2003 R2 IPMI driver installed, multiple time-out warning messages from source "IPMIDRV" with Event ID 1004 are logged in the System Log in the Event Viewer console. These messages can be safely ignored. However, to prevent the messages from being logged, you can uninstall the R2 IPMI driver before performing the firmware upgrade operation using the command "rundll32 ipmisetp.dll, RemoveTheDevice" from a command prompt. After the firmware flash is complete, you can install the driver again by executing the command "rundll32 ipmisetp.dll, AddTheDevice". On PowerEdge x9xx servers, the driver can be re-installed by performing a "Scan for hardware changes" in the Device Manager. For more information on this issue, including information on the cause of this issue, see the Microsoft KB article number 912596. ################################################### Important Information for Update Packages for Linux ################################################### * Do not run other applications while executing Dell Update Packages. * If the following error occurs, "Error while loading shared libraries: libstdc++.so.5: cannot open shared object file: No such file or directory", you must install the compatibility libraries from "www.redhat.com" or from the Red Hat CD. To install the compatibility libraries, use the following command: "RPM -ih compat-libstdc++-33-3.2.3-47.3.i386.rpm" * Dell Update Packages for BMC, BP, ESM, and DRAC5 require the OpenIPMI driver to be loaded on your system. The current drivers can be downloaded from the Dell Support website at "support.dell.com". ]]></Display> </ImportantInfo> <Criticality value="3"> <Display lang="en"><![CDATA[Optional-Dell recommends the customer review specifics about the update to determine if it applies to your system. The update contains changes that impact only certain configurations, or provides new features that may/may not apply to your environment.]]></Display> </Criticality> </SoftwareComponent> Tue 26 Jan 2010 11:05:07 EST ~ How could I update/install ESM in my server? Thank you lbrtchx _______________________________________________ Linux-PowerEdge mailing list [email protected] https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq _______________________________________________ Linux-PowerEdge mailing list [email protected] https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
