[Bug 462224] [NEW] Booting does not wait until "remaining" disks have been unlocked

[Gillen Daniel]

Public bug reported:

Binary package hint: cryptsetup

Hi

I'm using current xubuntu 9.10 release and installed it using the
alternate disk. I set up an encrypted root partition and everything
seemed to work fine. During installation, I also set up a raid 10 array
spawning over 4 disks. After setup, I fdisk'ed /dev/md0 and created one
partition using all available space. I then encrypted this partition
(/dev/md0p1) using "cryptsetup luksCreate /dev/md0p1" and afterwards
unlocked it and formated it.

As I want to use this partition as local storage place, I added the
following line to /etc/crypttab to unlock this partition during boot (I
added a line to /etc/fstab too, in order to mount the unlocked
partition).

local_crypt /dev/disk/by-uuid/<uuid> none luks

During reboot, I am asked the password for the root partiton first,
which is ok, and afterwards, I am asked the password for /dev/md0p1
which is also ok, but booting continues after +-1 minute if I dont'
enter a password and when entering a password, the disk isn't unlocked.

After boot, I can unlock the partition manually and mount it without any
problems.

I had the same setup with xubuntu 9.04 and there it worked fine. (It was
a single disk, and no raid. But that shouldn't make any difference I
think)

Shouldn't /etc/rcS.d/S28cryptdisks interupt booting until the disks are
unlocked or isn't this possible anymore with the new upstart?

** Affects: cryptsetup (Ubuntu)
     Importance: Undecided
         Status: New

-- 
Booting does not wait until "remaining" disks have been unlocked
https://bugs.launchpad.net/bugs/462224
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs at lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs