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
Not able to recover encypted OS #1444
Comments
Hi Team, Is it a bug or I am doing anything wrong configuration?. Below are few more test results:
|
Hi @metro1234, I doubt that this is your fault.
It looks that something went wrong during It would be interesting to see following files
Can you please provide these two files? Thanks V. |
Hi Gozora, /var/lib/rear/layout/disklayout.conf
/var/log/rear/rear-.log created during rear -d -D recover session is attached Thanks |
At first glance I don't see anything wrong neither in disklayout.conf nor in log file. V. |
I just successfully finished ReaR (2.2) restore of Centos 7.3, with setup similar to yours:
Your problem is rather simple to solve. V. |
Thanks @gozora for trying out that setup. What about Can it be that we need to improve the user guidance in ReaR so that it will show the user a short help text before running Maybe we should also actively handle the case that |
Hi @schlomo,
No problem, I was curious about how ReaR works with LUKS ...
I have no idea where this is coming from ... Maybe missing cracklib ? I really can't tell unless I have more information ...
Today it was first time in my life I've was configuring LUKS. I must say that neither configuring LUKS nor ReaR was "brain surgery or rocket science". So I'd conclude that if user have some basic understanding how LUKS works, he can handle such setups + basic troubleshooting.
You have this chance even now by running Like I already said, LUKS + ReaR works well enough for me. Only thing I would add is recovery of keys that were used on original system. @metro1234 if you still have trouble with restore, maybe you could share with me your recovery ISO so I can see what is wrong. V. |
Thinking of it, this is not such a good idea ... It would require to store original passphrases/keys somewhere very very safely, so NO Vladimir don't even think about it! :-) |
IMHO crypto disks are, by design, not meant for automated disaster recovery as long as the crypto secrets are entered by a human on the source system. ReaR cannot automate more than is already automated in the source system. That means that it could be automated if the entire crypto setup is automated on the source system, e.g. by retrieving the keys from a key server during booting (and yes, this is probably not a typical setup). If you all agree that ReaR doesn't require any improvement for this use case then please close the issue. |
I think the issue is sufficiently answered so that I close it. For the future we might use my new grandiose UserInput function This way it is the user who can predefine his LUKS passwords For example the user can predefine his LUKS passwords Alternatively - if the user really likes it - he could predefine |
@gozora , For some reasons I have not able to recover. I have used different password no luck and used difficult password no luck. How do i share files. Do you have any link? Thanks |
@metro1234 |
Hi, I have shared it. Could you please confirm you have received it. |
Got it.
You can remove it if checksum matches ... V, |
@metro1234 V. |
Yes Exactly |
@gozora , Just curious. How did you encrypt the file system? Did you encrypt during installation or Did you encrypt after OS Installation. Could you Please share steps you performed during encryption. I will try same setup here. I have tried cent OS,RHEL 7.2 for both version It will hung after passphrases password enter. |
I've let installer to setup and encrypt / and once installation was done, I've manually configured encryption for /data1, this however does not matter.
So your ReaR config should look something like:
After you run V. |
@gozora |
@metro1234 |
Hello @jsmeix, In this case it requires to have /var/tmp directory available at restore time (addressed by your #1457), and So with current ReaR 2.2, following needs to be added to _local.conf)
V. |
Relax-and-Recover (ReaR) Issue Template
Fill in the following items before submitting a new issue
(quick response is not guaranteed with free support):
BIOS
OS Is encrypted with luks.
I have tried to restore using below command
rear -v recover
Asked Passphrase of key (Encryption key) and entered correct password
and it failed for layout recreation
log file error:
The text was updated successfully, but these errors were encountered: