-
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
UEFI ISOLINUX boot failed with "Failed to load ldlinux.c32" on Ubuntu 18.04 #2471
Comments
In general regarding system migration with ReaR In general migrating a system onto different hardware In sufficiently simple cases it may "just work" but in general In general ReaR is first and foremost meant to recreate Additionally ReaR supports to migrate a system See also |
Why does the message mention ISOLINUX if it is on UEFI? I thought that in case of UEFI, ReaR uses GRUB2, not ISOLINUX. And it does not even seem to run under UEFI, because in that case it should mention |
@pcahyna I am always confused which bootloader is used in which circumstances. For details what exactly happens during "rear -D mkrescue" see Here an excerpt from
|
I am not at all an expert in the ReaR recovery system bootloader area
|
It seems some cleanup bug fixing is needed |
Could the root cause be that the ISO was created on an UEFI system and booted on a BIOS system? In that case, success is not expected, but the behavior seems a bit strange. |
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"): 2.6
OS version ("cat /etc/os-release" or "lsb_release -a" or "cat /etc/rear/os.conf"):
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):
Workaround, if any:
Attachments, as applicable ("rear -D mkrescue/mkbackup/recover" debug log files):
Failed to load ldlinux c32 when i tried to load rescue (iso) image in my vm.
I am using rsync to backup. I have done a backedup from my physical machine.
I tried to restore it in my VM. But is was throwing error like
Please help me on this.
rear-harish.log
The text was updated successfully, but these errors were encountered: