Ubuntu
cryptsetup package

  1. Bug #298906
  2. Comment #11

Comment 11 for bug 298906

Revision history for this message
Mattias Evensson (mevensson) wrote :

I can only speak for myself but I don't have this problem anymore. I think it was solved when I upgraded to Jaunty, I'm currently running on the Karmic beta.

I still have the same setup with the root fs on LVM on a LUKS encrypted md1.

I checked the commit log in the bazaar branch and found this:
revno: 56
tags: 2:1.0.6-7ubuntu6
author: Steve Langasek <email address hidden>
committer: Bazaar Package Importer <email address hidden>
branch nick: jaunty
timestamp: Sat 2009-03-07 13:39:14 -0800
message:
  debian/initramfs/cryptroot-script: we don't require vol_id to understand
  the encrypted device, but we should check the device is fully up first
  before continuing by calling udevadm settle. LP: #291752.

It added a call to udevsettle before the retry loop which might explain why it works.