[Bug 386976] Re: [Jaunty] early crypto disk keyfile on usb not found
Jean-Louis Dupond
jean-louis at dupond.be
Thu Mar 8 14:13:24 UTC 2012
Thank you for reporting this bug to Ubuntu. Jaunty reached EOL on October 23, 2010.
Please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
I've tried recreating this bug with RELEASE and was unable to, given the
information you've provided. Please either a) upgrade and test or b)
increase the verbosity of the steps to recreate it so we can try again.
Please feel free to report any other bugs you may find.
** Changed in: cryptsetup (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to cryptsetup in Ubuntu.
https://bugs.launchpad.net/bugs/386976
Title:
[Jaunty] early crypto disk keyfile on usb not found
Status in “cryptsetup” package in Ubuntu:
Invalid
Bug description:
Description: Ubuntu 9.04 Release: 9.04
cryptsetup 2:1.0.6-7ubuntu7
Linux ubuntuServer 2.6.28-11-server #42-Ubuntu SMP Fri Apr 17 02:45:36 UTC 2009 x86_64 GNU/Linux
After upgrading from intrepid my keyfile on my external usbstick is
not found anymore so my partitions are not mounted
During boot i receive now:
early crypto disk
mount: special device
/dev/sdc does not exist
keyfile not found
In order to boot correctly I had to change in the safe mode /etc/crypttab
from
var /dev/sdb5 /media/flash/var.key luks,tries=1,timeout=10
to
var /dev/sdb5 /media/var.key luks,tries=1,timeout=10 ( where i copied temporarily my keyfile )
Interestingly when i boot into my desktop and issue df -h i can see and access my usbstick
/dev/sdc 63M 15M 48M 24% /media/flash
so it seems it is only a problem with an early mount of my usbstick
My /etc/fstab
/dev/mapper/var /var ext3 relatime,errors=remount-ro 0 0
/dev/sdc /media/flash vfat uid=0,gid=0,umask=277 0 0
In my /etc/default/cryptdisks I have this line:
CRYPTDISKS_MOUNT="/media/flash"
I also did type update-initramfs -u , but it did not change anything
When the restart failed after the upgrade I still had in the grub list
a intrepid kernel (I dont remember which one) that i tried to boot
with. And the drives where mounted and decrypted correctly although my
ati drivers where not working correctly anymore of course that is a
another story. My point is that I believe my configuration is correct
and the issue seems to be related to my current kernel
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/386976/+subscriptions
More information about the foundations-bugs
mailing list