-
Notifications
You must be signed in to change notification settings - Fork 246
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
REAR image does not boot in UEFI ( only on physical machine ). Used latest rear 2.6 version #2585
Comments
Hello. There were some changes in the UEFI bootloader support, can you please try a version without those changes? You can try the rear-2.4 package included in CentOS, because it does not have the changes in question. By the way, does "only on physical machine" mean that on a virtual machine it is working properly? |
Yes it is working fine in virtual machine. Ok let me try with rear-2.4 |
Note that you will need the grub2-efi-x64-modules package, I believe it is not installed by default. |
@pcahyna : Thanks for your update. I haven't install this package. let me install it and verify once again. |
ReaR from CentOS should warn you that you need this package if you don't have it. |
Thanks @pcahyna. Its working fine with rear2.4. Looks I can't use rear-2.6. |
@cvijayvinoth if you press any key to continue when GRUB stops, do you get to the GRUB command line? If so, can you please try |
@cvijayvinoth |
@jsmeix : yes I have been used 2.6 version from git only. |
@jsmeix thanks, indeed GitHub master should fix the issue.
manually in the GRUB command line. |
sure let me try once @pcahyna. I have used edit option on the menu ( pressed e ) and updated (cd0) before the /isolinux. It didn't work. Let me check with GRUB command line manually and update. |
My bad, I have not realized that the latest Git version identifies itself as "Relax-and-Recover 2.6 / Git", not as 2.7. |
Could you please share the link location for 2.7 version? Let me try with that too once. |
2.7 has not been released yet, if you use master branch from Github, you get what will eventually become 2.7 when released. Is that what you have been using? |
yes... I am using the master branch only. |
Can you please try several other things? |
sure @pcahyna. Now the restore is going on with rear 2.4 version. Let me verify post completing the current restore process. |
Yes you are correct @pcahyna . After reverting the code it is working fine. Its booting now. |
You mean rear from Git master, not the 2.6 release, right? Anyway,
That's very interesting. I did not expect this. I guess that it finds the EFI partition on the hard disk, instead of the EFI files on the CD. |
so revision 2be7f8b never worked after all? That's strange because 2be7f8b is before my changes that I suspect were causing the problem. c9e61ba is after. So my changes seem to have improved it, if I understand correctly. Now the question is, why 2.4 works, even if it is way older, and current Git version does not, even though it contains my change. |
yes, rear from Git master only. |
Tried with revision 2be7f8b couple of times. It never worked. Even I am trying to understand the changes in rear 2.6 code base and 2.4 version. |
Found one more issue on https://github.com/rear/rear/blob/master/usr/share/rear/output/ISO/Linux-i386/250_populate_efibootimg.sh
grubdir For me output is:
Actually /boot/grub2 should be assigned for grubdir. |
Good catch, the code does not take into account the possibility of having both |
Hello @cvijayvinoth , do you have any updates? |
@pcahyna : sorry missed to update you. Lost the access for that device. Let me try to reproduce it on my local machine and update you on this. |
Stale issue message |
Relax-and-Recover (ReaR) Issue Template
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.6 / Git
OS version ("cat /etc/os-release" or "lsb_release -a" or "cat /etc/rear/os.conf"):
NAME="CentOS Linux"
VERSION="7 (Core)"
ID="centos"
ID_LIKE="rhel fedora"
VERSION_ID="7"
PRETTY_NAME="CentOS Linux 7 (Core)"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:centos:centos:7"
HOME_URL="https://www.centos.org/"
BUG_REPORT_URL="https://bugs.centos.org/"
CENTOS_MANTISBT_PROJECT="CentOS-7"
CENTOS_MANTISBT_PROJECT_VERSION="7"
REDHAT_SUPPORT_PRODUCT="centos"
REDHAT_SUPPORT_PRODUCT_VERSION="7"
ReaR configuration files ("cat /etc/rear/site.conf" and/or "cat /etc/rear/local.conf"):
OUTPUT=ISO
BACKUP=RSYNC
RSYNC_PREFIX="yuvaraj1_${HOSTNAME}"
BACKUP_PROG="/var/www/html/imageBackup/rsync"
OUTPUT_URL=rsync://yuvaraj1@192.168.1.123::rsync_backup
BACKUP_URL=rsync://yuvaraj1@192.168.1.123::rsync_backup
ISO_DIR="/var/www/html/imageBackup/iso/$HOSTNAME"
MESSAGE_PREFIX="$$: "
PROGRESS_MODE="plain"
AUTOEXCLUDE_PATH=( /tmp )
PROGRESS_WAIT_SECONDS="1"
export TMPDIR="/var/www/html/imageBackup/iso/"
PXE_RECOVER_MODE=automatic
ISO_FILES=("/var/www/html/imageBackup/rsync")
ISO_PREFIX="${HOSTNAME}"
Hardware (PC or PowerNV BareMetal or ARM) or virtual machine (KVM guest or PoverVM LPAR): PC
System architecture (x86 compatible or PPC64/PPC64LE or what exact ARM device): x86 compatible
Firmware (BIOS or UEFI or Open Firmware) and bootloader (GRUB or ELILO or Petitboot): UEFI and GRUB
Storage (local disk or SSD) and/or SAN (FC or iSCSI or FCoE) and/or multipath
(DM or NVMe): local disk
Storage layout ("lsblk -ipo NAME,KNAME,PKNAME,TRAN,TYPE,FSTYPE,SIZE,MOUNTPOINT" or "lsblk" as makeshift):
Description of the issue (ideally so that others can reproduce it):
NAME KNAME PKNAME TRAN TYPE FSTYPE SIZE MOUNTPOINT
/dev/sda /dev/sda ata disk 298.1G
|-/dev/sda1 /dev/sda1 /dev/sda part vfat 200M /boot/efi
|-/dev/sda2 /dev/sda2 /dev/sda part xfs 1G /boot
-/dev/sda3 /dev/sda3 /dev/sda part LVM2_member 296.9G |-/dev/mapper/centos-root /dev/dm-0 /dev/sda3 lvm xfs 50G / |-/dev/mapper/centos-swap /dev/dm-1 /dev/sda3 lvm swap 7.8G [SWAP]
-/dev/mapper/centos-home /dev/dm-2 /dev/sda3 lvm xfs 239.1G /home/dev/sdb /dev/sdb ata disk 465.8G
|-/dev/sdb1 /dev/sdb1 /dev/sdb part ext4 238.4G
`-/dev/sdb2 /dev/sdb2 /dev/sdb part ext4 227.4G
Workaround, if any:
error: file `/isolinux/kernel' not found.
Loading initial ramdisk ...
error: you need to load the kernel first.
Press any key to continue...
Attachments, as applicable ("rear -D mkrescue/mkbackup/recover" debug log files): mkbackup
rear-centos-7.log
To paste verbatim text like command output or file content,
include it between a leading and a closing line of three backticks like
The text was updated successfully, but these errors were encountered: