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
@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.
--
@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 eit
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
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 s
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 s
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 mo
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.)
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
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 t
"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
...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 en
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
** 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.
--
ubun
** 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.
--
ubun
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.
T
** 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
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, w
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
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 th
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
** 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, wh
** 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 li
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 underlyi
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
> 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 U
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
h
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/s
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.laun
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 wher
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 o
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
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
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 th
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://
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.
--
ubunt
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
> 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.
Ev
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
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
40 matches
Mail list logo
