luks header of newly created partition not written to disk, on reboot partition "unrecognised"

Bug #520442 reported by Wolfgang Kufner
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
gnome-disk-utility (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Binary package hint: gnome-disk-utility

I have now managed to produce an unusable luks partition 4 times. 2 times with the mint rc (karmic based) loopback mounted from hd via grub2 and now 2 times with lucid 20100210 64 bit daily iso loopback mounted from a usb stick via grub2 on a different notebook.

Here is how:
use gparted to make space by making the main partition shorter. I made empty space of about 10GB at the end of the disk.
use palimpsest to put an encrypted partition in this newly created empty space. tried with both ext4 and ext3. used default options.
the filesystem is created and can be mounted. put stuff in. unmount. shut down.
on reboot there is no luks partition anymore: gparted says "unknown" and palimpsest says "unrecognised"
sudo most /dev/sdax shows that partition has no luks header. a lot of zeros at the beginning instead.

when using palimpsest in the same manner on this faulty partition again to overwrite it with another encrypted partition all worked well.

description: updated
Revision history for this message
Saverio Miroddi (64kramsystem) wrote :

Affects me as well. I tried several times to create a second partition, encrypted, on a USB key, and after I eject the key and plug it back in, Ubuntu doesn't recognize it.
As a workaround, if I overwrite the faulty partition with a second one (without freeing the space first), it works fine.

Changed in gnome-disk-utility (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.