Red Hat Bugzilla – Bug 466115
Encrypted logical volumes aren't mounted during boot
Last modified: 2011-05-29 19:07:09 EDT
Description of problem:
When using lvm and cryptsetup/luks together, init is unable to mount LVM logical volumes if encrypted.
In such case, system system fails to start at all, because block device specified in /etc/fstab doesn't exist.
This is caused by fact, function init_crypto in rc.sysinit is called before lvm initialization and logical volumes are unknown at that moment. In Fedora init_crypto is called two times, additional execution is right after lvm initialization stuff.
Version-Release number of selected component (if applicable):
This issue occurs, if LVM logical volume is encrypted with cryptsetup/luks.
System doesn't boot and init drops to shell asking root for maintenance.
System should boot with all filesystems mounted.
So, presumably this works for you?
diff --git a/rc.d/rc.sysinit b/rc.d/rc.sysinit
index 7f28783..0972aed 100755
@@ -458,6 +458,14 @@ if [ -c /dev/mapper/control ]; then
+if [ -f /etc/crypttab ]; then
+ s=$"Starting disk encryption:"
+ echo "$s"
+ init_crypto 0 && success "$s" || failure "$s"
if [ -f /fastboot ] || strstr "$cmdline" fastboot ; then
Yes, this is the patch, which will fix the issue.
Confirmed, system is able to boot with described configuration.
Tested on: RHEL5.3-Server-20081020.1
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.