Bug 622810 - LUKS partition unreadable after latest update to updates-testing
LUKS partition unreadable after latest update to updates-testing
Status: CLOSED DUPLICATE of bug 622385
Product: Fedora
Classification: Fedora
Component: device-mapper-obsolete (Show other bugs)
All Linux
low Severity medium
: ---
: ---
Assigned To: Orphan Owner
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2010-08-10 09:16 EDT by Maximiliano Bertacchini
Modified: 2010-08-10 09:36 EDT (History)
8 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-08-10 09:36:01 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Photo of error from bug #620202 Comment 8 (52 bytes, text/plain)
2010-08-10 09:20 EDT, Maximiliano Bertacchini
no flags Details

  None (edit)
Description Maximiliano Bertacchini 2010-08-10 09:16:38 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- 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):

How reproducible:

Steps to Reproduce:
1. yum upgrade (updates-testing repo enabled)
2. reboot
Actual results:
LUKS partition not found.
Message: "fsck.ext4: No such file or directory while trying to open /dev/mapper/luks-VolGroup00-lvhome"

Expected results:
Successful boot

Additional info:
See bug #620202 which describes the same issue in Comment 7.
Comment 1 Maximiliano Bertacchini 2010-08-10 09:20:37 EDT
Created attachment 437873 [details]
Photo of error from bug #620202  Comment 8
Comment 2 Milan Broz 2010-08-10 09:36:01 EDT
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 ***

Note You need to log in before you can comment on or make changes to this bug.