It is a known problem that grub does not install properly with the installer with the current update release kernel. I suspect that something has changed in the kernel rpm install scripts, I'm not exactly sure what. One easy work-around is to always select lilo in the installer, then run grub-install after the system has rebooted. Running grub-install might be successfully done before reboot in a %post section of a kickstart file or at the Alt-F2 console at the end of the install, I haven't tried doing that. (From what is said below, it seems that it is once the config file is modified). Cheers Tony (PS: my howto at www.linuxworks.com.au/redhat-installer-howto.html needs to be updated to mention this problem). On Mon Jul 29 2002 at 14:33, "Beattie, Chad" wrote to kickstart list: > Just an FYI. As one last resort, I did a system erase with > smartstart, then re-configured the arrays, re-install > smartstart utils, ran my ks install again, and it all works now. I > must have really messed something up. > anyway, thanks for all of the help. > > > -----Original Message----- > From: Beattie, Chad > Sent: Thursday, July 18, 2002 4:09 PM > To: kickstart-list@xxxxxxxxxx > Subject: RE: Upgrade kernel from kickstart > > > > *** PGP Signature Status: good > *** Signer: Chad C. Beattie > *** Signed: 7/18/2002 4:09:17 PM > *** Verified: 7/29/2002 2:31:39 PM > *** BEGIN PGP VERIFIED MESSAGE *** > > > > I have not been able to get grub to work on this system. I have > tried manually installing RedHat 7.3 and choosing grub instead of > lilo. After the system is booted, the kernel loads, but then it is > unable to pass control to init. I get a message saying it could not > mount the ext3 file system and then it cannot find /sbin/init. From > what I can tell, grub is installed and configured correctly. > > -----Original Message----- > From: Buro, Nicholas F [mailto:nicholas_buro@xxxxxxxxx] > Sent: Thursday, July 18, 2002 4:04 PM > To: 'kickstart-list@xxxxxxxxxx' > Subject: RE: Upgrade kernel from kickstart > > > Is there any specific reason you need to use LILO? I have run > into a > similar issue, and my solution with GRUB was to run the following in > the post > > install: > > "perl -pi -e 's/default=.*/default=0/g' /boot/grub/grub.conf" > > Good luck > --N > > -----Original Message----- > From: Beattie, Chad [mailto:Chad.Beattie@xxxxxx] > Sent: Thursday, July 18, 2002 3:24 PM > To: kickstart-list@xxxxxxxxxx > Subject: Upgrade kernel from kickstart > > > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > I am working on automating a RedHat 7.3 setup on a couple of > DL380 > servers. I have built a custom kernel and made an rpm package from > the original src rpm for the generic kernel. After installing the > base os, I copy over some additional rpm files in the %post section > of the script. I then install the rpm packages. After the rpm's are > done, I copy over a pre-made lilo.conf file for the new kernel, the > last command I run from kickstart is /sbin/lilo -v. From watching the > install, everything works fine, even the lilo command works without > any errors. After server is rebooted, it still boots to the old > kernel. If I log into the server and run lilo again and reboot, it > boots to the new kernel. Anything I am missing here? [ ... ] > Chad C. Beattie > Network Engineer > Work 402-758-7744 > Cell 402-203-6437
