Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

Removed /boot and /boot/efi

Hello,

yesterday I upgraded from Fedora 19 to 20beta by fedup --network 20.

The update ran through, took about 2 hours and it upgraded about 3000 packages. So far so good, but the GRUB2-entry of Heisenbug told me that a magic value was wrong after the reboot.

So I booted a previous entry and tried to upgrade grub2-efi with yum upgrade grub2-efi. It said there is a new version, but the installation was not successful. I remounted /boot and /boot/efi as read/writeable and tried again. This time there was another error: "Disk space too low (required 6MB)"

When I installed F19 this year I accepted the values from the installer: /dev/sda1:/boot=200M, /dev/sda2:/boot/efi=500M. I thought this should be enough, but apparently the EFI-partition needs more space. So I used fdisk too delete both partitions and created two new: /dev/sda1 with 150M and /dev/sda2 with 550M. This should be enough to hold the new grub2-efi version. Or so I thought.

I knew that I had to reinstall grub2 because I removed the partition. So I rebooted, started from Fedora 20-DVD but the rescue-environment couldn't automatically fix grub2.

Now comes my question: How do I reinstall GRUB2 and EFI, so that I can boot again?

# fdisk -l
Device       Start         End    Size    Type
/dev/sda1       34                150M    BIOS boot partition
/dev/sda2              1435647    550M    EFI System
/dev/sda3                         565G    Linux LVM (/, /home)
/dev/sda4                         9.8G    Linux LVM (swap)

My tries so far:

# mount -o bind /dev /mnt/sysimage/dev
# chroot /mnt/sysimage
# grub2-install /dev/sda

This gives me many of the same messages:

...
/run/lvm/lvmetad.socket: connect failed: No such file or directory
...
WARNING: Failed to connect to lvmetad: No such file or directory. Falling back to internal scanning
...
Installation finished. No error reported.

When I reboot, grub starts, but has no entries and only gives me the console.

Removed /boot and /boot/efi

Hello,

yesterday I upgraded from Fedora 19 to 20beta by fedup --network 20.

The update ran through, took about 2 hours and it upgraded about 3000 packages. So far so good, but the GRUB2-entry of Heisenbug told me that a magic value was wrong after the reboot.

So I booted a previous entry and tried to upgrade grub2-efi with yum upgrade grub2-efi. It said there is a new version, but the installation was not successful. I remounted /boot and /boot/efi as read/writeable and tried again. This time there was another error: "Disk space too low (required 6MB)"

When I installed F19 this year I accepted the values from the installer: /dev/sda1:/boot=200M, /dev/sda2:/boot/efi=500M. I thought this should be enough, but apparently the EFI-partition needs more space. So I used fdisk too delete both partitions and created two new: /dev/sda1 with 150M and /dev/sda2 with 550M. This should be enough to hold the new grub2-efi version. Or so I thought.

I knew that I had to reinstall grub2 because I removed the partition. So I rebooted, started from Fedora 20-DVD but the rescue-environment couldn't automatically fix grub2.

Now comes my question: How do I reinstall GRUB2 and EFI, I tried to install Fedora 20 from disk - a fresh install to say. I have 120GB unallocated disk space where I located fedora-boot. /home is the same /home as before and the both boot partitions are created automatically. The installation stopped two times with a yum error "no more mirrors to try". It was not connected to the internet, so that I can boot again?I don't know why it even tries any mirrors but at least both partitions are created.

I rebooted into rescue-enviroment and executed the following commands.

# fdisk -l
Device       Start         End    Size    Type
mount /dev/fedora_pcname/root /mnt/sysimage
# mount /dev/sda2 /mnt/sysimage/boot
# mount /dev/sda1       34                150M    BIOS boot partition
/dev/sda2              1435647    550M    EFI System
/dev/sda3                         565G    Linux LVM (/, /home)
/dev/sda4                         9.8G    Linux LVM (swap)

My tries so far:

/mnt/sysimage/boot/efi
# mount -o bind /proc /mnt/sysimage/proc
# mount -o bind /sys /mnt/sysimage/sys
# mount -o bind /dev /mnt/sysimage/dev
# mount -o bind /run/lvm /mnt/sysimage/run/lvm
# chroot /mnt/sysimage

I removed the newest kernel with "rpm -e --nodeps kernel-3.11.80-300..." and reinstalled it with "yum install kernel" and installed grub2 on /dev/sda

# grub2-install /dev/sda

This gives me many of the same messages:

...
/run/lvm/lvmetad.socket: connect failed: No such file or directory
...
WARNING: Failed to connect to lvmetad: No such file or directory. Falling back to internal scanning
...
BootCurrent: 0000
Timeout: 0 seconds
BootOrder: 2001
Boot0000* UEFI DVD1 PATH1 (...)
Boot0001* UEFI Onboard LAN IPv4
Boot0002* UEFI Onboard LAN IPv6
Boot2001* EFI USB Device
BootCurrent: 0000
Timeout: 0 seconds
BootOrder 0003,2001
Boot0000* UEFI DVD1 PATH1 (...)
Boot0001* UEFI Onboard LAN IPv4
Boot0002* UEFI Onboard LAN IPv6
Boot2001* EFI USB Device
Boot0003* fedora
Installation finished. No error reported.

When I reboot, grub starts, but This sounded good, so I tried grub2-mkconfig

# grub2-mkconfig -o /boot/grub2/grub.cfg
Generating grub.cfg ...
Found linux image: /boot/vmlinuz-3.11.8-300.fc20.x86_64
Found initrd image: /boot/initramfs-3.11.8-300.fc20.x86_64.img
Found linux image: /boot/vmlinuz-0-rescue-0f18bb71b2d6400eb098ed7ca633f657
Found initrd image: /boot/initramfs-0-rescue-0f18bb71b2d6400eb098ed7ca633f657.img
done

More information:

# efibootmgr -v
BootCurrent: 0000
Timeout: 0 seconds
BootOrder: 0003,2001
Boot0000* UEFI DVD1 PATH1 (...)
Boot0001* UEFI Onboard LAN IPv4
Boot0002* UEFI Onboard LAN IPv6
Boot0003* fedora HD(1,800,fa000,---long---hash---)FILE(\EFI\fedora\grubx64.efi)
Boot2001* EFI USB Device

But my BIOS does not show me the Fedora entry, nor can it boot from hard disk. I reckon that some ID or reference is still wrong because the partition layout has no entries and only gives me the console.been mixed and changed.

Removed /boot and /boot/efi

Hello,

yesterday I upgraded from Fedora 19 to 20beta by fedup --network 20.

The update ran through, took about 2 hours and it upgraded about 3000 packages. So far so good, but the GRUB2-entry of Heisenbug told me that a magic value was wrong after the reboot.

So I booted a previous entry and tried to upgrade grub2-efi with yum upgrade grub2-efi. It said there is a new version, but the installation was not successful. I remounted /boot and /boot/efi as read/writeable and tried again. This time there was another error: "Disk space too low (required 6MB)"

When I installed F19 this year I accepted the values from the installer: /dev/sda1:/boot=200M, /dev/sda2:/boot/efi=500M. I thought this should be enough, but apparently the EFI-partition needs more space. space (?). So I used fdisk too to delete both partitions and created two new: /dev/sda1 with 150M and /dev/sda2 with 550M. This should be enough to hold the new grub2-efi version. Or so I thought.

I knew that I had to reinstall grub2 because I removed the partition. partitions. So I rebooted, started from Fedora 20-DVD but the rescue-environment couldn't automatically fix grub2.

I tried to install Fedora 20 from disk - a fresh install to say. I have 120GB unallocated disk space where I located fedora-boot. fedora-root. /home is the same /home as before and the both boot partitions are created automatically. The installation stopped two times with a yum error "no more mirrors to try". It was not connected to the internet, so I don't know why it even tries any mirrors but at least both partitions are created.created. This time /boot was set to 200M on /dev/sda2 and /boot/efi was set to 500M on /dev/sda1 (switched from prior installation wizard).

I rebooted into rescue-enviroment (from installation DVD) and executed the following commands.

# mount /dev/fedora_pcname/root /mnt/sysimage
# mount /dev/sda2 /mnt/sysimage/boot
# mount /dev/sda1 /mnt/sysimage/boot/efi
# mount -o bind /proc /mnt/sysimage/proc
# mount -o bind /sys /mnt/sysimage/sys
# mount -o bind /dev /mnt/sysimage/dev
# mount -o bind /run/lvm /mnt/sysimage/run/lvm
# chroot /mnt/sysimage

I removed the newest kernel with "rpm -e --nodeps kernel-3.11.80-300..." kernel-3.11.8-300..." and reinstalled it with "yum install kernel" and installed grub2 on /dev/sda

# grub2-install /dev/sda
BootCurrent: 0000
Timeout: 0 seconds
BootOrder: 2001
Boot0000* UEFI DVD1 PATH1 (...)
Boot0001* UEFI Onboard LAN IPv4
Boot0002* UEFI Onboard LAN IPv6
Boot2001* EFI USB Device
BootCurrent: 0000
Timeout: 0 seconds
BootOrder 0003,2001
Boot0000* UEFI DVD1 PATH1 (...)
Boot0001* UEFI Onboard LAN IPv4
Boot0002* UEFI Onboard LAN IPv6
Boot2001* EFI USB Device
Boot0003* fedora
Installation finished. No error reported.

This sounded good, so I tried grub2-mkconfig

# grub2-mkconfig -o /boot/grub2/grub.cfg
Generating grub.cfg ...
Found linux image: /boot/vmlinuz-3.11.8-300.fc20.x86_64
Found initrd image: /boot/initramfs-3.11.8-300.fc20.x86_64.img
Found linux image: /boot/vmlinuz-0-rescue-0f18bb71b2d6400eb098ed7ca633f657
Found initrd image: /boot/initramfs-0-rescue-0f18bb71b2d6400eb098ed7ca633f657.img
done

More information:

# efibootmgr -v
BootCurrent: 0000
Timeout: 0 seconds
BootOrder: 0003,2001
Boot0000* UEFI DVD1 PATH1 (...)
Boot0001* UEFI Onboard LAN IPv4
Boot0002* UEFI Onboard LAN IPv6
Boot0003* fedora HD(1,800,fa000,---long---hash---)FILE(\EFI\fedora\grubx64.efi)
Boot2001* EFI USB Device

But my BIOS does not show me the Fedora entry, nor can it boot from hard disk. I reckon that some ID or reference is still wrong because the partition layout has been mixed and changed.

Removed /boot and /boot/efi

Hello,

yesterday I upgraded from Fedora 19 to 20beta by fedup --network 20.

The update ran through, took about 2 hours and it upgraded about 3000 packages. So far so good, but the GRUB2-entry of Heisenbug told me that a magic value was wrong after the reboot.

So I booted a previous entry and tried to upgrade grub2-efi with yum upgrade grub2-efi. It said there is a new version, but the installation was not successful. I remounted /boot and /boot/efi as read/writeable and tried again. This time there was another error: "Disk space too low (required 6MB)"

When I installed F19 this year I accepted the values from the installer: /dev/sda1:/boot=200M, /dev/sda2:/boot/efi=500M. I thought this should be enough, but apparently the EFI-partition needs more space (?). So I used fdisk to delete both partitions and created two new: /dev/sda1 with 150M and /dev/sda2 with 550M. This should be enough to hold the new grub2-efi version. Or so I thought.

I knew that I had to reinstall grub2 because I removed the partitions. So I rebooted, started from Fedora 20-DVD but the rescue-environment couldn't automatically fix grub2.

I tried to install Fedora 20 from disk - a fresh install to say. I have 120GB unallocated disk space where I located fedora-root. /home is the same /home as before and the both boot partitions are created automatically. The installation stopped two times with a yum error "no more mirrors to try". It was not connected to the internet, so I don't know why it even tries any mirrors but at least both partitions are created. This time /boot was set to 200M on /dev/sda2 and /boot/efi was set to 500M on /dev/sda1 (switched from prior installation wizard).

I rebooted into rescue-enviroment (from installation DVD) and executed the following commands.

# mount /dev/fedora_pcname/root /mnt/sysimage
# mount /dev/sda2 /mnt/sysimage/boot
# mount /dev/sda1 /mnt/sysimage/boot/efi
# mount -o bind /proc /mnt/sysimage/proc
# mount -o bind /sys /mnt/sysimage/sys
# mount -o bind /dev /mnt/sysimage/dev
# mount -o bind /run/lvm /mnt/sysimage/run/lvm
# chroot /mnt/sysimage

I removed the newest kernel with "rpm -e --nodeps kernel-3.11.8-300..." and reinstalled it with "yum install kernel" and installed grub2 on /dev/sda

# grub2-install /dev/sda
BootCurrent: 0000
Timeout: 0 seconds
BootOrder: 2001
Boot0000* UEFI DVD1 PATH1 (...)
Boot0001* UEFI Onboard LAN IPv4
Boot0002* UEFI Onboard LAN IPv6
Boot2001* EFI USB Device
BootCurrent: 0000
Timeout: 0 seconds
BootOrder 0003,2001
Boot0000* UEFI DVD1 PATH1 (...)
Boot0001* UEFI Onboard LAN IPv4
Boot0002* UEFI Onboard LAN IPv6
Boot2001* EFI USB Device
Boot0003* fedora
Installation finished. No error reported.

This sounded good, so I tried grub2-mkconfig

# grub2-mkconfig -o /boot/grub2/grub.cfg
Generating grub.cfg ...
Found linux image: /boot/vmlinuz-3.11.8-300.fc20.x86_64
Found initrd image: /boot/initramfs-3.11.8-300.fc20.x86_64.img
Found linux image: /boot/vmlinuz-0-rescue-0f18bb71b2d6400eb098ed7ca633f657
Found initrd image: /boot/initramfs-0-rescue-0f18bb71b2d6400eb098ed7ca633f657.img
done

More information:

# efibootmgr -v
BootCurrent: 0000
Timeout: 0 seconds
BootOrder: 0003,2001
Boot0000* UEFI DVD1 PATH1 (...)
Boot0001* UEFI Onboard LAN IPv4
Boot0002* UEFI Onboard LAN IPv6
Boot0003* fedora HD(1,800,fa000,---long---hash---)FILE(\EFI\fedora\grubx64.efi)
Boot2001* EFI USB Device

But my BIOS does not show me the Fedora entry, nor can it boot from hard disk. I reckon that some ID or reference is still wrong because the partition layout has been mixed and changed.

Edit:

I reinstalled grub2 grub2-efi and shim again and run "grub2-install /dev/sda" multiple times. Suddenly it worked. It was finally ready to boot. I had to remove AMD-drivers, SELinux, reconfigure X and edit /etc/fstab so that /boot and /boot/efi were mounted by the right partition (for me /dev/sda2 and /dev/sda1).

Finally gdm showed and I could log in.

Removed /boot and /boot/efi

Hello,

yesterday I upgraded from Fedora 19 to 20beta by fedup --network 20.

The update ran through, took about 2 hours and it upgraded about 3000 packages. So far so good, but the GRUB2-entry of Heisenbug told me that a magic value was wrong after the reboot.

So I booted a previous entry and tried to upgrade grub2-efi with yum upgrade grub2-efi. It said there is a new version, but the installation was not successful. I remounted /boot and /boot/efi as read/writeable and tried again. This time there was another error: "Disk space too low (required 6MB)"

When I installed F19 this year I accepted the values from the installer: /dev/sda1:/boot=200M, /dev/sda2:/boot/efi=500M. I thought this should be enough, but apparently the EFI-partition needs more space (?). So I used fdisk to delete both partitions and created two new: /dev/sda1 with 150M and /dev/sda2 with 550M. This should be enough to hold the new grub2-efi version. Or so I thought.

