Red Hat Bugzilla – Bug 743642
bootloader not installed on serial only machines
Last modified: 2011-10-24 19:54:03 EDT
Description of problem:
trying to install F16 Beta (interactive or kickstart), I get this at the end
┌──────────────────┤ Warning ├──────────────────┐
│ There was an error installing the bootloader. │
│ The system may not be bootable. │
│ ┌────┐ │
│ │ OK │ │
│ └────┘ │
and the system is indeed not bootable
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. install F16 Beta on a system that has no video hardware but does have a serial console
2. wait for install to finish
3. notice error
system not bootable
system bootable after installation, just like previous Fedora version were.
I see this on all of
(do not mind the names, they will only mean something to $custmer, TAM and DEE)
$customer can live with this bug in Fedora, but it MUST NOT be present in RHEL7 (RHEL6 works just fine on the machines)
Created attachment 526527 [details]
program.log from an affected machine
18:05:53,984 ERR program: Serial terminal not available on this platform.
might be what's the problem here.
ssh-ing into the machine;
[anaconda root@acpi4-12 grub2]# pwd
[anaconda root@acpi4-12 grub2]# ls
device.map grub.cfg grub.cfg.new grubenv
But I'm told that serial.mod is expected to be present.
I hit this with F16 beta as well. It's easy to reproduce when installing to a virtual machine with serial console. Booting the install cd in rescue mode enabled me to install the bootloader manually with:
grub2-mkconfig -o /boot/grub2/grub.cfg
I'm happy to provide whatever information is needed, or I can work with anybody who wants me to on setting up the libvirt configuration required to reproduce it.
(In reply to comment #3)
> grub2-mkconfig -o /boot/grub2/grub.cfg
> grub2-install /dev/sda
Urgh, that should have been grub2-install /dev/vda in my case.
*** This bug has been marked as a duplicate of bug 736993 ***