Red Hat Bugzilla – Bug 622810
LUKS partition unreadable after latest update to updates-testing
Last modified: 2010-08-10 09:36:01 EDT
Description of problem:
After updating to device-mapper-1.02.53-4.fc13.x86_64, the system was unable to mount a LUKS partition and exited to an emergency shell (see attached image from bug #620202). Kernel was updated to kernel-22.214.171.124-34.fc13.x86_64 in the same yum transaction. Tried reverting to device-mapper*-1.02.44-1.fc13.i686.rpm and the system booted successfully. I later found out it could boot with latest device-mapper but previous version of "/lib/udev/rules.d/10-dm.rules". I finally tried rebuilding the initramfs (i.e. dracut --force) and it fixed the issue. According to /var/log/yum.log the new kernel was installed before the device-mapper update, so I guess the initramfs needed an extra update.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. yum upgrade (updates-testing repo enabled)
LUKS partition not found.
Message: "fsck.ext4: No such file or directory while trying to open /dev/mapper/luks-VolGroup00-lvhome"
See bug #620202 which describes the same issue in Comment 7.
Created attachment 437873 [details]
Photo of error from bug #620202 Comment 8
Current lvm2/dm build in F13 updates is broken and is already removed from testing repo, I hope new update will be ready soon.
*** This bug has been marked as a duplicate of bug 622385 ***