After installing from a live iso on an encrypted root (sda10), with another encrypted file system, that is not used by the install (sda3), both of which use the same passphrase, when the passphrase is entered, both encrypted file systems are opened. There is then a second prompt for a passphrase (5 times). After either entering the passphrase, or just pressing enter, there's a message that crypt_sda10 already exists. Running dracut -f from the installed system fixes the problem.
Whiteboard: (none) => 3beta1
Created attachment 3218 [details] dracut.log from live install and from inside installed system
Priority: Normal => release_blockerCC: (none) => tmb
Can you specify if these partitions are mentioned in /etc/crypttab? If so, does removing them from there, regenerating initrd (although possibly not required) and rebooting help the issue?
Also this bug is reported against dracut, but is the question asked from dracut or the real filesystem. You can test this easily by booting with rd.break=prepivot on the kernel command line. If it asks you for the passphrase before you get a dracut shell, then it's in the initrd. If it only pops up after you've typed "exit" into the dracut shell, then it's happening on the real filesystem.
Created attachment 3445 [details] Portion of journalctl output. Turns out it has nothing to do with unused encrypted file systems. Do to some drive problems I had recently, my most recent tests have been on a system where the only encrypted file system is for the root file system being used. After an install using any of the live iso images, on any boot into the installed system, dracut asks for the password for the encrypted file system, mounts it, then asks again (5 times), each time failing to mount, as it's already mounted. After pressing enter 5 times, the boot continues normally. This happens before dropping to the rd.break=pre-pivot shell. It's fixed by running dracut -f, after booting into the system. The attached output from journalctl shows the order that things are happening.
*** Bug 8913 has been marked as a duplicate of this bug. ***
CC: (none) => matali
Whiteboard: 3beta1 => 3beta2
problem is solved this week too, i didn't changed anything, but I'm not asked for passphrase anymore. For me can the bug be closed.
Dave, can you confirm?
CC: (none) => sander.lepik
No. Installs done with the standard installer are ok, but not installs done using the live iso, which are currently blocked by Bug 9213.
Depends on: (none) => 9213
strange, i really didn't changed any config files... and i installed one month ago with the live iso ( i can't with install due to an ati proprietary driver's bug).
What about this bug guys? Can we try to test it all from a new install and then close it if all is ok?
CC: (none) => ennael1
The fix for bug 9213 seems to have fixed this one too.
Status: NEW => RESOLVEDResolution: (none) => FIXED