Ask Your Question
0

Anaconda failed to set new efi boot target [F19] and grub2-efi issues

asked 2013-07-10 09:17:17 -0600

Jorge_R gravatar image

updated 2013-07-26 19:28:02 -0600

Hi, I've tried to install F19 on my Lenovo S205 without success. I deleted all my old partitions to set a gpt partition system instead of the old mbr. I can set up all requirements to install but when the post-install process starts anaconda fails with the error shown in the title.

All partitions are configured automatically so it's very strange to me. My BIOS is a Phoenix Securecore Tiano with firmware version 4bcn21ww.

Edit: The output of efibootmgr is:

BootCurrent: 0004
Timeout: 0 seconds
BootOrder: 0007,0002,0003,0004,0005,0006
Boot0000  Setup
Boot0001  Boot Menu
Boot0002* USB FDD
Boot0003* ATA HDD0: ST9500325AS
Boot0004* USB HDD: Kingston DT 101 G2
Boot0005* USB CD:
Boot0006* PCI LAN: Realtek PXE B02 D00
Boot0007* Fedora

When I restart the system I get the grub command-shell mode and don't know how to proceed from there.

Edit 2: I found how to go further of grub's command-shell. I used the following commands

set root=(hd0,gpt4)
linuxefi (hd0,gpt2)/vmlinuz-3.9.9(etc) root=/dev/sda4 rhgb quiet syslinux=0
initrdefi (hd0,gpt2)/initramfs-3.9.9(etc)
boot

and the system starts pretty well, but I can't access as root on login (lxde version). I've changed /etc/{passwd,shadow} files so with Ctrl+Alt+F2 I can login as root, but still can't at lxde's login screen.

I tried to generate grub.cgf, there wasn't one, with grub2-mkconfig -o /boot/grub2/grub.cfg and installed with grub2-install /dev/sda but after a reboot I get a grub command-shell again.

Am I doing something wrong?

edit retag flag offensive close merge delete

3 Answers

Sort by ยป oldest newest most voted
0

answered 2013-07-10 15:38:02 -0600

newbeelike gravatar image

Hi, trying to install F19 yesterday on an Asus Eee PC 1215B I run into the same problem.

The Eee PC ran with F16 previously, so I booted with grml, deleted all partitions and wrote a fresh gpt to the disc. Afterwards I tried to install F19 several times, always ending up in the described error (while anaconda was trying to install the boot manager). Finally I booted with the F19 KDE live system, installed the kde-partitionmanager and re-wrote the gpt with it.

This solved the problem for me and F19 installed now smoothly. It looks like there was an issue with my "gpt", causing anaconda to crash.

edit flag offensive delete link more

Comments

Thanks for the response. Following your idea I installed gparted on the Gnome live-usb and re-wrote the partition system but the instalation failed again.

Jorge_R gravatar imageJorge_R ( 2013-07-10 21:24:14 -0600 )edit
0

answered 2014-05-15 16:04:47 -0600

I lost 3 days trying to figure out how to make Red Hat 6.5 boot properly after installation. Apparently this is an issue related to Lenovo BIOS in many motherboards. Here goes how i solved it:

- Boot to any Live media and then mount the boot partition;

- Inside this partition there is one only folder, named [EFI]. Inside [EFI] folder, a subfolder named [REDHAT], containing the files [grub.conf] and [grub.efi]. Probably in Fedora this subfolder is named [FEDORA];

- On [EFI] folder you should duplicate the subfolder, whatever it is, and then rename this copy as [BOOT];
Now, inside the newly renamed [BOOT] folder you should rename the files to [Bootx64.conf] and [Bootx64.efi];

- Unmount the partition and try to boot to your system now.
edit flag offensive delete link more
0

answered 2013-07-10 13:10:11 -0600

faustus gravatar image

Have you tried using efibootmgr to manually add the new boot entry? If you are running anaconda from the Live DVD, after the installation completes (with your error), you should still be able to open a shell and tweak your system. Running efibootmgr as root, without arguments, should show you your current boot settings. You can, of course, also add a new entry, change the default, etc. I refer you to the manual page for further details. If nothing else, assuming it also fails, it may provide a more detailed error message as to what went wrong.

edit flag offensive delete link more

Comments

Thanks for the help. On the error window there are three options: report bug, debug and quit. I reported the bug to bugzilla, debug is not an option for me because is a pretty strange error and quit exits anaconda. I can't enter the new system so I suppose that 'efibootmgr' must be executed from the live system, I'm right?

Jorge_R gravatar imageJorge_R ( 2013-07-10 21:27:51 -0600 )edit

Yes, you can execute it from the live system, either immediately after you run the installer, or, since you probably have already shut down your computer since then, you can boot to the Live desktop and run efibootmgr after the fact. Be sure to boot in EFI mode, though. You don't need to be booted into the installed system itself, since efibootmgr actually writes to the motherboard's NVRAM, not to your disks. This all assumes that Anaconda correctly formatted and populated your /boot/efi partition. You will need to pass the device node of your installed system to efibootmgr.

faustus gravatar imagefaustus ( 2013-07-12 21:37:10 -0600 )edit

Question Tools

2 followers

Stats

Asked: 2013-07-10 09:17:17 -0600

Seen: 3,098 times

Last updated: May 15 '14