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.
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
Some disks need 'dd ... bs=4092' in guess_bootloader.sh and without grub2-efi-modules installed things go wrong on RHEL 7.3 with UEFI #1242
Comments
They looks similar but I couldn't find "BOOTX64.EFI" under /boot/efi. Would you please elaborate what you mean by "try latest snapshot version" |
@j100ng You can download it from http://download.opensuse.org/repositories/Archiving:/Backup:/Rear:/Snapshot/CentOS_7/x86_64/ |
I tried this snapshot version and still encounter the same error. Attached is the execution log. |
@j100ng Please have a look at script |
Here's the output of "dd if=/dev/sda bs=512 count=4 | strings" as called in /usr/share/rear/prep/default/50_guess_bootloader.sh . [jacksonl@macso1 sda]$ sudo dd if=/dev/sda bs=512 count=4 | strings So it does not show the bootloader type. [jacksonl@macso1 sda]$ sudo dd if=/dev/sda bs=4096 count=4 | strings So I created my own /var/lib/rear/recovery/bootloader to contain EFI. But now I got a different error |
Hello @j100ng, Could you please run Thanks V. |
@j100ng try to install |
Is this something new? |
"rear -v mkrescue" was successful after I installed grub2-efi-modules. Now trying to do a full backup & restore |
For me "new" is very relative. But this requirement is in ReaR for 8 months or so ... |
#1242 (comment) I wonder if there could be a reliably working automated test grub2-efi-modules needs to be installed @gozora |
Hello @jsmeix, I guess you just overlooked a fact that this issue is not longer about "unknown boot loader". See #1242 (comment). For the second problem, ReaR ended with error: "grub2-mkimage: error: cannot open `/usr/lib/grub/x86_64-efi/moddep.lst': No such file or directory", which is OK to my opinion. V. |
@gozora |
Please note that the original issue where /usr/share/rear/prep/default/50_guess_bootloader.sh does not find the bootloader info is still there. The root cause is the line
had failed. The disk drive on my system needs to use 4092 instead of 512. I initially used a workaround of manually creating the bootloader file. I just tried a different solution and seems to work |
@j100ng Regardless what kind of guesswork you use, I think I will implement support for a BOOTLOADER variable @j100ng |
Via #1262 |
@j100ng Setting BOOTLOADER is only meant so that the user What is currently listed in GRUB2-EFI EFI GRUB2 GRUB ELILO LILO PPC Currently there is no validation check for a BOOTLOADER @j100ng I would appreciate it if you coud test ReaR Many thanks in advance! |
I have tested the latest version of rear from git under the following 2 scenarios:
|
@j100ng According to |
Please fill in the following items before submitting a new issue (quick response is not guaranteed with free support):
rear version (/usr/sbin/rear -V):
Relax-and-Recover 2.00 / Git
OS version (cat /etc/rear/os.conf or lsb_release -a):
Are you using legacy BIOS or UEFI boot?
UEFI
Brief description of the issue:
I was previously using rear (v1.17.2) as installed via "yum install rear" on RHEL 7.3. It does not backup/restore capabilities. So I downloaded v2.00 and tried to run this version. It gives me this error. As I looked through the codes & logs, it complained because file, /var/lib/rear/recovery/bootloader, is missing.
I tried running "rear savelayout" and got the same error.
I rolled back to v1.18, and I can now run "rear -v mkbackup"
rear.zip
The text was updated successfully, but these errors were encountered: