RE: ***POSSIBLE SOLUTION*** OM 6.2 Broken Storage Section
I wasn't able to find if there was a resolution to this, so I'll post what worked for me. I installed 6.2 on a 2950 as noted in http://linux.dell.com/repo/hardware/OMSA_6.2/ When I started the services # srvadmin-services.sh start I got an error like this "Error while loading shared libraries: libstdc++.so.5" but the service was showing at started. After doing some digging, I found this readme (http://ftp.dell.com/diags/DR5125A0.txt) which noted to install the compatibility librairies. # yum install compat-libstdc++-33 (the one thing not mentioned) Once I did that, storage started to work just fine. I hope this helps someone. Sijis -Original Message- Message: 2 Date: Fri, 18 Dec 2009 14:54:12 -0500 From: Ryan Miller Subject: RE: ***POSSIBLE SOLUTION*** OM 6.2 Broken Storage Section To: "jeffrey_l_mend...@dell.com" , "linux-powere...@lists.us.dell.com" Message-ID: Content-Type: text/plain; charset="us-ascii" Turns out that the reason that srvadmin-all wouldn't install after just editing the .repo file to say OMSA_6.1 instead of latest and the failure of update_firmware were related: something strange with dependency resolution around libsmbios means that for things to work I need to remove that package before upgrading or downgrading; seems like a specific version of python-smbios is required, but I'm able to downgrade srvadmin* without yum throwing a conflict or dependency. Not sure what's wrong with the dependency graph or how to give you more useful information, but at least now I have a way back onto 6.1, and update_firmware now works with 6.2. Still not seeing the disk controllers under 6.2 no matter what I do though, for SAS or PERC6, on 1950-III or R610. Hope that's at least moderately helpful, and let me know if there's some way I can provide better information. Ryan From: jeffrey_l_mend...@dell.com [mailto:jeffrey_l_mend...@dell.com] Sent: Friday, December 18, 2009 12:12 PM To: Ryan Miller; linux-powere...@lists.us.dell.com Subject: RE: ***POSSIBLE SOLUTION*** OM 6.2 Broken Storage Section Ryan, Thanks for the report on the firmware update exception. What distro/version are you running? Would you mind posting the output with '--verbose'? Thanks, Jeff From: linux-poweredge-bounces-Lists On Behalf Of Ryan Miller Sent: Thursday, December 17, 2009 7:03 PM To: linux-poweredge-Lists Subject: ***POSSIBLE SOLUTION*** OM 6.2 Broken Storage Section I'm also seeing this issue, and no luck with the workaround either. (Plus I had to manually unload the ipmi module-stopping the service didn't do it).I opened a support case and he tried suggested to use the driver from the website - v00.00.03.21 instead of the 00.00.04.08 in the 2.6.18-164.6.1.el5 kernel, but as this kernel and hardware play fine with OMSA6.1 I didn't really want to go that direction (and doubt it would help anyway). Also, firmware updates seem to be broken: [r...@write1y ~]# update_firmware --yes Running system inventory... Searching storage directory for available BIOS updates... Checking BIOS - 1.2.6 Available: dell_dup_componentid_00159 - 1.3.6 Found Update: dell_dup_componentid_00159 - 1.3.6 Checking MBE2147RC Firmware - d701 Available: dell_dup_componentid_20515 - d903 Found Update: dell_dup_componentid_20515 - d903 Checking SAS/SATA Backplane 0:0 Backplane Firmware - 1.07 Available: dell_dup_componentid_11204 - 1.05 Did not find a newer package to install that meets all installation checks. Checking PERC 6/i Integrated Controller 0 Firmware - 6.2.0-0013 Available: pci_firmware(ven_0x1000_dev_0x0060_subven_0x1028_subdev_0x1f0c) - 6.2.0-0013 Did not find a newer package to install that meets all installation checks. Checking System BIOS for PowerEdge R610 - 1.2.6 Did not find a newer package to install that meets all installation checks. Found firmware which needs to be updated. Running updates... | Installing dell_dup_componentid_00159 - 1.3.6Traceback (most recent call last): File "/usr/sbin/update_firmware", line 23, in ? ftmain.main(sys.argv[1:]) File "/usr/share/firmware-tools/ftmain.py", line 109, in main result, resultmsgs = base.doCommands() File "", line 3, in doCommands File "/usr/lib/python2.4/site-packages/firmwaretools/trace_decorator.py", line 81, in trace result = func(*args, **kw) File "/usr/share/firmware-tools/cli.py", line 134, in doCommands self.opts.mode, self.fullCmdLine, self.args) File "", line 3, in doCommand File "/usr/lib/python2.4/site-packages/firmwaretools/trace_decorator.py", line 81, in trace result = func(*args, **kw) File "/usr/share/firmware-tools/plugins/update_cmd.py", line 61, in doCommand base.updateF
RE: ***POSSIBLE SOLUTION*** OM 6.2 Broken Storage Section
Just to get this out into Google for anybody else that's been having trouble rolling back to 6.1, I ended up with the following order of operations: 1.Replace the .repo file with the OMSA_6.1-specific version (replace "latest" with "OMSA_6.1" 2. Yum remove libsmbios srvadmin* sblim-sfcb 3. Yum install yum-dellsysid 4. Yum clean metadata 5. Yum install srvadmin-all I believe that step 2 implies a bug in the dependency graph, because libsmbios is a dependency of yum-dellsysid, so the latter is uninstalled also, but then the correct version cannot be installed in step3 because it introduces a conflict with sblim-sfcb, which implies that that package should have been listed as a dep of yum-dellsysid and removed with it in the first place. I think something similar holds with srvadmin and libsmbios, but I'm less clear on the details. Ryan ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
RE: ***POSSIBLE SOLUTION*** OM 6.2 Broken Storage Section
Turns out that the reason that srvadmin-all wouldn't install after just editing the .repo file to say OMSA_6.1 instead of latest and the failure of update_firmware were related: something strange with dependency resolution around libsmbios means that for things to work I need to remove that package before upgrading or downgrading; seems like a specific version of python-smbios is required, but I'm able to downgrade srvadmin* without yum throwing a conflict or dependency. Not sure what's wrong with the dependency graph or how to give you more useful information, but at least now I have a way back onto 6.1, and update_firmware now works with 6.2. Still not seeing the disk controllers under 6.2 no matter what I do though, for SAS or PERC6, on 1950-III or R610. Hope that's at least moderately helpful, and let me know if there's some way I can provide better information. Ryan From: jeffrey_l_mend...@dell.com [mailto:jeffrey_l_mend...@dell.com] Sent: Friday, December 18, 2009 12:12 PM To: Ryan Miller; linux-powere...@lists.us.dell.com Subject: RE: ***POSSIBLE SOLUTION*** OM 6.2 Broken Storage Section Ryan, Thanks for the report on the firmware update exception. What distro/version are you running? Would you mind posting the output with '--verbose'? Thanks, Jeff From: linux-poweredge-bounces-Lists On Behalf Of Ryan Miller Sent: Thursday, December 17, 2009 7:03 PM To: linux-poweredge-Lists Subject: ***POSSIBLE SOLUTION*** OM 6.2 Broken Storage Section I'm also seeing this issue, and no luck with the workaround either. (Plus I had to manually unload the ipmi module-stopping the service didn't do it).I opened a support case and he tried suggested to use the driver from the website - v00.00.03.21 instead of the 00.00.04.08 in the 2.6.18-164.6.1.el5 kernel, but as this kernel and hardware play fine with OMSA6.1 I didn't really want to go that direction (and doubt it would help anyway). Also, firmware updates seem to be broken: [r...@write1y ~]# update_firmware --yes Running system inventory... Searching storage directory for available BIOS updates... Checking BIOS - 1.2.6 Available: dell_dup_componentid_00159 - 1.3.6 Found Update: dell_dup_componentid_00159 - 1.3.6 Checking MBE2147RC Firmware - d701 Available: dell_dup_componentid_20515 - d903 Found Update: dell_dup_componentid_20515 - d903 Checking SAS/SATA Backplane 0:0 Backplane Firmware - 1.07 Available: dell_dup_componentid_11204 - 1.05 Did not find a newer package to install that meets all installation checks. Checking PERC 6/i Integrated Controller 0 Firmware - 6.2.0-0013 Available: pci_firmware(ven_0x1000_dev_0x0060_subven_0x1028_subdev_0x1f0c) - 6.2.0-0013 Did not find a newer package to install that meets all installation checks. Checking System BIOS for PowerEdge R610 - 1.2.6 Did not find a newer package to install that meets all installation checks. Found firmware which needs to be updated. Running updates... | Installing dell_dup_componentid_00159 - 1.3.6Traceback (most recent call last): File "/usr/sbin/update_firmware", line 23, in ? ftmain.main(sys.argv[1:]) File "/usr/share/firmware-tools/ftmain.py", line 109, in main result, resultmsgs = base.doCommands() File "", line 3, in doCommands File "/usr/lib/python2.4/site-packages/firmwaretools/trace_decorator.py", line 81, in trace result = func(*args, **kw) File "/usr/share/firmware-tools/cli.py", line 134, in doCommands self.opts.mode, self.fullCmdLine, self.args) File "", line 3, in doCommand File "/usr/lib/python2.4/site-packages/firmwaretools/trace_decorator.py", line 81, in trace result = func(*args, **kw) File "/usr/share/firmware-tools/plugins/update_cmd.py", line 61, in doCommand base.updateFirmware(base.opts.show_unknown) File "", line 3, in updateFirmware File "/usr/lib/python2.4/site-packages/firmwaretools/trace_decorator.py", line 81, in trace result = func(*args, **kw) File "/usr/share/firmware-tools/cli.py", line 214, in updateFirmware ret = firmwaretools.pycompat.runLongProcess(pkg.install, waitLoopFunction=statusFunc) File "", line 3, in runLongProcess File "/usr/lib/python2.4/site-packages/firmwaretools/trace_decorator.py", line 81, in trace result = func(*args, **kw) File "/usr/lib/python2.4/site-packages/firmwaretools/pycompat.py", line 177, in runLongProcess raise thread.exception xml.parsers.expat.ExpatError: no element found: line 1, column 0 Haven't dug through the python to see what the source of that might be yet, but it certainly works for me with OMSA6.1. Does anyone know what incantation I can substitute in the .repo file for mirrorlist=http://linux.dell.
RE: ***POSSIBLE SOLUTION*** OM 6.2 Broken Storage Section
Ryan, Thanks for the report on the firmware update exception. What distro/version are you running? Would you mind posting the output with '--verbose'? Thanks, Jeff From: linux-poweredge-bounces-Lists On Behalf Of Ryan Miller Sent: Thursday, December 17, 2009 7:03 PM To: linux-poweredge-Lists Subject: ***POSSIBLE SOLUTION*** OM 6.2 Broken Storage Section I'm also seeing this issue, and no luck with the workaround either. (Plus I had to manually unload the ipmi module-stopping the service didn't do it).I opened a support case and he tried suggested to use the driver from the website - v00.00.03.21 instead of the 00.00.04.08 in the 2.6.18-164.6.1.el5 kernel, but as this kernel and hardware play fine with OMSA6.1 I didn't really want to go that direction (and doubt it would help anyway). Also, firmware updates seem to be broken: [r...@write1y ~]# update_firmware --yes Running system inventory... Searching storage directory for available BIOS updates... Checking BIOS - 1.2.6 Available: dell_dup_componentid_00159 - 1.3.6 Found Update: dell_dup_componentid_00159 - 1.3.6 Checking MBE2147RC Firmware - d701 Available: dell_dup_componentid_20515 - d903 Found Update: dell_dup_componentid_20515 - d903 Checking SAS/SATA Backplane 0:0 Backplane Firmware - 1.07 Available: dell_dup_componentid_11204 - 1.05 Did not find a newer package to install that meets all installation checks. Checking PERC 6/i Integrated Controller 0 Firmware - 6.2.0-0013 Available: pci_firmware(ven_0x1000_dev_0x0060_subven_0x1028_subdev_0x1f0c) - 6.2.0-0013 Did not find a newer package to install that meets all installation checks. Checking System BIOS for PowerEdge R610 - 1.2.6 Did not find a newer package to install that meets all installation checks. Found firmware which needs to be updated. Running updates... | Installing dell_dup_componentid_00159 - 1.3.6Traceback (most recent call last): File "/usr/sbin/update_firmware", line 23, in ? ftmain.main(sys.argv[1:]) File "/usr/share/firmware-tools/ftmain.py", line 109, in main result, resultmsgs = base.doCommands() File "", line 3, in doCommands File "/usr/lib/python2.4/site-packages/firmwaretools/trace_decorator.py", line 81, in trace result = func(*args, **kw) File "/usr/share/firmware-tools/cli.py", line 134, in doCommands self.opts.mode, self.fullCmdLine, self.args) File "", line 3, in doCommand File "/usr/lib/python2.4/site-packages/firmwaretools/trace_decorator.py", line 81, in trace result = func(*args, **kw) File "/usr/share/firmware-tools/plugins/update_cmd.py", line 61, in doCommand base.updateFirmware(base.opts.show_unknown) File "", line 3, in updateFirmware File "/usr/lib/python2.4/site-packages/firmwaretools/trace_decorator.py", line 81, in trace result = func(*args, **kw) File "/usr/share/firmware-tools/cli.py", line 214, in updateFirmware ret = firmwaretools.pycompat.runLongProcess(pkg.install, waitLoopFunction=statusFunc) File "", line 3, in runLongProcess File "/usr/lib/python2.4/site-packages/firmwaretools/trace_decorator.py", line 81, in trace result = func(*args, **kw) File "/usr/lib/python2.4/site-packages/firmwaretools/pycompat.py", line 177, in runLongProcess raise thread.exception xml.parsers.expat.ExpatError: no element found: line 1, column 0 Haven't dug through the python to see what the source of that might be yet, but it certainly works for me with OMSA6.1. Does anyone know what incantation I can substitute in the .repo file for mirrorlist=http://linux.dell.com/repo/hardware/latest/mirrors.cgi?osname=el$releasever&basearch=$basearch&dellsysidpluginver=$dellsysidpluginver to stay on 6.1? Merely swapping 6.1 in for "latest" doesn't work for whatever reason. Thanks, Ryan ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
RE: ***POSSIBLE SOLUTION*** OM 6.2 Broken Storage Section
Does anyone know what incantation I can substitute in the .repo file for mirrorlist=http://linux.dell.com/repo/hardware/latest/mirrors.cgi?osname=el$releasever&basearch=$basearch&dellsysidpluginver=$dellsysidpluginver to stay on 6.1? Merely swapping 6.1 in for "latest" doesn't work for whatever reason. Ryan, You can swap http://linux.dell.com/repo/hardware/latest/ with http://linux.dell.com/repo/hardware/OMSA_6.1/ Or, go to the 6.1 page and run the bootstrap command there: 'wget -q -O - http://linux.dell.com/repo/hardware/OMSA_6.1/bootstrap.cgi | bash' and it will set you up with 6.1. -Jeff ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
***POSSIBLE SOLUTION*** OM 6.2 Broken Storage Section
I'm also seeing this issue, and no luck with the workaround either. (Plus I had to manually unload the ipmi module-stopping the service didn't do it).I opened a support case and he tried suggested to use the driver from the website - v00.00.03.21 instead of the 00.00.04.08 in the 2.6.18-164.6.1.el5 kernel, but as this kernel and hardware play fine with OMSA6.1 I didn't really want to go that direction (and doubt it would help anyway). Also, firmware updates seem to be broken: [r...@write1y ~]# update_firmware --yes Running system inventory... Searching storage directory for available BIOS updates... Checking BIOS - 1.2.6 Available: dell_dup_componentid_00159 - 1.3.6 Found Update: dell_dup_componentid_00159 - 1.3.6 Checking MBE2147RC Firmware - d701 Available: dell_dup_componentid_20515 - d903 Found Update: dell_dup_componentid_20515 - d903 Checking SAS/SATA Backplane 0:0 Backplane Firmware - 1.07 Available: dell_dup_componentid_11204 - 1.05 Did not find a newer package to install that meets all installation checks. Checking PERC 6/i Integrated Controller 0 Firmware - 6.2.0-0013 Available: pci_firmware(ven_0x1000_dev_0x0060_subven_0x1028_subdev_0x1f0c) - 6.2.0-0013 Did not find a newer package to install that meets all installation checks. Checking System BIOS for PowerEdge R610 - 1.2.6 Did not find a newer package to install that meets all installation checks. Found firmware which needs to be updated. Running updates... | Installing dell_dup_componentid_00159 - 1.3.6Traceback (most recent call last): File "/usr/sbin/update_firmware", line 23, in ? ftmain.main(sys.argv[1:]) File "/usr/share/firmware-tools/ftmain.py", line 109, in main result, resultmsgs = base.doCommands() File "", line 3, in doCommands File "/usr/lib/python2.4/site-packages/firmwaretools/trace_decorator.py", line 81, in trace result = func(*args, **kw) File "/usr/share/firmware-tools/cli.py", line 134, in doCommands self.opts.mode, self.fullCmdLine, self.args) File "", line 3, in doCommand File "/usr/lib/python2.4/site-packages/firmwaretools/trace_decorator.py", line 81, in trace result = func(*args, **kw) File "/usr/share/firmware-tools/plugins/update_cmd.py", line 61, in doCommand base.updateFirmware(base.opts.show_unknown) File "", line 3, in updateFirmware File "/usr/lib/python2.4/site-packages/firmwaretools/trace_decorator.py", line 81, in trace result = func(*args, **kw) File "/usr/share/firmware-tools/cli.py", line 214, in updateFirmware ret = firmwaretools.pycompat.runLongProcess(pkg.install, waitLoopFunction=statusFunc) File "", line 3, in runLongProcess File "/usr/lib/python2.4/site-packages/firmwaretools/trace_decorator.py", line 81, in trace result = func(*args, **kw) File "/usr/lib/python2.4/site-packages/firmwaretools/pycompat.py", line 177, in runLongProcess raise thread.exception xml.parsers.expat.ExpatError: no element found: line 1, column 0 Haven't dug through the python to see what the source of that might be yet, but it certainly works for me with OMSA6.1. Does anyone know what incantation I can substitute in the .repo file for mirrorlist=http://linux.dell.com/repo/hardware/latest/mirrors.cgi?osname=el$releasever&basearch=$basearch&dellsysidpluginver=$dellsysidpluginver to stay on 6.1? Merely swapping 6.1 in for "latest" doesn't work for whatever reason. Thanks, Ryan ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
Re: ***POSSIBLE SOLUTION*** OM 6.2 Broken Storage Section
Not sure if I should continue top-posting, but ... Tried your fix on a PE2950 - unfortunately, no joy :-( Dimitri On Thursday 17 December 2009 1:34:47 pm Aaron McKinnon wrote: > On my machines I noticed ipmi was not fully > unloading. Here is what we did to fix it: > > * Stop OMSA > - srvadmin-services.sh stop > * Stop haldaemon - it was determined that for > some reason haldaemon was hanging on to the > ipmi modules... > - service haldaemon stop > - pkill hald-addon* > * Make sure everything is stopped: > - srvadmin-services.sh status > - lsmod | grep ipmi > * Restart haldaemon > - service haldaemon start > * Restart OMSA > - srvadmin-services.sh start > > ...worked on one machine so far. Trying more. > > -Aaron > > Aaron McKinnon wrote: > > Non of our servers can now see the storage > > elements: > > > > # srvadmin-services.sh status > > dell_rbu (module) is running > > ipmi driver is running > > dsm_sa_datamgrd (pid 23010) is running > > dsm_sa_eventmgrd (pid 23122) is running > > dsm_sa_snmpd (pid 23181) is running > > dsm_om_shrsvcd (pid 23256) is running > > dsm_om_connsvcd (pid 23299 23298) is running > > > > # omreport storage controller controller=1 > > Invalid controller value. Read, controller=1 > > Valid values for controller are: 0 > > > > I have three controllers on this machine, but > > no disks on what is listed as zero. > > > > # omreport storage vdisk > > List of Virtual Disks in the System > > > > Controller LSI Logic 1020/1030 Ultra320 SCSI > > Adapter (Slot 2) No virtual disks found > > > > We have restarted OM and snmpd to no avail. > > Ideas? > > > > -Aaron > > > > _ > >__ Linux-PowerEdge mailing list > > Linux-PowerEdge@dell.com > > https://lists.us.dell.com/mailman/listinfo/li > >nux-poweredge Please read the FAQ at > > http://lists.us.dell.com/faq > > ___ > Linux-PowerEdge mailing list > Linux-PowerEdge@dell.com > https://lists.us.dell.com/mailman/listinfo/linu >x-poweredge Please read the FAQ at > http://lists.us.dell.com/faq -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
***POSSIBLE SOLUTION*** OM 6.2 Broken Storage Section
On my machines I noticed ipmi was not fully unloading. Here is what we did to fix it: * Stop OMSA - srvadmin-services.sh stop * Stop haldaemon - it was determined that for some reason haldaemon was hanging on to the ipmi modules... - service haldaemon stop - pkill hald-addon* * Make sure everything is stopped: - srvadmin-services.sh status - lsmod | grep ipmi * Restart haldaemon - service haldaemon start * Restart OMSA - srvadmin-services.sh start ...worked on one machine so far. Trying more. -Aaron Aaron McKinnon wrote: > Non of our servers can now see the storage elements: > > # srvadmin-services.sh status > dell_rbu (module) is running > ipmi driver is running > dsm_sa_datamgrd (pid 23010) is running > dsm_sa_eventmgrd (pid 23122) is running > dsm_sa_snmpd (pid 23181) is running > dsm_om_shrsvcd (pid 23256) is running > dsm_om_connsvcd (pid 23299 23298) is running > > # omreport storage controller controller=1 > Invalid controller value. Read, controller=1 > Valid values for controller are: 0 > > I have three controllers on this machine, but no disks on what is listed > as zero. > > # omreport storage vdisk > List of Virtual Disks in the System > > Controller LSI Logic 1020/1030 Ultra320 SCSI Adapter (Slot 2) > No virtual disks found > > We have restarted OM and snmpd to no avail. Ideas? > > -Aaron > > ___ > Linux-PowerEdge mailing list > Linux-PowerEdge@dell.com > https://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@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
OM 6.2 Broken Storage Section
Non of our servers can now see the storage elements: # srvadmin-services.sh status dell_rbu (module) is running ipmi driver is running dsm_sa_datamgrd (pid 23010) is running dsm_sa_eventmgrd (pid 23122) is running dsm_sa_snmpd (pid 23181) is running dsm_om_shrsvcd (pid 23256) is running dsm_om_connsvcd (pid 23299 23298) is running # omreport storage controller controller=1 Invalid controller value. Read, controller=1 Valid values for controller are: 0 I have three controllers on this machine, but no disks on what is listed as zero. # omreport storage vdisk List of Virtual Disks in the System Controller LSI Logic 1020/1030 Ultra320 SCSI Adapter (Slot 2) No virtual disks found We have restarted OM and snmpd to no avail. Ideas? -Aaron ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
