RE: ***POSSIBLE SOLUTION*** OM 6.2 Broken Storage Section

2010-04-16 Thread Sijis Aviles
just fine. I hope this helps someone. Sijis -Original Message- Message: 2 Date: Fri, 18 Dec 2009 14:54:12 -0500 From: Ryan Miller rmil...@smartertravelmedia.com Subject: RE: ***POSSIBLE SOLUTION*** OM 6.2 Broken Storage Section To: jeffrey_l_mend...@dell.com jeffrey_l_mend...@dell.com

RE: ***POSSIBLE SOLUTION*** OM 6.2 Broken Storage Section

2009-12-18 Thread Ryan Miller
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

RE: ***POSSIBLE SOLUTION*** OM 6.2 Broken Storage Section

2009-12-18 Thread Ryan Miller
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*

***POSSIBLE SOLUTION*** OM 6.2 Broken Storage Section

2009-12-17 Thread Aaron McKinnon
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

Re: ***POSSIBLE SOLUTION*** OM 6.2 Broken Storage Section

2009-12-17 Thread Dimitri Yioulos
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 -

***POSSIBLE SOLUTION*** OM 6.2 Broken Storage Section

2009-12-17 Thread Ryan Miller
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