update firmware

[Michael E Brown]

On Wed, Mar 12, 2008 at 09:40:57AM -0400, J Potter wrote:
> 
> >Are your commands below correct? You need the 'software' and  
> >'firmware' repos to do firmware updates. The 'dell-dup' package is  
> >in the 'software' repo. The 'dell_inventory_collector' package is in  
> >the 'firmware' repo.
> 
> This is on a box that already had stuff installed a while back, so  
> firmware is already on there. I should have included that for  
> clarity's sake.

Ok. thanks for the clarification.

> >The dell-lsiflash package is now obsolete. You should remove it and  
> >any firmware packages that depend on it. I havent quite worked out  
> >an automated way of doing this, unfortunately.
> >The next version of firmware-tools will have a conflicts: tag on  
> >dell-lsiflash so that you can be alerted of the situation, but it  
> >requires manual intervention.
> >
> >I'm a bit unhappy about the situation, because it basically screws  
> >over the people who have used and tested firmware-tools for the  
> >longest time and have the previous packages installed, and I really  
> >appreciate and value all my users. I just dont see any way of  
> >automatically resolving the situation. Suggestions taken...
> 
> I don't mind a one-time "do X to get things working again." The  
> problem is, I've been banging my head against a wall for a week now to  
> figure out what X is to get the firmware updates to the Perc RAID  
> cards, all the while, receiving nagios alerts every hour telling me  
> "storage degraded!". (x 20 servers that are on OMSA 5.3 = a lot of  
> annoying email! Not to mention potentially lost-in-the-noise real  
> problems.)

Yes, understood.

> 
> I've managed to reduce it down to the same OS (CentOS 5), on the same  
> hardware (1850s w/ Perc 4w/Si), and have been able to get one box to  
> install the update, and the second box to not install it.
> 
> The box that it works on is CentOS 5, 32 bit; the one it fails on is  
> CentOS 5, 64 bit. I don't know if this is material, though, just  
> happens to be what I'm working with.

I do almost all of my testing on 64-bit, so I am confident that it
should work.

> I have no idea why one box fails with an "522d does not have an  
> installer available" error and the other box works and applies the  
> firmware update.
> 
> The boxes have the exact same Dell repos in /etc/yum.repos.d/, there  
> are no differences between them when doing a diff:
> 	dell-firmware-repository.repo dell-hw-indep-repository.repo dell-hw- 
> specific-repository.repo dell-unsupported-repository.repo

Ok. good.

> Packages installed with the word "dell" are equal, including the same  
> version:
> 	dell-dup-1.0.5-1.el5
> 	dell-firmware-repository-1-4
> 	dell-hw-indep-repository-1-15
> 	dell-hw-specific-repository-1-13.el5
> 	dell_inventory_collector-5.3.0-1
> 	dell-lsiflash-2.0.6-1.el5
> 	dell-unsupported-repository-1-4.el5
> 	firmware-addon-dell-2.0.11-1.el5
> 
> Per your suggestion, after the above testing, I tried removing dell- 
> lsiflash, but no luck getting it to install. ('rpm -e dell-lsiflash;  
> yum clean all; yum install $(bootstrap_firmware); update_firmware  -- 
> yes'.
> 
> Thoughts? I feel like I must be missing something -- is it not  
> possible to apply this update through packages supplied via yum  
> currently?

Are you still getting the "Error: Missing Dependency: dell-dup ..."?
That could only come if dell-unsupported (the 'software' repository)
isnt working. If the repo files under /etc/yum.repos.d are there, then
it may be a yum caching problem.

Try "yum clean all" on the non-working machine, then redo
the 'yum install $(bootstrap_firmware)' command.

--
Michael