Description of problem: I tried installing multiple times on different NVME drives LUKS Encrypted Fedora Workstation and I always get this same error message. Here's what I tried so far: - Wiping the drives beforehand with "wipefs -a" - Deleting and creating a new partition table with fdisk - BTRFS layout using "Custom" in the installer - BTRFS layout using "Custom Blivet-GUI" - EXT4 using "Custom Blivet-GUI" - Using Network installer instead of Fedora 35 Workstation ISO - Using different LUKS passwords - Disabling TPM and SGX in BIOS I made sure to use the following partition layout in my BTRFS attempts /boot ext4 1 GiB /boot/efi EFI Partition 512 Mib BTRFS partition layout with home, root, var layout (/home, /, /var) for the rest of the space Version-Release number of selected component: anaconda-35.22.2 The following was filed automatically by anaconda: anaconda 35.22.2 exception report Traceback (most recent call first): File "/usr/lib/python3.10/site-packages/dasbus/client/handler.py", line 497, in _handle_method_error raise exception from None File "/usr/lib/python3.10/site-packages/dasbus/client/handler.py", line 477, in _get_method_reply return self._handle_method_error(error) File "/usr/lib/python3.10/site-packages/dasbus/client/handler.py", line 444, in _call_method return self._get_method_reply( File "/usr/lib64/python3.10/site-packages/pyanaconda/modules/common/task/__init__.py", line 46, in sync_run_task task_proxy.Finish() File "/usr/lib64/python3.10/site-packages/pyanaconda/installation_tasks.py", line 527, in run_task sync_run_task(self._task_proxy) File "/usr/lib64/python3.10/site-packages/pyanaconda/installation_tasks.py", line 496, in start self.run_task() File "/usr/lib64/python3.10/site-packages/pyanaconda/installation_tasks.py", line 311, in start item.start() File "/usr/lib64/python3.10/site-packages/pyanaconda/installation_tasks.py", line 311, in start item.start() File "/usr/lib64/python3.10/site-packages/pyanaconda/installation_tasks.py", line 311, in start item.start() File "/usr/lib64/python3.10/site-packages/pyanaconda/installation.py", line 415, in run_installation queue.start() File "/usr/lib64/python3.10/threading.py", line 946, in run self._target(*self._args, **self._kwargs) File "/usr/lib64/python3.10/site-packages/pyanaconda/threading.py", line 275, in run threading.Thread.run(self) pyanaconda.modules.common.errors.installation.StorageInstallationError: Failed to activate device: Incorrect passphrase. Additional info: addons: com_redhat_kdump cmdline: /usr/bin/python3 /sbin/anaconda cmdline_file: BOOT_IMAGE=/images/pxeboot/vmlinuz inst.stage2=hd:LABEL=Fedora-S-dvd-x86_64-35 quiet executable: /sbin/anaconda hashmarkername: anaconda hawkey.log: 2022-01-15T01:40:57+0000 INFO === Started libdnf-0.64.0 === kernel: 5.14.10-300.fc35.x86_64 product: Fedora release: Fedora release 35 (Thirty Five) type: anaconda version: 35
Created attachment 1850881 [details] File: anaconda-tb
Created attachment 1850882 [details] File: anaconda.log
Created attachment 1850883 [details] File: dbus.log
Created attachment 1850884 [details] File: dnf.librepo.log
Created attachment 1850885 [details] File: environ
Created attachment 1850886 [details] File: lorax-packages.log
Created attachment 1850887 [details] File: lsblk_output
Created attachment 1850888 [details] File: nmcli_dev_list
Created attachment 1850889 [details] File: os_info
Created attachment 1850890 [details] File: program.log
Created attachment 1850891 [details] File: storage.log
Created attachment 1850892 [details] File: syslog
Created attachment 1850893 [details] File: packaging.log
Using Luks1 instead of Luks2 works
I encountered this bug installing Qubes OS (fedora based), and it was because the passphrase was too small (I used "1234" for speed and convenience during install steps/reboots). The GUI installer warns that the passphrase is too small, but does not prevent continuing the installation, which fails at luks creation with the error message you report. The difference is that the anaconda version used was older : 32.24.5-5.fc32 (you reported 35), maybe it was solved since, I don't know.
Hi @zithro, my LUKS passphrase was at 31 chracters in length. I think it's two seperate bugs.
Hi fredol, thank you for the precision. But is it worth it to open a new bug ? Or should I see with downstream first as it's using an older anaconda version ?
It seems to be an issue in Blivet-GUI. Reassigning.
Hi Vendula, it also happened on me with a long password, so ignore the "short password" thing from my previous post. I had the problem using the Blivet-GUI (this picture: https://fedoraproject.org/wiki/Blivet-gui), but in my case the error did ALSO happen by manual partitioning without Blivet (don't know how it's called sorry, I'm not well versed into Fedora installs). In fact, it even happens by manually partitioning via the command line (via cryptsetup). I don't know if it's relevant, but the install is done in a Xen domU, on an empty sparse-file-backed PV disk (xvda used in the config file).
Hey everyone, I did some memory tests with memtest86 and it seems that my issue with LUKS2 would be caused by faulty ram. Once I receive my new ram I will reinstall Fedora with LUKS2 and tell you if I can still reproduce this bug.
This message is a reminder that Fedora Linux 35 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 35 on 2022-12-13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '35'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 35 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 35 entered end-of-life (EOL) status on 2022-12-13. Fedora Linux 35 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.