I had opt in the complete disk encryption when I was installing Ubuntu 18.04 and my password is not being accepted when I boot my system. However, I can access the encrypted drive and open it (using cryptsetup luksOpen) when I boot with Ubuntu stick. My questions are:

1. How can fully remove the encryption on that drive so that next time that I boot my system it goes directly to the OS that I had installed previously?

2. Are there any risk of loosing my data if I perform 1? If this is the case, how can make a backup of the encrypted drive so that I can recover it later.

Thanks

What error messages are you getting when it doesn't accept it? Have you asked this question on the Ubuntu forums? This sounds like it could be an XY problem. The link in my signature explains the XY problem.

1. You don't. You backup, reformat, and restore.

2. As much risk as there is in losing your dump files. Make a backup of them. You have to dump the filesystems, repartition the disk, format the partitions/LVM volumes, restore the dumps, update your boot loader config, and update /etc/fstab.

This will help you with the backup and restore part: https://tylersguides.com/guides/how-...t4-filesystem/ - Just do a full dump and full restore.

Any backup is better than no backup, but dump-restore ?. Phew .. haven't seen anyone suggesting that in a long time.
For a one-off full filesystem event like this I prefer something like fsarchiver - that gives you a checksummed backup for a bit more "comfort factor".

I have used dump and restore quite a bit in a production environment for similar scenarios. I had to move a bunch of VMs to their own hardware due to some initial confusion about licensing. In another situation I used them to move an old system to new hardware. Dump and restore are always in the repos, can read and write using stdin and stdout, and are easy to use when all you are doing is full dump and restore. You could always use your package manager to checksum the bulk of your files and manually checksum any data files.

Well, your question should be, why is that happening. And I think the reason is due to some keyboard setup. Clearly you know the password and it works, it just doesn't work on boot (due to keyboard setting?).

Do you have any data there aside from system data?

1 members found this post helpful.