Bug 980587

Summary: Upgrade from F18 to F19 via FedUp on encrypted system (luks/dm-crypt, no LVM), can't boot normally
Product: [Fedora] Fedora Reporter: Garve <xgarve>
Component: systemdAssignee: systemd-maint
Status: CLOSED CANTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 19CC: fabian.deutsch, harald, johannbg, lnykryn, msekleta, notting, plautrba, systemd-maint, vpavlin, zbyszek
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-07-04 08:14:28 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Garve 2013-07-02 19:11:17 UTC 
Description of problem:
After upgrading from F18 to F19 via FedUp I can't boot Fedora normally anymore. The password prompt appears, I type the password, then the prompt keeps appearing again and again. After some trials I end up in dracut.

If I choose the Rescue entry in GRUB it starts normally like before, when I used F18.

Version-Release number of selected component (if applicable):


How reproducible:
Start Fedora 19, use any GRUB option except for rescue mode.

Steps to Reproduce:
1.
2.
3.

Actual results:
Can't boot.

Expected results:
Boot normally.

Additional info:
The last errors are

[DEPEND] Dependency failed for Encrypted Volumes.
[DEPEND] Dependency failed for Initrd Default Target.
[FAILED] Failed to start Cryptography Setup for luks-<number>
Comment 1 Harald Hoyer 2013-07-03 12:05:32 UTC 
Does a:

# dracut --regenerate-all --force

cure the problem?
Comment 2 Garve 2013-07-03 14:54:21 UTC 
Hi, Harald.

Yes it works indeed, thank you very much!
Comment 3 Fabian Deutsch 2013-08-01 16:22:19 UTC 
I'm facing the same problem after an update from F18 to F19 using fedup.

But running the command given in comment #1 doesn't solve the problem for me.
Comment 4 Fabian Deutsch 2013-08-01 16:27:57 UTC 
ah no, I've got a slightly different error  msg. Sorry for the noise.