[Bug 430496] Re: cryptsetup devices not mounted on boot

[Boris]

The cause (for me) of these problems in Lucid was due to cryptsetup not
removing NL/LF characters in the password file. Temporary fix is
obviously entering the password in a file without such characters.

echo -n secretpasswordstring > /etc/cryptkey

-- 
cryptsetup devices not mounted on boot
https://bugs.launchpad.net/bugs/430496
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

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

[Bug 430496] Re: cryptsetup devices not mounted on boot

[Dave]

@throughnothing thanks - that bug's related to init scripts, which i
didn't *think* was an issue for me, since they're not in /etc/rc2.d/,
but then I'm now quite foggy about how the whole boot process works
these days.  The symptoms certainly match, so I'll post my observations
there.  Cheers.

-- 
cryptsetup devices not mounted on boot
https://bugs.launchpad.net/bugs/430496
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

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

[Bug 430496] Re: cryptsetup devices not mounted on boot

[throughnothing]

@Dave Check and see if this bug matches your symptoms.  I have been
having the issues that I mention in the folowing ticket:

https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/473615

If you think this fits what you are experiencing, maybe make a comment
there if it is not fixed for you either.

-- 
cryptsetup devices not mounted on boot
https://bugs.launchpad.net/bugs/430496
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

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

[Bug 430496] Re: cryptsetup devices not mounted on boot

[Dave]

