Antti Kaijanmäki: You sir, are my hero.
The python script did the trick, and now my external firewire drive
detects and asks for a password right away.
Thanks!
--
external harddrive (luks encrypted) will not mount automatically
https://bugs.launchpad.net/bugs/428435
You received this bug
OK. I now have a python program (attached) that I successfully used to make my
karmic upgrade bootable again.
The idea is to remove all additional signatures from superblock. Currently only
removing ext[234] signature is supported, but the program can be extended if
needed.
The idea is that
I was wrong on #18. I do not actually have any old jaunty menu entries
left, but I have 2.6.30-020630-generic which I installed for intel
drivers on jaunty. I just forgot about it and didn't look hard enough
last night.
http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.30/
Anyway this
After some research this is what I've found out; udev is responsible of
creating the entries under /dev/disks/by-uuid. Jaunty's udev (which is
also in the old initrd) uses udev's vol_id library to detect the FS
information. Karmic has new udev which has ditched vol_id and is using
blkid instead.
How about adding a VERY big warning to the release notes if this doesn't
get fixed before karmic is released? I too got bitten by this on
standard upgrade from jaunty to karmic and now karmic initramfs doesn't
find my encrypted LVM (root, swap) partition!
--
external harddrive (luks encrypted)
Hmm.. odd thing is that if I boot using old jaunty menu entry then the
partition is detected correctly...
--
external harddrive (luks encrypted) will not mount automatically
https://bugs.launchpad.net/bugs/428435
You received this bug notification because you are a member of Ubuntu
Bugs, which
Antti: Did you have this problem with a standard (automatic encryption
from alternate install CD) encrypted HDD or something else? Just
curious, since I'm running karmic without problems, and the installation
has been originally done from alternate CD with the automatic option. I
did however
Timo: I installed clean jaunty with standard alternate CD HDD
encryption. Jaunty ships with cryptsetup 1.0.6 and the problem which
causes this was fixed in 1.0.7
from the mailing list in comment #16:
cryptsetup 1.0.7 changelog:
- Wipe start of device (possible fs signature) before
I dont believe we can fix this in an automatic way for the users. The
best idea would be to document the dd command to clean the record and
put it on the wiki and reference it in release notes.
There is not a reliable way to detect what type of filesystem is on it
before cryptsetup 1.0.7, hence
This bug has been discussed at the mailing list of util-linux:
http://thread.gmane.org/gmane.linux.utilities.util-linux-
ng/2563/focus=2565
The problem here are devices which have been created with old versions
of cryptsetup, new versions wipe out the whole superblock data. At the
moment there is
Indeed the dk-disks data for /dev/sdb1 looks empty:
usage:
type:
version:
uuid:
For my encrypted USB stick it looks like
usage: crypto
type:crypto_LUKS
b...@buzz-laptop:~$ sudo blkid -c /dev/null /dev/sdb1
b...@buzz-laptop:~$
b...@buzz-laptop:~$ apt-cache policy cryptsetup
cryptsetup:
Installiert: 2:1.0.6+20090405.svn49-1ubuntu4
Kandidat: 2:1.0.6+20090405.svn49-1ubuntu4
Versions-Tabelle:
*** 2:1.0.6+20090405.svn49-1ubuntu4 0
500
Debugging the libblkid revealed that the probe functions detects two
filesystem magics on the device.
luks and ext4
as the blkid is set to be not tolerant it aborts the probe and sends a
null pointer. if i change blkid to be tolerant it works fine, it shows
me the password dialog and mounts the
buzz, thanks!
Would it be possible for you to get an image of the first 100 kB of data
of this partition? This will contain your encrypted LUKS password and
possibly some remainders of file system metadata from the old ext4, so
please don't do it if you have potentially sensitive data there. I
i would do the next steps private via email if thats fine for you?
--
external harddrive (luks encrypted) will not mount automatically
https://bugs.launchpad.net/bugs/428435
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
buzz [2009-10-12 13:46 -]:
i would do the next steps private via email if thats fine for you?
Sure, thanks!
Martin
--
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
--
external harddrive (luks encrypted)
Here is mine to help get this faster. Mine is a luks encrypted ext3
drive.
** Attachment added: ext3-luks.img
http://launchpadlibrarian.net/33496628/ext3-luks.img
** Changed in: util-linux (Ubuntu)
Status: Incomplete = Confirmed
--
external harddrive (luks encrypted) will not mount
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately I can't fix it without more information,
since I cannot reproduce the problem (it works fine for my encrypted USB
stick).
In Ubuntu 9.10 (Karmic) we have a new tool to debug storage related
problems.
As this bug also happens with my external harddrive i posted a new bug
report via the ubuntu-bug tool:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/448984
--
external harddrive (luks encrypted) will not mount automatically
https://bugs.launchpad.net/bugs/428435
You received this bug
I can also confirm on Karmic Beta 1 + updates.
** Changed in: devicekit-disks (Ubuntu)
Status: New = Confirmed
--
external harddrive (luks encrypted) will not mount automatically
https://bugs.launchpad.net/bugs/428435
You received this bug notification because you are a member of Ubuntu
I can confirm this situation with a new installed karmic version.
Unencrypted USB Stick mounts fine (except nautilus is not opening the
window), but encrypted external hard disc fails to prompt for a password
and is only mountable via terminal.
--
external harddrive (luks encrypted) will not
Just tested this today and it worked fine for me. However bug #430605
was also fixed overnight for me. Can you retest this and report whether
it is still an issue?
--
external harddrive (luks encrypted) will not mount automatically
https://bugs.launchpad.net/bugs/428435
You received this bug
It might be related to bug #430605 - also automount not happening,
though for different devices.
I think not because it affects encrypted devices only.
- CD: no problem
- usb stick: no problem
- same stick with encryped volume: not mounted
- encrypted external hard drive: not mounted
--
It might be related to bug #430605 - also automount not happening,
though for different devices.
--
external harddrive (luks encrypted) will not mount automatically
https://bugs.launchpad.net/bugs/428435
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Package changed: gvfs (Ubuntu) = devicekit-disks (Ubuntu)
--
external harddrive (luks encrypted) will not mount automatically
https://bugs.launchpad.net/bugs/428435
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/31721908/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/31721909/CurrentDmesg.txt
** Attachment added: DKDisksMonitorLog.txt
http://launchpadlibrarian.net/31721910/DKDisksMonitorLog.txt
26 matches
Mail list logo
