-
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
AWS EC2 Xen based Amazon Linux 2 : ReaR won't consider BIOS boot partition (/dev/xvda128 was not created by kernel < 5.14) #3093
Comments
I have neither a AWS EC2 system nor do I use Amazon Linux 2 To have at least a chance to imagine |
In contrast to this issue here |
@jsmeix Yes, you are correct, nvme** based VM's are fine but with XVDA it is not. Debug Log:
Conf File:
|
@ramzcode In general: |
@jsmeix Sorry for the confusion, my bad mistook the question. Attached the full log file for your reference. I just want to highlight my finding that the /dev/xvda128 don't even exist as well. and i don't see it under the dmesg log as well. |
Hi @ramzcode what problem do you actually encounter? Is it the rescue image not booting? Failing to recover? Recovering but then not being able to boot the recovered system? Please specify. What does it mean that "ReaR ignores or fails to record the Boot or Partition that is not listed under lsblk but available under fdisk or cfdisk" ? How does the problem manifest? Please also attach the file |
@pcahyna Hi, I have included my query in the first block of this thread. Backup and Recovery via RAW based disk image boots, but while setting up the disk layout and installing the boot loader on target VM ReaR complains that no BIOS type partitions found. This is because from the source the Disk Layout builder of ReaR failed to identify the BIOS boot Partition i.e. /dev/xvda128. Now the prob is recovery works but it won't boot due to improper partition structure on the target. NOTE: If you notice LSBLK will not list the 128 Partition that is boot type. and ReaR relies on lsblk for building Disk layout as of my understanding. |
My understanding is that ReaR uses parted, not lsblk. Please provide the output of It is indeed weird that lsblk does not show |
As far as I see in
so '/sys/block/xvda' is the only one in '/sys/block/*' From my current point of view it is From my current point of view in such cases it means See in particular the section "Inappropriate expectations" in |
@ramzcode By the way: |
If that's the reason, ReaR would not find |
Yes /dev/xvda1 is the root XFS filesystem, and it is recorded.
|
Please also attach the file /var/lib/rear/layout/disklayout.conf |
@pcahyna Partitions are not like /sys/block/sda1 but /sys/block/sda/sda1 |
I confused myself with disks and partitions in /sys/block/ Actually it is here that
which is the only found partition in /sys/block/ 'xvda128' does not appear in |
@jsmeix Yes, the underlying problem was due to the driver it seems, |
@ramzcode
In particular
is interesting for me because it answers my question in |
For the record, here https://wiki.archlinux.org/title/GRUB#GUID_Partition_Table_(GPT)_specific_instructions I see:
(emphasis mine). |
ReaR version ("/usr/sbin/rear -V"):
2.7
OS version ("cat /etc/os-release" or "lsb_release -a" or "cat /etc/rear/os.conf"):
Amazon Linux 2
ReaR configuration files ("cat /etc/rear/site.conf" and/or "cat /etc/rear/local.conf"):
Hardware vendor/product (PC or PowerNV BareMetal or ARM) or VM (KVM guest or PowerVM LPAR):
AWS
System architecture (x86 compatible or PPC64/PPC64LE or what exact ARM device):
x86
Firmware (BIOS or UEFI or Open Firmware) and bootloader (GRUB or ELILO or Petitboot):
BIOS
Storage (local disk or SSD) and/or SAN (FC or iSCSI or FCoE) and/or multipath (DM or NVMe):
NVMe Local Drives
Storage layout ("lsblk -ipo NAME,KNAME,PKNAME,TRAN,TYPE,FSTYPE,LABEL,SIZE,MOUNTPOINT"):
Partition table entries are not in disk order.
ReaR ignores or fails to record the Boot or Partition that is not listed under lsblk but available under fdisk or cfdisk
Still not available
The text was updated successfully, but these errors were encountered: