#1752 Issue closed: AWS EC2 systems show wrong bootloader

Labels: fixed / solved / done, minor bug

gdha opened issue at 2018-03-09 14:20:

  • rear version (/usr/sbin/rear -V): 2.0 and higher
  • OS version (cat /etc/rear/os.conf or lsb_release -a): RHEL 7.4
  • rear configuration files (cat /etc/rear/site.conf or cat /etc/rear/local.conf): n/a
  • Are you using legacy BIOS or UEFI boot? BIOS
  • Brief description of the issue: rear -D -d savelayout
    It tells us Using guessed bootloader 'EFI', but AWS EC2 is using GRUB as bootloader. The funny thing is the following:
#-> cat /tmp/rear.V9AKAEZDKjqVbWE/tmp/bootloader_area_strings
Hard Disk

The AWS engineer who wrote this thinks this is funny...lol (notice IdontNeedEFI)

  • Work-around, if any:
    Is not such a big deal as we cannot use rear to recover an AWS EC2 anyhow -> no console available. But, if it is possible I would like to hear a success story!

OliverO2 commented at 2018-03-09 14:26:

The AWS engineer who wrote this thinks this is funny...lol (notice IdontNeedEFI)

Actually, "Hah!IdontNeedEFI" is the text representation of the official GUID number for a GPT BIOS boot partition: https://en.wikipedia.org/wiki/BIOS_boot_partition

gdha commented at 2018-03-09 14:45:

@OliverO2 Never too old to learn! Thanks for the clarification

jsmeix commented at 2018-04-19 13:44:

Via https://github.com/rear/rear/pull/1779
I enhanced https://github.com/rear/rear/pull/1754
so that now it also detects other non-EFI bootloaders
(in particular also GRUB2).

jsmeix commented at 2018-04-24 14:15:

With https://github.com/rear/rear/pull/1780 merged
this issue should be (hopefully) fully fixed.

[Export of Github issue for rear/rear.]