@jwegman hmm... I don't see how resetting the BIOS default settings directly contributes to the failure of the FRUSDR updates process, the last update in the set of four firmware updates. I installed the board into the chassis and powered on once with no drives. I then powered on with USB installed and proceeded to update the BIOS and the other firmwares where upon the FRUSDR failed to update. I was having issues with the FRUSDR update process twice using the firmware set with BIOS 2.05.0004. I tried it a third time with firmware set with BIOS 2.06.0002, and eventually had success. It's possible that running the duo "syscfg /rfs" and "syscfg /rBMC" were unnecessary. But forcing the system to use the "S2600CP.fru" file seemed to rather quickly resolve the failure and allowed the FRUSDR update process to complete and then reduce the loud fast-spinning fan noise. It's possible that the the BIOS settings were not reset appropriately. However, I only have one system to work with and these are the steps that I took. The conclusion I've come to is based on
@DavidVermillion 's post about possible file corruption or errors introduced by the system integrator having some funky name with his S2600CP board causing havoc and how the FRUSDR update process was not working. As I recall, his did not explain the nature of the error, only that it didn't work. Whereas I have paraphrased in an attempt to give direction to the type of error message that I had. It seems some systems update very nicely while others simply cause headaches while they seemingly crash and burn.
Thanks for the the details on where to find the SEL. I'm sure I would have gotten there eventually, but I don't have an active network connection to the server to work with at this time. Unfortunately, my modem and router sit in the back bedroom near the short stubby cable source that's in the closet ceiling while the server sits near the computer with a wireless internet connection in the front of the apartment. I suppose getting into wild and exotic configurations (such as Window's internet connection sharing (or however they have it named now), or a cumbersome wireless bridge [a switch with a wireless radio A, B, G, N, AC, etc.]) would also work.
@nthu9280 .. Yeah, I've read about that here. Thanks for the heads up. I will check that next before I have more mind numbing issues
(Yeah, it's very frustrating to have "banging head on wall" moments. Even worse is when it is your own work working against you.
"Measured once, cut twice, and still too short"
Aaah, oops!
And "'I see,' said the blind man, who picked up his hammer and saw.")
@Boddy .. I hope your system build and updating is trouble free.