Hide Forgot
Description of problem: Installer crashes in manual paritioning after being given password to existing LUKS encrypted partition in LVM LV inside Intel firmware RAID I install onto a system with two disks, one SSD and one Intel firmware RAID on which there is already an existing Fedora instrallation. The installer crashes after I provide the password for the encrypted partition. I tried twice, with the encrypted partition either first or last of the existing partitions to be imported to the new installation. This install is from F25 Workstation live image. The existing F25b installation (from KDE spin live image) worked fine. Version-Release number of selected component: anaconda-core-25.20.8-1.fc25.x86_64 The following was filed automatically by anaconda: anaconda 25.20.8-1 exception report Traceback (most recent call first): File "/usr/lib64/python3.5/site-packages/gi/overrides/BlockDev.py", line 441, in wrapped raise transform[1](msg) File "/usr/lib/python3.5/site-packages/blivet/devices/lvm.py", line 1928, in _setup blockdev.lvm.lvactivate(self.vg.name, self._name) File "/usr/lib/python3.5/site-packages/blivet/devices/lvm.py", line 1801, in decorated return meth(self, *args, **kwargs) # pylint: disable=not-callable File "/usr/lib/python3.5/site-packages/blivet/threads.py", line 45, in run_with_lock return m(*args, **kwargs) File "/usr/lib/python3.5/site-packages/blivet/devices/storage.py", line 372, in setup self._setup(orig=orig) File "/usr/lib/python3.5/site-packages/blivet/threads.py", line 45, in run_with_lock return m(*args, **kwargs) File "/usr/lib/python3.5/site-packages/blivet/devices/lvm.py", line 1898, in setup return DMDevice.setup(self, orig) File "/usr/lib/python3.5/site-packages/blivet/devices/lvm.py", line 1801, in decorated return meth(self, *args, **kwargs) # pylint: disable=not-callable File "/usr/lib/python3.5/site-packages/blivet/threads.py", line 45, in run_with_lock return m(*args, **kwargs) File "/usr/lib64/python3.5/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 2807, in on_unlock_clicked device.setup() File "/usr/lib64/python3.5/site-packages/pyanaconda/ui/gui/utils.py", line 267, in _run_once_one_arg self._func(*args, **kwargs) gi.overrides.BlockDev.LVMError: Process reported exit code 1280: WARNING: Device for PV JZukN5-kw3I-zct2-d0k0-PKTb-6fLj-qnqtxA not found or rejected by a filter. Refusing activation of partial LV vg_desk/encrypted. Use '--activationmode partial' to override. Additional info: addons: com_redhat_kdump cmdline: /usr/bin/python3 /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-base cmdline_file: BOOT_IMAGE=vmlinuz initrd=initrd.img root=live:CDLABEL=Fedora-WS-Live-25-1-3 rd.live.image quiet executable: /sbin/anaconda hashmarkername: anaconda kernel: 4.8.6-300.fc25.x86_64 other involved packages: python3-blockdev-1.9-8.fc25.x86_64, python3-blivet-2.1.6-4.fc25.noarch, anaconda-gui-25.20.8-1.fc25.x86_64 product: Fedora release: Fedora release 25 (Twenty Five) type: anaconda version: 25
Created attachment 1225152 [details] File: anaconda-tb
Created attachment 1225153 [details] File: anaconda.log
Created attachment 1225154 [details] File: environ
Created attachment 1225155 [details] File: journalctl
Created attachment 1225156 [details] File: lsblk_output
Created attachment 1225157 [details] File: lvm.log
Created attachment 1225158 [details] File: nmcli_dev_list
Created attachment 1225159 [details] File: os_info
Created attachment 1225160 [details] File: program.log
Created attachment 1225161 [details] File: storage.log
Created attachment 1225162 [details] File: ifcfg.log
The error happens both with the correct and with an incorrect password.
I checked another computer, this one has a LUKS encrypted partition inside an LVM but on a normal disk. No problems seeing the encrypted partition after entering the passphrase (i.e. it's working correctly and the same as F25b). My main suspect remains the Intel firmware raid that the LVM lives in, in other words.
My memory that F25 beta allowed install turned out to be correct. I did have to make second pass, selecting first an SSD partition, then an unencrypted imsm LV then the encrypted imsm LV and then it accepted the passphrase and did an install. The log files are uploadde
Created attachment 1225762 [details] GZIP'ed TAR file of installer logs, F25 Beta, install successful
Workaround found. Taking my clue from the "I did have to make second pass" I tried two installs, first one abandoned on purpose, second one finished normally. I was successful. How I installed Fedora 25, KDE spin. Setup: two disks, one SSD (/dev/sda) one IMSM RAID device administered by MDADM. The RAID device was detected on the boot and the partitions existed in /dev/mapping . There was a preexisting Fedora install, i.e. I reused most of the partitions (only formatting swap, / and /boot) Procedure: Starts "install to disk," select just the imsm device as install target, enter manual partitioning, select a few partitions from it, QUIT the installer. Start "install to disk" again, select both SSD and IMSM device as targets, set SSD as bootable device, start manual partitioning, select both SSD and IMSM device partitions, unlock LUKS encrypted LV (on IMSM device). add as partition in install, click "Done" and "begin installation." The rest of the install went as usual. Installer logs from successful run as attachment follows.
*** Bug 1399473 has been marked as a duplicate of this bug. ***
Created attachment 1225961 [details] Instal logs, successful install of F25 KDE spin on IMSM with encrypted LV
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. 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 Fedora 'version' of '25'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 25 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, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 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 please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.