Hi Steve:
Try this newer version of
SystemConfigurator from OSCAR trunk and see if it works for you.
Supposedly it fixes some RHEL4 grub-related issues:
Cheers,
Bernard
From: [EMAIL PROTECTED] on behalf of Kan Tok
Sent: Sat 07/01/2006 19:03
To: sisuite-users@lists.sourceforge.net
Subject: RE: [Sisuite-users] Grub issues with IBM HS20 Bladecenter
Bernard,
Good evening. I'm using the packages provided for in the guide, so it's the systemconfigurator-2.2.2-1.noarch.rpm package. I had read of some interesting problems with grub when you have your machine raided, but I don't have a raid array setup for these machines. . Please let me know if there's any other relevant information I can provide. Thanks again.
Steve
How To being used:
http://www.opensubscriber.com/message/sisuite-users@lists.sourceforge.net/1483555.html
Bernard Li <[EMAIL PROTECTED]> wrote:
Good evening. I'm using the packages provided for in the guide, so it's the systemconfigurator-2.2.2-1.noarch.rpm package. I had read of some interesting problems with grub when you have your machine raided, but I don't have a raid array setup for these machines. . Please let me know if there's any other relevant information I can provide. Thanks again.
Steve
How To being used:
http://www.opensubscriber.com/message/sisuite-users@lists.sourceforge.net/1483555.html
Bernard Li <[EMAIL PROTECTED]> wrote:
Hi Steve:Which version of SystemConfigurator are you using?Cheers,Bernard
From: [EMAIL PROTECTED] on behalf of Kan Tok
Sent: Fri 06/01/2006 21:04
To: sisuite-users@lists.sourceforge.net
Subject: [Sisuite-users] Grub issues with IBM HS20 BladecenterGood day,
We have s everal IBM Blade Chassis (with HS20s) that we had been successfuly administering with an older version of systemimager and rh9. We were required recently to upgrade to rhel 4.0 and, as such, upgrade our version of systemimager to 3.5.2. We followed the excellent guide and files provided by Mr. Nielsen. With that guide, combined with a couple of hacks mentioned below, we got the image to be grabbed from a golden client built by hand and then pushed to new blades successfully. However, when we try to push the same image to a blade with the same exact hardware, but with a BIOS level of 1.06 (as opposed to a BIOS of 1.05 of the machines that are working), the machine hangs on its first reboot after image push. As mentioned below, even on machines that we get to work, it seems there's some sort of problem with how the bootloader is being handled (not sure what finally arranges that in the process, systemconfigurator?)
The symptom on the non-working machine is that it gets past loading the BIOS and displays only the word: GRUB and is unresponsive then to keystrokes. We've verified that the image is being pushed to the new blade with the BIOS 1.06 (we modified the .master script so that it wouldn't partition the drives and put a sleep command in there so we could ctrl-c to get to the command prompt of ash and we see the directory structure loaded under /a/ as it seems like it should, including the /boot/grub files), but it seems like something is wrong with how grub is being loaded to the MBR or its not being loaded at all (as I don't see any messages saying it is going to stage 1.5 and no menu for 2 is show.)
I'm afraid I'm new to these listings, but I have followed them for almost two years now and have been impressed with the knowledge of the participants.&n bsp; Any suggestions, comments or even anecdotes on reaching a solution to this problem would be greatly appreciated. Thank you.
Steve
"What we had to hack to get it working on an IBM Blade":
Although the rpms and guide by Ole Holm Nielsen were good, there were several issues we had to work through to get systemimager working on the blade hardware. Our final solution involved using our original initrd from the old blades we had working with the old systemimager, adding some files to the boel_binaries.tar.gz, such as /etc/init.d/functions I think (sorry away from the chassis as I write this) so that systemimager would have what it would need to execute the .master scipt properly. The image would push fine (with some messages about unresolved symbols) but then after it was done pushing and the reboot happened the machine would first go through the BIOS as normal but then instead of loading GRUB properly it would display as message about grub. I forget the exact wording but it was a paragraph describing some basic grub shell functionality and then gave the grub shell prompt.
At this prompt, we then mounted the grub bootloader with
root (hd0,0)
setup (hd0)
reboot
in the prompt. Unfortunately, as I mentioned above, this prompt never appears with the version 1.05 IBM Blade BIOS. It just sits with GRUB on the screen, unresponsive. We've been toying with including /sbin/grub (and other appropriate files) to try to load the bootloader into the MBR by hand after the image is pushed (by taking the reboot out of the .master script) but whenever we try and perform a root(hd0,0) it gives an error saying there's no such device (which I guess makes sense considering everything is mounted kinda wonky at that point.)
BIOS issues:
We've done some research on IBM's support site, but they have a very t hin level of documentation and they seem to have stopped carrying the 1.06 BIOS lev el in their archives. Upgrading to the newest BIOS 1.10 would be a serious difficulty for us given some issues with version control their trying to enact around here.
If you've read all this, thanks, I really appreciate the help.
Yahoo! Photos
Got holiday prints? See all the ways to get quality prints in your hands ASAP.
Yahoo! Photos
Got holiday prints? See all the ways to get quality prints in your hands ASAP.
