Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
.`ReaR` utility now restores system using `LUKS2` encrypted partition
Previously, when at least one `LUKS2` encrypted partition was present on the system to backup with Relax-and-Recover (`Rear`) utility, the user was not informed that ReaR does not support `LUKS2` encrypted partition. Consequently, the `ReaR` utility was unable to recreate the original state of the system during the restore phase.
With this update, support of basic `LUKS2` configuration, error checking, and improved output has been added to the `ReaR` utility. The `ReaR` utility now restores systems using basic `LUKS2` encrypted partitions or notifies users in the opposite case.
Rear is unable to properly backup LUKS2 volumes and currently does not complain that it did not do so correctly.
There is an upstream bug about this already.
https://github.com/rear/rear/issues/2204
Also there is a patch to report error to backup until the underlying issue is corrected.
https://github.com/rear/rear/pull/2381
From a quick look at the issue, it seems that ReaR backs up the data properly, and then fails to recreate the disk layout during restore, right? I.e. data are not lost and could be in principle restored in another way. (I am not trying to say that the issue does not matter, just trying to understand the impact and cause and possible workarounds.)
Comment 6Vitezslav Crhonek
2020-10-13 11:26:15 UTC
Improved version of patch from PR#2381 is available in PR#2493.
https://github.com/rear/rear/pull/2493
It doesn't report error when creating backup but just warns user that usage
of unsupported version of LUKS was detected. ReaR then adds commented out
"crypt" entry to disklayout.conf and finishes the backup as usual.
During the recover phase, user can edit disklayout.conf, uncomment "crypt"
entry and provide correct values there. I was able to successfully complete
the system recovery in this manner.
Comment 7Vitezslav Crhonek
2020-10-14 07:17:12 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (rear bug fix and enhancement update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2021:1910