I knew that I had to reinstall grub2 because I removed the partitions. So I rebooted, started from Fedora 20-DVD but the rescue-environment couldn't automatically fix grub2.

I tried to install Fedora 20 from disk - a fresh install to say. I have 120GB unallocated disk space where I located fedora-root. /home is the same /home as before and the both boot partitions are created automatically. The installation stopped two times with a yum error "no more mirrors to try". It was not connected to the internet, so I don't know why it even tries any mirrors but at least both partitions are created. This time /boot was set to 200M on /dev/sda2 and /boot/efi was set to 500M on /dev/sda1 (switched from prior installation wizard).

I rebooted into rescue-enviroment (from installation DVD) and executed the following commands.

# mount /dev/fedora_pcname/root /mnt/sysimage
# mount /dev/sda2 /mnt/sysimage/boot
# mount /dev/sda1 /mnt/sysimage/boot/efi
# mount -o bind /proc /mnt/sysimage/proc
# mount -o bind /sys /mnt/sysimage/sys
# mount -o bind /dev /mnt/sysimage/dev
# mount -o bind /run/lvm /mnt/sysimage/run/lvm
# chroot /mnt/sysimage

I removed the newest kernel with "rpm -e --nodeps kernel-3.11.8-300..." and reinstalled it with "yum install kernel" and installed grub2 on /dev/sda

# grub2-install /dev/sda
BootCurrent: 0000
Timeout: 0 seconds
BootOrder: 2001
Boot0000* UEFI DVD1 PATH1 (...)
Boot0001* UEFI Onboard LAN IPv4
Boot0002* UEFI Onboard LAN IPv6
Boot2001* EFI USB Device
BootCurrent: 0000
Timeout: 0 seconds
BootOrder 0003,2001
Boot0000* UEFI DVD1 PATH1 (...)
Boot0001* UEFI Onboard LAN IPv4
Boot0002* UEFI Onboard LAN IPv6
Boot2001* EFI USB Device
Boot0003* fedora
Installation finished. No error reported.

This sounded good, so I tried grub2-mkconfig

# grub2-mkconfig -o /boot/grub2/grub.cfg
Generating grub.cfg ...
Found linux image: /boot/vmlinuz-3.11.8-300.fc20.x86_64
Found initrd image: /boot/initramfs-3.11.8-300.fc20.x86_64.img
Found linux image: /boot/vmlinuz-0-rescue-0f18bb71b2d6400eb098ed7ca633f657
Found initrd image: /boot/initramfs-0-rescue-0f18bb71b2d6400eb098ed7ca633f657.img
done

More information:

# efibootmgr -v
BootCurrent: 0000
Timeout: 0 seconds
BootOrder: 0003,2001
Boot0000* UEFI DVD1 PATH1 (...)
Boot0001* UEFI Onboard LAN IPv4
Boot0002* UEFI Onboard LAN IPv6
Boot0003* fedora HD(1,800,fa000,---long---hash---)FILE(\EFI\fedora\grubx64.efi)
Boot2001* EFI USB Device

But my BIOS does not show me the Fedora entry, nor can it boot from hard disk. I reckon that some ID or reference is still wrong because the partition layout has been mixed and changed.

Edit:

I reinstalled grub2 grub2-efi and shim again and run "grub2-install /dev/sda" multiple times. Suddenly it worked. times and configured EFI step by step with the guide for FedUp.

It was finally ready to boot. I had to remove AMD-drivers, SELinux, reconfigure X and edit /etc/fstab so that /boot and /boot/efi were mounted by the right partition (for me /dev/sda2 and /dev/sda1).

Finally gdm showed and /dev/sda1) and then I could finally log in.

Removed /boot and /boot/efi

Hello,

yesterday I upgraded from Fedora 19 to 20beta by fedup --network 20.

The update ran through, took about 2 hours and it upgraded about 3000 packages. So far so good, but the GRUB2-entry of Heisenbug told me that a magic value was wrong after the reboot.

So I booted a previous entry and tried to upgrade grub2-efi with yum upgrade grub2-efi. It said there is a new version, but the installation was not successful. I remounted /boot and /boot/efi as read/writeable and tried again. This time there was another error: "Disk space too low (required 6MB)"

When I installed F19 this year I accepted the values from the installer: /dev/sda1:/boot=200M, /dev/sda2:/boot/efi=500M. I thought this should be enough, but apparently the EFI-partition needs more space (?). So I used fdisk to delete both partitions and created two new: /dev/sda1 with 150M and /dev/sda2 with 550M. This should be enough to hold the new grub2-efi version. Or so I thought.

I knew that I had to reinstall grub2 because I removed the partitions. So I rebooted, started from Fedora 20-DVD but the rescue-environment couldn't automatically fix grub2.

I tried to install Fedora 20 from disk - a fresh install to say. I have 120GB unallocated disk space where I located fedora-root. /home is the same /home as before and the both boot partitions are created automatically. The installation stopped two times with a yum error "no more mirrors to try". It was not connected to the internet, so I don't know why it even tries any mirrors but at least both partitions are created. This time /boot was set to 200M on /dev/sda2 and /boot/efi was set to 500M on /dev/sda1 (switched from prior installation wizard).

I rebooted into rescue-enviroment (from installation DVD) and executed the following commands.

# mount /dev/fedora_pcname/root /mnt/sysimage
# mount /dev/sda2 /mnt/sysimage/boot
# mount /dev/sda1 /mnt/sysimage/boot/efi
# mount -o bind /proc /mnt/sysimage/proc
# mount -o bind /sys /mnt/sysimage/sys
# mount -o bind /dev /mnt/sysimage/dev
# mount -o bind /run/lvm /mnt/sysimage/run/lvm
# chroot /mnt/sysimage

I removed the newest kernel with "rpm -e --nodeps kernel-3.11.8-300..." and reinstalled it with "yum install kernel" and installed grub2 on /dev/sda

# grub2-install /dev/sda
BootCurrent: 0000
Timeout: 0 seconds
BootOrder: 2001
Boot0000* UEFI DVD1 PATH1 (...)
Boot0001* UEFI Onboard LAN IPv4
Boot0002* UEFI Onboard LAN IPv6
Boot2001* EFI USB Device
BootCurrent: 0000
Timeout: 0 seconds
BootOrder 0003,2001
Boot0000* UEFI DVD1 PATH1 (...)
Boot0001* UEFI Onboard LAN IPv4
Boot0002* UEFI Onboard LAN IPv6
Boot2001* EFI USB Device
Boot0003* fedora
Installation finished. No error reported.

This sounded good, so I tried grub2-mkconfig

# grub2-mkconfig -o /boot/grub2/grub.cfg
Generating grub.cfg ...
Found linux image: /boot/vmlinuz-3.11.8-300.fc20.x86_64
Found initrd image: /boot/initramfs-3.11.8-300.fc20.x86_64.img
Found linux image: /boot/vmlinuz-0-rescue-0f18bb71b2d6400eb098ed7ca633f657
Found initrd image: /boot/initramfs-0-rescue-0f18bb71b2d6400eb098ed7ca633f657.img
done

More information:

# efibootmgr -v
BootCurrent: 0000
Timeout: 0 seconds
BootOrder: 0003,2001
Boot0000* UEFI DVD1 PATH1 (...)
Boot0001* UEFI Onboard LAN IPv4
Boot0002* UEFI Onboard LAN IPv6
Boot0003* fedora HD(1,800,fa000,---long---hash---)FILE(\EFI\fedora\grubx64.efi)
Boot2001* EFI USB Device

But my BIOS does not show me the Fedora entry, nor can it boot from hard disk. I reckon that some ID or reference is still wrong because the partition layout has been mixed and changed.

Edit:

I reinstalled grub2 grub2-efi and shim again and run "grub2-install /dev/sda" multiple times and configured EFI step by step with the guide for FedUp.

It was finally ready to boot. I had to remove AMD-drivers, SELinux, reconfigure X and edit /etc/fstab so that /boot and /boot/efi were mounted by the right partition (for me /dev/sda2 and /dev/sda1) and then I could finally log in.