Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

AWS EC2 systems show wrong bootloader #1752

Closed
gdha opened this issue Mar 9, 2018 · 4 comments
Closed

AWS EC2 systems show wrong bootloader #1752

gdha opened this issue Mar 9, 2018 · 4 comments
Assignees
@gdha
Labels
fixed / solved / done minor bug An alternative or workaround exists
Milestone
ReaR v2.4

Comments

@gdha
Copy link
Member

gdha commented Mar 9, 2018

  • 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
ZRr=
`|f
\|f1
GRUB
Geom
Hard Disk
Read
 Error
EFI PART
Hah!IdontNeedEFI"s8<

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!
@gdha gdha added the minor bug An alternative or workaround exists label Mar 9, 2018
@gdha gdha self-assigned this Mar 9, 2018
@OliverO2
Copy link
Contributor

OliverO2 commented Mar 9, 2018

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
Copy link
Member Author

gdha commented Mar 9, 2018

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

@gdha gdha mentioned this issue Mar 12, 2018
Merged
gdha added a commit that referenced this issue Mar 13, 2018
@gdha
AWS EC2 systems show wrong bootloader
de63bcb 
additional check for Hah!IdontNeedEFI #1752
@gdha gdha added this to the ReaR v2.4 milestone Mar 13, 2018
@gdha gdha closed this as completed Mar 13, 2018
@jsmeix
Copy link
Member

jsmeix commented Apr 19, 2018

Via #1779
I enhanced #1754
so that now it also detects other non-EFI bootloaders
(in particular also GRUB2).

This was referenced Apr 19, 2018
Closed
Merged
jsmeix added a commit that referenced this issue Apr 20, 2018
@jsmeix
Merge pull request #1779 from jsmeix/detect_LUKS_encrypted_bootloader…
d6cf9f8 
…_issue1769

Skip LUKS encrypted disks when guessing bootloader
so that it could still detect (guess) the bootloader on other
non-LUKS-encrypted (i.e. unencrypted) disks and if nowhere
a bootloader could be guessed it fails in the same way as before
cf. #1769
and
enhanced the "Hah!IdontNeedEFI" case
cf. #1752
so that now it also detects other non-EFI bootloaders
and
avoid 'cp' error exit in case of an improper RESULT_FILES member
cf. #1711 starting
at #1711 (comment)
@jsmeix jsmeix mentioned this issue Apr 23, 2018
Merged
@jsmeix
Copy link
Member

jsmeix commented Apr 24, 2018 •
edited

With #1780 merged
this issue should be (hopefully) fully fixed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@gdha gdha

Labels
fixed / solved / done minor bug An alternative or workaround exists
Projects
None yet
Milestone
ReaR v2.4
Development

No branches or pull requests
3 participants
@gdha @jsmeix @OliverO2