13.04 installation has damaged my luks partition

Bug #1169611 reported by Hugo Melo
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Invalid
High
Unassigned

Bug Description

Some days ago I've installed ubuntu 13.04 beta2 release on a clean partition I had.

I've chosen in the installer to not touch my home partition as it's encrypted and I doubted it would not understand that.

I chose the root partition and asked to encrypt my swap partition.

After installation I couldn't open my home partition any more. It keep saying:

  hugo@scare:~$ sudo cryptsetup luksOpen /dev/ubuntu/home home_crypt
Device /dev/ubuntu/home is not a valid LUKS device.

I don't know what the installer thought about my partition but I expected it to not touch that.
I am still trying to not go crazy about it but I didn't have the luks partition header on my backups and I have almost zero hope on recovering that. I just expect it to be fixed in a near future.

It seems ubuntu installer still has little support for lvm+luks partitions on installer.

Hugo Melo (hugo-melo)
tags: added: raring
Revision history for this message
Hugo Melo (hugo-melo) wrote :
Revision history for this message
Hugo Melo (hugo-melo) wrote :
Revision history for this message
Hugo Melo (hugo-melo) wrote :
Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1169611/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

tags: added: bot-comment
affects: ubuntu → ubiquity (Ubuntu)
Changed in ubiquity (Ubuntu):
importance: Undecided → High
Revision history for this message
Dimitri John Ledkov (xnox) wrote :

partman log is very verbose and it's not entirely clear to me what layout you had before the install, what install you have chosen and what happened afterwards.

Partman is showing two disks /dev/sda and /dev/sdb in the beginning.

What did you perform manual partitioning using "something else" option? Or did you select of the pre-defined options (resize, wipe & install, upgrade)? How did you encrypt swap?

Revision history for this message
Hugo Melo (hugo-melo) wrote :

Hi Dmitrijs,

I had a ubuntu 12.10 and I chose the image ubuntu-13.04-beta2-desktop-i386.iso.

I've used the unetbootin application for creating an installation media using my pendrive (that's the /dev/sdb).

The installation finished successfully and I am able to use raring without problems.

I've used the "something else" option and defined /dev/ubuntu/raring as my root partition and /dev/ubuntu/swap as my encrypted swap partition. Nothing more.
The encryption was taken using the installer. If I remember well, I had an option of using the partition as luks encrypted and it showed me an input for password (did not let me choose random passphrase).

After the installation was finished I asked it to restart. After restart, I noted it was not showing the text saying "please type the password for your swap encrypted partition. It just presented me the dark input and got stuck. I've switched the consoles and got the message asking the passphrase.

After boot, I was not able to luksOpen my home partition anymore. It's still untouched.

Revision history for this message
Dimitri John Ledkov (xnox) wrote :

@hugo-melo

Thank you for those details. And how was ubuntu 12.10 installed? Using manual partitioning as well? How were those partitions arranged?

Regards,

Dmitrijs.

Revision history for this message
Hugo Melo (hugo-melo) wrote :

@xnox

Here's a fdisk output.
The configuration is the same as before Raring.
On sda5, there's a LVM partition which can be analysed on the first attachments of this bug (vgdisplay and lvdisplay).
The only difference is that I didn't have /dev/ubuntu/raring. The /dev/ubuntu/root partition had 30GB and I decreased it's size to create raring. The /dev/ubuntu/root partition has 12.10 still working.

Thanks for taking time to work on this.

Revision history for this message
Dimitri John Ledkov (xnox) wrote :

@hugo-melo

I'm still slightly confused on how it was before and how it is now.
Can you give the output of:
sudo lvs

?

Revision history for this message
Hugo Melo (hugo-melo) wrote :

@xnox

Sorry, I will try to explain better:

Before the installation I had something like this:

 home ubuntu -wi-a--- 664.00g
  root ubuntu -wi-ao-- 30.59g
  swap_1 ubuntu -wi-a--- 3.80g

Using the 13.10 live media I changed the above configuration to:
  home ubuntu -wi-a--- 664.00g
  raring ubuntu -wi-a--- 10.59g
  root ubuntu -wi-ao-- 20.00g
  swap_1 ubuntu -wi-a--- 3.80g

After that, I started ubiquity and asked to install.

Revision history for this message
Dimitri John Ledkov (xnox) wrote :

right, i see what you mean now. Yeah, that should not have done anything to "home". I hope you marked "home" volume to "don't use" while installing raring?! because at the moment installer cannot activate dm-crypt and thus selecting "home" volume for anything could have damaged it.

Revision history for this message
Hugo Melo (hugo-melo) wrote :

Yes, I did select "do not use the partition" option.

The question to me is: why the format of my home partition is not being recognized?
If ubiquity got confused and tried to format my luks partition with something else it would be possible to mount that.

Revision history for this message
Phillip Susi (psusi) wrote :

According to the logs, you formatted that volume with an ext2 filesystem. You must have made a mistake.

Changed in ubiquity (Ubuntu):
status: New → Invalid
Revision history for this message
Hugo Melo (hugo-melo) wrote :

@psusi

Shouldn't it mount as ext2 so?
Look below..

╭─hugo@scare ~
╰─➤ sudo mount /dev/ubuntu/home /mnt
[sudo] password for hugo:
mount: you must specify the filesystem type

And I didn't ask it to format..
I am not so crazy.

Revision history for this message
Phillip Susi (psusi) wrote :

Try sudo mount -t ext2 /dev/ubuntu/home /mnt

Revision history for this message
Phillip Susi (psusi) wrote :

Actually, now that I look again, it appears you created a partition to hold an ext2 filesystem, without formatting that partition, so it just changed the first sector.

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.