I have the same problem but with regular encrypted partition. I enabled
proposed repository and updated cryptsetup, but it didn't help. If I
don't have bootwait in fstab boot process continues without waiting for
the password. If I add bootwait for that device in fstab it asks for the
password but
This bug was fixed in the package cryptsetup -
2:1.0.6+20090405.svn49-1ubuntu7.2
---
cryptsetup (2:1.0.6+20090405.svn49-1ubuntu7.2) karmic-proposed; urgency=low
* Depend on watershed.
* cryptdisks.functions: do_tmp should mount under /var/run/cryptsetup for
changing the permis
There's still a real, fixable bug here that we've identified, i.e., that
the old upstart job could completely miss *prompting* for a device
that's plugged in and hang the boot forever. So we'll continue to track
that here.
--
cryptsetup starts too early
https://bugs.launchpad.net/bugs/454898
You
Steve,
Ok I'm going to use "noauto".
I'm not quite sure there is a point to support my usecase (too complex
and too specific).
You can set this bug to "won't fix". I'm fine with that.
--
cryptsetup starts too early
https://bugs.launchpad.net/bugs/454898
You received this bug notification becaus
Xavier,
There are two configurations for such devices that are supported by
karmic:
- configure the filesystem as 'bootwait' in /etc/fstab. This will block the
boot indefinitely waiting for the device, to ensure that slow hardware does not
prevent the passphrase prompt from being displayed.
-
Well, using 'defaults,bootwait' it does work.
However, I use a set of encrypted SDcards.
If there is no card in the slot, it does not boot anymore (I only get a
maintenance shell).
That's why I put:
/dev/mapper/data/home/gnata/data ext4defaults0 1
and not:
/dev/mapp
Xavier,
If you change the options on the fstab entry to 'defaults,bootwait' (as
mentioned in the Ubuntu 9.10 release notes), does this make a
difference?
--
cryptsetup starts too early
https://bugs.launchpad.net/bugs/454898
You received this bug notification because you are a member of Ubuntu
Bu
> Also, when this hang occurs, please check whether you have multiple
> 'watershed' processes running. If the boot-time cryptsetup has hung for
> whatever reason, 'cryptdisks restart' will also hang waiting, to avoid
> colliding with the one that's already running.
>
>
ok. I stop /etc/init.d
Also, when this hang occurs, please check whether you have multiple
'watershed' processes running. If the boot-time cryptsetup has hung for
whatever reason, 'cryptdisks restart' will also hang waiting, to avoid
colliding with the one that's already running.
--
cryptsetup starts too early
https:/
Xavier,
Can you please attach your /etc/fstab and /etc/crypttab here?
--
cryptsetup starts too early
https://bugs.launchpad.net/bugs/454898
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.u
Something has changed but that's not that good:
It does not ask for the password during the boot.
Worst, /etc/init.d/cryptdisks restart now hangs:
* Stopping remaining crypto
disks... * data
(stopped)...
Accepted cryptsetup into karmic-proposed, the package will build now and
be available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advance!
** Changed in: cryptsetup (Ubuntu Ka
** Description changed:
I hope that the tilte is correct.
I have encrypted a sdcard using cryptsetup.
During the boot sequence, it does not ask for the password. I fail to find an
error message in the logs.
I think my config is ok because /etc/init.d/cryptdisks start does work:
* Sta
** Description changed:
I hope that the tilte is correct.
I have encrypted a sdcard using cryptsetup.
During the boot sequence, it does not ask for the password. I fail to find an
error message in the logs.
I think my config is ok because /etc/init.d/cryptdisks start does work:
* Sta
** Changed in: cryptsetup (Ubuntu Karmic)
Status: Triaged => In Progress
** Changed in: cryptsetup (Ubuntu Karmic)
Assignee: (unassigned) => Steve Langasek (vorlon)
--
cryptsetup starts too early
https://bugs.launchpad.net/bugs/454898
You received this bug notification because you ar
This bug was fixed in the package cryptsetup - 2:1.1.0~rc2-1ubuntu4
---
cryptsetup (2:1.1.0~rc2-1ubuntu4) lucid; urgency=low
[ Steve Langasek ]
* debian/initramfs/cryptroot-script: if plymouth is present in the
initramfs, use this directly, bypassing the cryptsetup askpass scr
** Branch linked: lp:~ubuntu-core-dev/cryptsetup/ubuntu
--
cryptsetup starts too early
https://bugs.launchpad.net/bugs/454898
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
** Changed in: cryptsetup (Ubuntu)
Status: Confirmed => Fix Committed
** Changed in: cryptsetup (Ubuntu)
Importance: Undecided => High
** Also affects: cryptsetup (Ubuntu Karmic)
Importance: Undecided
Status: New
** Also affects: cryptsetup (Ubuntu Lucid)
Importance: High
Still fully broken.
Unfortunately, I would have to understand how to tune the upstart
sequence to try to fix this...
Any comments?
> ** Changed in: cryptsetup (Ubuntu)
> Status: New => Confirmed
>
>
--
cryptsetup starts too early
https://bugs.launchpad.net/bugs/454898
You received this
** Changed in: cryptsetup (Ubuntu)
Status: New => Confirmed
--
cryptsetup starts too early
https://bugs.launchpad.net/bugs/454898
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.ubunt
> I confirm the problem on a EEE 901A.
> I use an encrypted SD card for my home folder, and even if /etc/crypttab is
> configured correctly I usually do not get a prompt at the splash screen.
> However, I said "usually": sometimes I DO get the prompt as it should be,
> typically when starting en
I confirm the problem on a EEE 901A.
I use an encrypted SD card for my home folder, and even if /etc/crypttab is
configured correctly I usually do not get a prompt at the splash screen.
However, I said "usually": sometimes I DO get the prompt as it should be,
typically when starting encrypted par
** Package changed: ubuntu => cryptsetup (Ubuntu)
--
cryptsetup starts too early
https://bugs.launchpad.net/bugs/454898
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://lis
23 matches
Mail list logo
