What runs "Setting up disk encryption?"

[Clyde E. Kunkel]

How do I get all LVs to activate before activation of disk encryption?

I am mounting an encrypted filesystem in fstab that resides on a VG 
different from my un-encrypted root filesystem.

The root LV is initialized in the initrd, but the remaining are not 
initialized until after udev starts.  This apparently leads to an 
initial failure, based on the msgs I am seeing, for "Starting disk 
encryption" preceeds "Setting up Logical Volume Management".  After LVM 
is setup, "Starting Disk Encryption" is run again and I can enter the 
pass phrase and all is well.

Tho the problem is currently self healing, it seems that something is 
out of sync.

-- 
---------------------------------
Regards,

Old Fart

What runs "Setting up disk encryption" in F9 prerelease?

[Clyde E. Kunkel]

Clyde E. Kunkel wrote:
>  How do I get all LVs to activate before activation of disk
> encryption?
>  
>  I am mounting an encrypted filesystem in fstab that resides on a VG 
>  different from my un-encrypted root filesystem.
>  
>  The root LV is initialized in the initrd, but the remaining are not 
>  initialized until after udev starts.  This apparently leads to an 
>  initial failure, based on the msgs I am seeing, for "Starting disk 
>  encryption" preceeds "Setting up Logical Volume Management".  After LVM 
>  is setup, "Starting Disk Encryption" is run again and I can enter the 
>  pass phrase and all is well.
>  
>  Tho the problem is currently self healing, it seems that something is 
>  out of sync.
>   

Anyone?  This is Fedora 9 prerelease updated to current.

-- 
---------------------------------
Regards,

Old Fart

What runs "Setting up disk encryption" in F9 prerelease?

[Andrew Farris]

Clyde E. Kunkel wrote:
>  Clyde E. Kunkel wrote:
> > How do I get all LVs to activate before activation of disk encryption?
> >
> > I am mounting an encrypted filesystem in fstab that resides on a VG 
> > different from my un-encrypted root filesystem.
> >
> > The root LV is initialized in the initrd, but the remaining are not 
> > initialized until after udev starts.  This apparently leads to an 
> > initial failure, based on the msgs I am seeing, for "Starting disk 
> > encryption" preceeds "Setting up Logical Volume Management".  After 
> > LVM is setup, "Starting Disk Encryption" is run again and I can enter 
> > the pass phrase and all is well.
> >
> > Tho the problem is currently self healing, it seems that something is 
> > out of sync.
> >
>  
>  
>  Anyone?  This is Fedora 9 prerelease updated to current. 
Interesting problem.  I don't know the answer to what does it, but since you 
have the choice of either encrypting the entire volume group or the logical 
volumes separately I think it must start before LVM gets started.  Otherwise, 
you might not be able to read anything to find out if you need to decrypt it. 
It may just be an unfortunate sequence that has to happen for your particular setup.

-- 
Andrew Farris <lordmorgul(a)gmail.com&gt; www.lordmorgul.net
  gpg 0x8300BF29 fingerprint 071D FFE0 4CBC 13FC 7DEB  5BD5 5F89 8E1B 8300 BF29

[Bruno Wolff III]

On Tue, Apr 29, 2008 at 15:17:44 -0400,
  "Clyde E. Kunkel" <clydekunkel7734(a)cox.net&gt; wrote:
>  How do I get all LVs to activate before activation of disk
> encryption?
>
>  I am mounting an encrypted filesystem in fstab that resides on a VG 
>  different from my un-encrypted root filesystem.
>
>  The root LV is initialized in the initrd, but the remaining are not 
>  initialized until after udev starts.  This apparently leads to an initial 
>  failure, based on the msgs I am seeing, for "Starting disk encryption" 
>  preceeds "Setting up Logical Volume Management".  After LVM is setup, 
>  "Starting Disk Encryption" is run again and I can enter the pass phrase and 
>  all is well.
>
>  Tho the problem is currently self healing, it seems that something is out 
>  of sync. 
I don't think that that is a problem. I run a machine with 4 encrypted
raid partitions and / and swap are done first and the other two are done by
udev.

My guess is that because you have some encrypted file systems that you get
the init script trying to get any keys needed early in the boot process,
even though in your particular case this step isn't needed.

[Gordon Messmer]

Clyde E. Kunkel wrote:
>  How do I get all LVs to activate before activation of disk
> encryption? 
Look at /etc/rc.d/rc.sysinit.  You'll notice that init_crypto is called 
several times to bring up devices as they become available.  You 
probably have an LV on a device that's brought up in the section that 
runs the multipath and dmraid tools.

You might be able to modify the init_crypto function to bail out if 
"$src" doesn't exist, which would avoid showing you the error.  I wonder 
if that would be accepted as a bug report, and fixed in init-scripts...