Red Hat Bugzilla – Bug 178815
kickstart doesn't seem to use bootloader command
Last modified: 2007-11-30 17:11:21 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20050922 Fedora/1.0.7-1.1.fc4 Firefox/1.0.7
Description of problem:
When doing a kickstart install, the bootloader configuration screen is always shown, and the 'bootloader' command in the kickstart configuration file is being ignored.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. install FC5 test 2 using a ks.cfg with an entry for bootloader configuration, in my case:
bootloader --location=mbr --driveorder=hda --md5pass=encryptedpassword
Actual Results: The screen for configuring the bootloader appeared and the grub password was not set so it seems the bootloader command in ks.cfg was ignored
Expected Results: installation should have continued with the settings provided in the kickstart file without prompting 9as happened in FC4)
This is still a problem in FC5 test 3, despite the fact it is marked "fixed in
rawhide". Can we get an explanation why this bug is closed?
"bootloader --location=mbr" in a ks.cfg file for FC5t3, resulting in a system
that will not boot after install. tty5 show that grub is failing with:
"Error 16: Inconsistent filesystem structure"
Note that I have raid configured with my boot partition being RAID1. This worked
flawlessly in FC4 and the bootloader was written to the MBR. I can't quite
figure out if 1) grub is ignoring the "bootloader" command in the ks.cfg or 2)
the RAID1 on the boot partition is causing the problem.
I believe Jeremy fixed this in rawhide earlier this week.