Did another bug get open for this (as per #49/#50)?  I haven't been able
to find one.

I am seeing the same behaviour as comment #25, with a brand new install
of 9.10, which I then updated meaning I have cryptsetup
2:1.0.6+20090405.svn49-1ubuntu7.2 and mountall 1.0.  If I don't have
'bootwait', gdm starts, but my encrypted partition isn't mounted (and
switching back to tty1 there is no sign of a prompt for the passphrase).
If I do set 'bootwait' for the partition, the boot stops when mounting
fails.  A few hits of return sometimes gives a passphrase prompt, which
doesn't work, saying the passphrase is wrong, as if it's only seeing the
'return', and not any other keystrokes.  After a mixture of repeated
attempts (so cryptsetup fails?) or waiting for mountall to timeout (I'm
guessing), I eventually managed to get a maintenance prompt, so that I
could remove the 'bootwait', and at least get back in to a state where
the machine booted.  (trying to boot in to single user mode to remove
the 'bootwait' didn't work, because it still hit the failing mount).

/etc/crypttab:
# 
data/dev/sda6   noneluks
cswap   /dev/sda5   /dev/urandomswap

/etc/fstab:
/dev/mapper/data/mnt/data   ext3defaults,relatime   1   
2
/dev/mapper/cswap   noneswapsw  0   0

cswap appears to work *sometimes*, but usually only after a huge delay.
dmesg for this boot (no 'bootwaits' in fstab) shows me that it came up
after 2137 seconds.

BTW, 'data' isn't one of the 'essential' system mount points, but does
contain, among other things, /home.

If there is another open bug that this should be posted to instead, let
me know.

Cheers,
--Dave

-- 
cryptsetup devices not mounted on boot
https://bugs.launchpad.net/bugs/430496
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

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

[Bug 430496] Re: cryptsetup devices not mounted on boot

[Kevin C]

Using Kubuntu 9.10 alternate CD.

First time, I encrypted using manual partition during install, which creates 
/etc/crypttab and /etc/fstab entries for /home and swap.
Same issues on boot, kdm refuses to accept the password, no matter how many 
times entered.

Second time, I installed only / and swap (using random key so no
password required), it gives waiting for swap partition to be
initialized, then proceeds with /etc/fstab.  Adding a manual encrypted
/home (requiring a password) gives the original problem.

This has worked well in previous releases since 2007 June, only Karmic
has made some changes which have caused this problem.

-- 
cryptsetup devices not mounted on boot
https://bugs.launchpad.net/bugs/430496
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

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

[Bug 430496] Re: cryptsetup devices not mounted on boot

[Kevin C]

Using Kubuntu 9.10 alternate CD.

First time, I encrypted using manual partition during install, which creates 
/etc/crypttab and /etc/fstab entries for /home and swap.
Same issues on boot, kdm refuses to accept the password, no matter how many 
times entered.

Second time, I installed only / and swap (using random key so no
password required), it gives waiting for swap partition to be
initialized, then proceeds with /etc/fstab.  Adding a manual encrypted
/home (requiring a password) gives the original problem.

This has worked well in previous releases since 2007 June, only Karmic
has made some changes which have caused this problem.

-- 
cryptsetup devices not mounted on boot
https://bugs.launchpad.net/bugs/430496
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

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

[Bug 430496] Re: cryptsetup devices not mounted on boot

[Steve Langasek]

Yes, I think we want a new bug report because we know we've already
fixed *a* bug here, and we know you're seeing a problem in a case where
bootwait makes no difference.  That's a different bug than the one we've
been tracking, despite having broadly similar symptoms.

-- 
cryptsetup devices not mounted on boot
https://bugs.launchpad.net/bugs/430496
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

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

Re: [Bug 430496] Re: cryptsetup devices not mounted on boot

[Pete Phillips]

Hi Steve

Just to confirm - you want me to file a bug report on this even though
it sounds like a duplicate of the issues that others are seeing ?

(it doesn't sound like a cryptsetup problem to me - it sounds as if it
is related to the issue of other programs eating the stdin - but i'm no
expert.)

Happy to do this if you think this is a distinct bug.

Pete

-- 
cryptsetup devices not mounted on boot
https://bugs.launchpad.net/bugs/430496
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

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

[Bug 430496] Re: cryptsetup devices not mounted on boot

[Steve Langasek]

Pete,

The 'bootwait' option should have no effect for the /home filesystem.

Could you please file a new bug report against the cryptsetup package
for the issue you're describing?

-- 
cryptsetup devices not mounted on boot
https://bugs.launchpad.net/bugs/430496
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

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

[Bug 430496] Re: cryptsetup devices not mounted on boot

[Pete Phillips]

I am also experiencing this with Karmic.   I find that I have to enter
my passphrase multiple times.  Sometimes it doesn't work at all, and I
have to Ctrl/Alt/Del, reboot, and then try again. Eventually the system
gets my passphrase, but this is clearly a mission critical problem.  I
haven't seen the password prompt not appear - rather something appears
to be eating my keystrokes.

My crypttab is:

  lap1:[~] % cat /etc/crypttab 
  #   
  crypt-home/dev/sda3   noneluks

fstab:

  dev/mapper/crypt-home /home   ext3defaults,relatime   0
2

Will adding 'bootwait' to the fstab options help ?

Pete

-- 
cryptsetup devices not mounted on boot
https://bugs.launchpad.net/bugs/430496
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

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

[Bug 430496] Re: cryptsetup devices not mounted on boot

[Steve Langasek]

"cryptdisks-early" - well, that's not supposed to be responsible for
decrypting the disks anyway, we have a native upstart job that's
supposed to take care of it.  The init scripts were left in the package
in Ubuntu 9.10 by mistake; I just don't know if it's safe to try to
remove them in SRU.

Yes - you're right that cryptdisks-early will block, and that this will
prevent ttys from starting but not prevent gdm from starting.  I'll have
a look at fixing this as an SRU to karmic.

-- 
cryptsetup devices not mounted on boot
https://bugs.launchpad.net/bugs/430496
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

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

[Bug 430496] Re: cryptsetup devices not mounted on boot

[Blue]

...with bootwait added to fstab the thing waits indefinitely for the password, 
which is good. (it still produces "some filesystem could not be mounted, pres 
esc for recovery shell,etc" (which is not appropriate in this context), 
However, at least it waits with every thing untill passphrase is entered.
Without bootwait, the above mentioned scenario happens (gdm starts, ttys do 
not).
Also, shouldn't the bootwait documented somewhere in the manpages? When I first 
ran into this I looked up the mount manpage to find such an option, quite like 
_netdev is mentioned in the same manpage.

-- 
cryptsetup devices not mounted on boot
https://bugs.launchpad.net/bugs/430496
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

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

[Bug 430496] Re: cryptsetup devices not mounted on boot

[Blue]

Sorry for the previous duplicate file.


** Attachment added: "pstree_before.txt"
   http://launchpadlibrarian.net/34978372/pstree_before.txt

-- 
cryptsetup devices not mounted on boot
https://bugs.launchpad.net/bugs/430496
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

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

[Bug 430496] Re: cryptsetup devices not mounted on boot

[Blue]

** Attachment added: "pstree_after.txt"
   http://launchpadlibrarian.net/34978219/pstree_after.txt

-- 
cryptsetup devices not mounted on boot
https://bugs.launchpad.net/bugs/430496
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

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

[Bug 430496] Re: cryptsetup devices not mounted on boot

[Blue]

** Attachment added: "pstree_after.txt"
   http://launchpadlibrarian.net/34978193/pstree_after.txt

-- 
cryptsetup devices not mounted on boot
https://bugs.launchpad.net/bugs/430496
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

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

[Bug 430496] Re: cryptsetup devices not mounted on boot

[Blue]

I attached two process lists that prove my previous post. The first listing is 
the process list as the system boots (and i log on using gdm). It can be seen 
that the cryptsetup scripts are running, and waiting for a passphrase. It can 
be seen that no tty nor other daemons like ssh are running.
The second listing is obtained after I manually killed the crypto scripts. It 
can be seen that both ttys and other daemons started.
I also added a pstree before and after.


** Attachment added: "psax_after.txt"
   http://launchpadlibrarian.net/34978022/psax_after.txt

-- 
cryptsetup devices not mounted on boot
https://bugs.launchpad.net/bugs/430496
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

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

[Bug 430496] Re: cryptsetup devices not mounted on boot

[Blue]

** Attachment added: "psax_before.txt"
   http://launchpadlibrarian.net/34978123/psax_before.txt

-- 
cryptsetup devices not mounted on boot
https://bugs.launchpad.net/bugs/430496
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

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

[Bug 430496] Re: cryptsetup devices not mounted on boot

[Blue]

Sorry, but I think you are wrong. While cryptdisks-early is running (and
waiting for a passphrase) tty's will NOT start, however gdm will.

-- 
cryptsetup devices not mounted on boot
https://bugs.launchpad.net/bugs/430496
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

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

Re: [Bug 430496] Re: cryptsetup devices not mounted on boot

[Steve Langasek]

On Mon, Nov 02, 2009 at 08:18:39AM -, Blue wrote:

>  Shouldn't this at least be fully consistent ? I mean ok, you do not wait
> for non core filesystems, but you either do not wait with anything unless
> bootwait is specified, or you wait with everything ?

No, the default is to wait only for those filesystems that are known to be
required for successfully starting the other services.  cryptsetup is a
special case in that it interferes with gdm startup directly, regardless of
where the related filesystems are mounted (and even if they're not mounted
at all by default).

We should try to find a better solution for Lucid on this issue that doesn't
require use of bootwait.

> Now, tty's will wait for any filesystem but gdm won't.

Not true; both gdm and ttys wait for the same set of filesystems, gdm is
just started first whereas ttys are started only after the rest of the init
scripts run.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developerhttp://www.debian.org/
slanga...@ubuntu.com vor...@debian.org

-- 
cryptsetup devices not mounted on boot
https://bugs.launchpad.net/bugs/430496
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

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

[Bug 430496] Re: cryptsetup devices not mounted on boot

[Blue]

PS
 Shouldn't this at least be fully consistent ? I mean ok, you do not wait for 
non core filesystems, but you either do not wait with anything unless bootwait 
is specified, or you wait with everything ? Now  tty's will not start while gdm 
will start.
One would rather expect tty's to start so that you can log on another console 
and resolve things, not the gdm to start.
Even more than that, i think that  if such a filesystem (non core filesystem) 
will fail for some reason (for example it had a severe corruption ), then weird 
things will happen : 
- first you WILL need at least a tty to log in and solve the problem
- you must not have gdm steal your display and keyboard
I think tty's should be one of the first things to load, and either way load 
before gdm (at least if the core file systems are ok).
Now, tty's will wait for any filesystem but gdm won't.

-- 
cryptsetup devices not mounted on boot
https://bugs.launchpad.net/bugs/430496
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

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

[Bug 430496] Re: cryptsetup devices not mounted on boot

[Blue]

Steve :
I will try with bootwait  and i'll get back to you.
It is actually used for a core fs, but indirectly (mounts somewhere, and then 
bind mounts from somewhere are created for some user homes)

-- 
cryptsetup devices not mounted on boot
https://bugs.launchpad.net/bugs/430496
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

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

[Bug 430496] Re: cryptsetup devices not mounted on boot

[Steve Langasek]

** Changed in: ubuntu-release-notes
   Status: New => Triaged

** Changed in: ubuntu-release-notes
   Importance: Undecided => Medium

-- 
cryptsetup devices not mounted on boot
https://bugs.launchpad.net/bugs/430496
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

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

[Bug 430496] Re: cryptsetup devices not mounted on boot

[Steve Langasek]

** Also affects: ubuntu-release-notes
   Importance: Undecided
   Status: New

-- 
cryptsetup devices not mounted on boot
https://bugs.launchpad.net/bugs/430496
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

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

Re: [Bug 430496] Re: cryptsetup devices not mounted on boot

[Steve Langasek]

On Sat, Oct 31, 2009 at 10:12:35PM -, Blue wrote:
> This is a quite simple and straightforward scenario

Well, no, not really.  To have run into the problem you did, you must have
devices configured in your /etc/crypttab that are being enabled at boot
time, but that are not used as the underlying devices for any core
filesystems, including /, /usr, /var, or /home (or even swap).  I think
that's quite an unusual setup.

To work around this issue, you can mark the filesystem that sits on the
encrypted volume as "bootwait" in your /etc/fstab, as documented in the
release notes:


We could do with an explicit comment there about the need for this with
cryptsetup.  Opening a task on ubuntu-release-notes for this.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developerhttp://www.debian.org/
slanga...@ubuntu.com vor...@debian.org

-- 
cryptsetup devices not mounted on boot
https://bugs.launchpad.net/bugs/430496
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

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

Re: [Bug 430496] Re: cryptsetup devices not mounted on boot

[gpz]

Marc A. Donges wrote:
>> swap: waiting for /dev/mapper/swap
>> /var/tmp: waiting for tmpfs
>> 
>
> Please show /etc/fstab and /etc/crypttab.
>
> Marc
>
>   
It is my fault, sorry. The bug is  not the above.
I am user. Yesterday, i tried to upgrade the ubuntu 9.04
to 9.10. All things were going right, but when finished
the installation, the ethernet card stoped. The informations
of my ethernet card is :

09:00.0 Ethernet controller: Attansic Technology Corp. Atheros 
AR8121/AR8113/AR8114 PCI-E Ethernet Controller (rev b0)
Subsystem: Acer Incorporated [ALI] Device 015e
Flags: fast devsel, IRQ 17
Memory at be10 (64-bit, non-prefetchable) [size=256K]
I/O ports at 3000 [size=128]
Capabilities: [40] Power Management version 2
Capabilities: [48] Message Signalled Interrupts: Mask- 64bit+ 
Queue=0/0 Enable-
Capabilities: [58] Express Endpoint, MSI 00
Capabilities: [6c] Vital Product Data 
Capabilities: [100] Advanced Error Reporting 
Capabilities: [180] Device Serial Number ff-8b-23-00-b6-2b-16-ff
Kernel modules: atl1e


The last kernel, wich the above card were  working, is 2.6.28-16 for 
64bit version.


The upgrade install the kernel 2.6.31-14. That kernel has not drivers 
for my ethernet controller.
I was looking for that problem and find the next :

http://ubuntuforums.org/showthread.php?t=770173&page=1

but when download the appropriate source files and try to compile 
receive error
for 'struct' of data.

I think it is useful to describe the problem and it will fixed at the 
feauter, because
i think the ubuntu is very nice OS and it must be at the top...

Thanks.

-- 
cryptsetup devices not mounted on boot
https://bugs.launchpad.net/bugs/430496
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

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

Re: [Bug 430496] Re: cryptsetup devices not mounted on boot

[Marc A. Donges]

> swap: waiting for /dev/mapper/swap
> /var/tmp: waiting for tmpfs

Please show /etc/fstab and /etc/crypttab.

Marc

-- 
cryptsetup devices not mounted on boot
https://bugs.launchpad.net/bugs/430496
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

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

[Bug 430496] Re: cryptsetup devices not mounted on boot

[dvhart]

OK, commenting out the swap partition and the two tmpfs mountpoints from
/etc/fstab allows the boot sequence to continue after interrupting
mountall to run "/etc/init.d/cryptdisk start;  mount /home". At least I
can use my system while we sort this out.

-- 
cryptsetup devices not mounted on boot
https://bugs.launchpad.net/bugs/430496
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

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

[Bug 430496] Re: cryptsetup devices not mounted on boot

[dvhart]

I have home and swap as cryptdisks and after the upgrade to karmic today
I don't get the passphrase prompt at all, the boot just hangs at:

One or more of the mounts listed /etc/fstab cannot yet be mounted:
(ESC for recovery shell)
/home: waiting for /dev/mapper/home
swap: waiting for /dev/mapper/swap
/var/tmp: waiting for tmpfs

If I enter the recovery shell and run "/etc/init.d/cryptdisks start" I
get the prompt and can then type "mount /home" and "swapon
/dev/mapper/swap" to successfully mount those partitions.  However,
CTRL-D returns to output the following:

mountall start/starting
One of more of the mounts listed in /etc/fstab cannot yet be mounted:
(ESC recovery shell)
swap: waiting for /dev/mapper/swap
/var/tmp: waiting for tmpfs

(home isn't listed that time)

Does anyone know of a way to at least get this system to boot for the
time being?

-- 
cryptsetup devices not mounted on boot
https://bugs.launchpad.net/bugs/430496
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

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

[Bug 430496] Re: cryptsetup devices not mounted on boot

[Blue]

PS : 
As gdm overtook the keyboard and screen, it seems that the init scripts somehow 
hang, and other things like for example the tty's do not start at all. You'll 
have to get back to tty1 and send a few enters to unhang  the sequence.

-- 
cryptsetup devices not mounted on boot
https://bugs.launchpad.net/bugs/430496
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

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

[Bug 430496] Re: cryptsetup devices not mounted on boot

[Blue]

Just reproduced this on a fresh install in a VM:
- made a clean install;
- cryptsetup luksFormat /dev/somepartition
- added esomepartition /dev/somepartition  none luks
in /etc/crypttab
-added /dev/mapper/esomepartition in /etc/fstab
rebooted.
After reboot, the startup scripts get to the point where a password for the 
encrypted partition is asked.
However, after just a few keystrokes gdm overtakes the screen and the keyboard.
This is a quite simple and straightforward scenario, has anyone tested these 
things ?!

-- 
cryptsetup devices not mounted on boot
https://bugs.launchpad.net/bugs/430496
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

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

[Bug 430496] Re: cryptsetup devices not mounted on boot

[Blue]

This is not quite fixed, yet.
I encounter the following issues :
*  the startup scripts do not always succed in correctly unlocking the keyslot. 
Looks like sometimes the keyboard
input does not get to the password reader but to something else. 
* And if you can switch  to console 8 unfortunately one can even see the 
password typed in the first console where the luks password was asked; This is 
not ok first because the password does not get where it should get, and second 
because it creates a security risk as anyone could press (ctrl)-alt-f8 and see 
the password for the encrypted disk(s).
* if cryptdisks is enabled, all other services should depend on cryptdisks, 
nothing should continue until the user either correctly  unlocks all the 
encrypted volumes OR he cancels the operation or he fails the password for the 
numtries parameter in crypttab.
NOW, for example gdm starts anyway. Needless to say, this create an issue when 
you are trying to enter the cryptovolumes password and  then gdm takes over the 
screen and the keyboard.
* The tty's on the other side seem to wait for the cryptdisks. This creates the 
following issue : If you did not manage to properly enter the password, after 
gdm started you could try to switch back to console 1 and retry to enter the 
password. However, because of how the dependencies are made, you are presented 
with a blank screen. If you press enter a few times, eventually the startup 
sequence completes (i think it actually terminates cryptdisks init script) and 
so the other services get to be started (getty for ex).

-- 
cryptsetup devices not mounted on boot
https://bugs.launchpad.net/bugs/430496
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

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

[Bug 430496] Re: cryptsetup devices not mounted on boot

[Martin Pitt]

So the blkid output is correct, thanks. Seems that the cryptsetup mount
scripts or mountall break things then.

-- 
cryptsetup devices not mounted on boot
https://bugs.launchpad.net/bugs/430496
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

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

[Bug 430496] Re: cryptsetup devices not mounted on boot

[Swistak]

Here's the output:
/dev/sda6: UUID="9d5d03d5-85ba-4a4e-9fbe-e87c650cd800" VERSION="256" 
TYPE="crypto_LUKS" USAGE="crypto"
It's my /home partition.

Basically when usplash is on I'm asked to type the password and after doing 
that system boots correctly, even though I get something like "Could not mount 
all entries in /etc/fstab".
With usplash off I'm asked for password several times and it has no effect.

-- 
cryptsetup devices not mounted on boot
https://bugs.launchpad.net/bugs/430496
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

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

Re: [Bug 430496] Re: cryptsetup devices not mounted on boot

[Martin Pitt]

Swistak [2009-10-23 20:51 -]:
> It seems to me that it's not completely fixed. I have usplash disabled
> ("splash" option removed from GRUB configuration) and still experience
> this problem. When I to re-enabled splash mounting encrypted /home went
> fine. 

usplash is not at all related to this original blkid fix. Can you
please give us the output of "sudo blkid -p /dev/affected_device"?
(Find it out with "mount" in a working system).

-- 
cryptsetup devices not mounted on boot
https://bugs.launchpad.net/bugs/430496
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

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

[Bug 430496] Re: cryptsetup devices not mounted on boot

[Swistak]

It seems to me that it's not completely fixed. I have usplash disabled
("splash" option removed from GRUB configuration) and still experience
this problem. When I to re-enabled splash mounting encrypted /home went
fine. Scott: Could you check it?

-- 
cryptsetup devices not mounted on boot
https://bugs.launchpad.net/bugs/430496
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

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

[Bug 430496] Re: cryptsetup devices not mounted on boot

[GiuseppeVerde]

scott: see bug #431040, please. I'd like to help (especially since it's
made my laptop unusable!).

-- 
cryptsetup devices not mounted on boot
https://bugs.launchpad.net/bugs/430496
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

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

Re: [Bug 430496] Re: cryptsetup devices not mounted on boot

[Scott James Remnant]

On Thu, 2009-09-17 at 19:02 +, Luka Renko wrote:

> > debian/cryptdisks-enable.upstart: Things that often help include
> >  not setting stdin/out to /dev/null, so you can actually type the
> >  passphrase. I am an idiot. LP: #430496.
> 
> Scott, no: you rock! Because you dare to change this old kludge of
> sysvinit and moving us in new world with upstart.
> 
> Everything works now with my /home on dm-crypt+LVM and this is for the first 
> time in Karmic cycle. Thanks!
> I will also close my older (pre upstart job).
> 
This may not fix it for everybody, but I would appreciate it if those
people could open new bugs individually rather than commenting here.

With so many different fstab and crypttab combinations, while they often
sound like the same bug, the fixes are often quite different.

Scott
-- 
Scott James Remnant
sc...@canonical.com

-- 
cryptsetup devices not mounted on boot
https://bugs.launchpad.net/bugs/430496
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

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

[Bug 430496] Re: cryptsetup devices not mounted on boot

[Luka Renko]

> debian/cryptdisks-enable.upstart: Things that often help include
>  not setting stdin/out to /dev/null, so you can actually type the
>  passphrase. I am an idiot. LP: #430496.

Scott, no: you rock! Because you dare to change this old kludge of
sysvinit and moving us in new world with upstart.

Everything works now with my /home on dm-crypt+LVM and this is for the first 
time in Karmic cycle. Thanks!
I will also close my older (pre upstart job).

-- 
cryptsetup devices not mounted on boot
https://bugs.launchpad.net/bugs/430496
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

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

[Bug 430496] Re: cryptsetup devices not mounted on boot

[Launchpad Bug Tracker]

This bug was fixed in the package cryptsetup -
2:1.0.6+20090405.svn49-1ubuntu4

---
cryptsetup (2:1.0.6+20090405.svn49-1ubuntu4) karmic; urgency=low

  * debian/cryptdisks-enable.upstart: Things that often help include
not setting stdin/out to /dev/null, so you can actually type the
passphrase.  I am an idiot.  LP: #430496.

 -- Scott James RemnantThu, 17 Sep 2009 17:58:01
+0100

** Changed in: cryptsetup (Ubuntu Karmic)
   Status: Triaged => Fix Released

-- 
cryptsetup devices not mounted on boot
https://bugs.launchpad.net/bugs/430496
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

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

[Bug 430496] Re: cryptsetup devices not mounted on boot

[Rick Spencer]

Changing to critical as it keeps a service from starting

** Changed in: cryptsetup (Ubuntu Karmic)
   Importance: High => Critical

-- 
cryptsetup devices not mounted on boot
https://bugs.launchpad.net/bugs/430496
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

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