-
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
Failed to create parition table with LVM and LUKS #2722
Comments
Yup, it is indeed LUKS2. I will see if I can use the dev version. Is there an ETA for LUKS2 support in the release? |
See the first part of https://github.com/rear/rear#quick-start-guide "how to run Relax-and-Recover from the git checkout". Note that the configuration file for running from git checkout is indeed |
The partition table was created. Unfortunately I did not include the necessary information about the restic backup that has the rest of the disk content and I cannot get to it from the rescue image, but that is not part of the issue I consider this issue closed. Thanks everyone |
@Quixus thank you for verifying the fix in the development version. |
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.5 / Git
OS version ("cat /etc/os-release" or "lsb_release -a" or "cat /etc/rear/os.conf"):
Ubuntu 20.04.3 LTS
ReaR configuration files ("cat /etc/rear/site.conf" and/or "cat /etc/rear/local.conf"):
Default configuration
Hardware vendor/product (PC or PowerNV BareMetal or ARM) or VM (KVM guest or PowerVM LPAR):
Source for mkrescue: x64 PC
Target of rear recover: VM in HyperV
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):
EFI and GRUB
Storage (local disk or SSD) and/or SAN (FC or iSCSI or FCoE) and/or multipath (DM or NVMe):
Source: Local Disk with LVM and LUKS
Storage layout ("lsblk -ipo NAME,KNAME,PKNAME,TRAN,TYPE,FSTYPE,SIZE,MOUNTPOINT"):
After creating the ISO and mounting it as boot device on the VM, the writing of the partitions fails at the step where the LUKS password should be entered.
Workaround, if any:
I haven't found one
Attachments, as applicable ("rear -D mkrescue/mkbackup/recover" debug log files):
Unfortunately I cannot get the log out of the VM.
The text was updated successfully, but these errors were encountered: