This bug has been reported on the Ubuntu ISO testing tracker.
A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1523194
** Tags added: iso-testing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Tags added: ce-qa-concern disco
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1523194
Title:
Can't install /home into separate LUKS encrypted volume
To manage notifications about this bug go
Just as a follow-up, if I use the following partitioning, the
installation completes:
/dev/sda:
- EFI partition: 128 MB
- unencrypted root (/) formatted in ext4: 31 GB
/dev/sdb:
- encrypted volume hosting home partition (/home) formatted in ext4: 500 GB
(basically, only /home on the HDD is
I'm facing a similar (if not the same) issue.
My laptop has the following hardware:
- 500 GB HDD (TOSHIBA MQ01ACF050 (AV002D)) (/dev/sda)
- 32 GB SSD (LITEON LST-32S9G-11 SATA 32GB (ZS2110B)) (/dev/sdb)
I'm trying to install Ubuntu 19.04 on it as follow, using disk
encryption:
/dev/sda:
- EFI
Trust me, I have identified the whole of the problem after enabling full
trace of the relevant scripts and going through the logs with a fine
tooth comb. The bug is not *in* Ubiquity therefore it is incorrect to
leave it tasked there. The Ubiquity developers do not need to know
about it as they
Phillip,
You've identified part of the problem. And I thank you for that. But
I'm not convinced that you have identified the whole problem. In
addition to assigning the bug to partman-crypto, please leave the bug
assigned to ubiquity so that others can find the bug and provide
additional
The bug isn't in ubiquity, which is why I reassigned it.
** No longer affects: ubiquity (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1523194
Title:
Can't install /home into separate
** Also affects: ubiquity (Ubuntu)
Importance: Undecided
Status: New
** Changed in: ubiquity (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1523194
** Package changed: ubiquity (Ubuntu) => partman-crypto (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1523194
Title:
Can't install /home into separate LUKS encrypted volume
To manage
No, I don't work for Canonical. I was able to reproduce this and it
looks like the problem is that only one of the two volumes is being
formatted and the other has no filesystem in it. I'll try to do some
tracing and see where it is going wrong but it certainly looks like a
bug in one of the
Bingo!
/lib/partman/init.d/52crypto: IN: NEW_LABEL =dev=mapper=xvda5_crypt loop
parted_server: Read command: NEW_LABEL
parted_server: command_new_label()
parted_server: Note =dev=mapper=xvda5_crypt as changed
parted_server: Opening outfifo
parted_server: command_new_label: requested label with
Phillip,
When I originally reported the bag back on 2015-12-06, the installer
did, in fact, hang during installation when the following was displayed:
“Creating ext4 system for /home in partition #1 of Encrypted volume
(sda3_crypt)...”
But as I wrote in Comment #9, the screen shot uploaded with
** Changed in: ubiquity (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1523194
Title:
Can't install /home into separate LUKS encrypted volume
To manage
Ahh, it also shows that contrary to what you said before, the install
did not hang during "creating ext4 system..." but has popped up an error
dialog saying it was unable to mount the volume. Please attach
/var/log/syslog once this has happened.
** Changed in: ubiquity (Ubuntu)
Status:
Phillip,
I tried to install the most current daily build (2016-01-28) of Ubuntu
16.04 into /home into separate LUKS encrypted volume, this time using
QEMU/KVM. The attached screen shot was taken just after the
installation failed. On this attempt, the error differs somewhat what I
observed when
** Changed in: ubiquity (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1523194
Title:
Can't install /home into separate LUKS encrypted volume
To
Why do you think this is not a duplicate of #1361951? When it is hung,
can you check with ps or the task manager to see if you have the mke2fs
process running? If so, run sudo gdb -p and at the
prompt, give it a "bt" command and post its output.
** Changed in: ubiquity (Ubuntu)
Status:
Please:
1. Into the tag list, write down the first name of each release where you are
seeing this bug.
2. Set this bug status back to "confirmed".
Thank you.
** Changed in: ubiquity (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member
I started report at Bug #1531387 to expand on comment #1 above.
I don't know what, if any, relation Bug #1531387 has to the current bug,
but here's a summary of Bug #1531387:
1) Installing root (/) into an Ext4 formatted LUKS partition creates
/dev/dm-0, rather than /dev/mapper/sdaX_crypt.
2)
** Tags added: wily
** Tags added: xenial
** Changed in: ubiquity (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1523194
Title:
Can't install /home
** Changed in: ubiquity (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1523194
Title:
Can't install /home into separate LUKS encrypted volume
To manage
This bug may also be related to Bug #1361951 related to mke2fs.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1523194
Title:
Can't install /home into separate LUKS encrypted volume
To manage
** This bug is no longer a duplicate of bug 1361951
mke2fs asks for input when formatting over a partition table
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1523194
Title:
Can't install /home
*** This bug is a duplicate of bug 1361951 ***
https://bugs.launchpad.net/bugs/1361951
** This bug has been marked a duplicate of bug 1361951
mke2fs asks for input when formatting over a partition table
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
This bug may also be related to Bug #1531387.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1523194
Title:
Can't install /home into separate LUKS encrypted volume
To manage notifications about
Although perhaps not a "duplicate" of Bug #1509877 (assessed to be a
"critical" bug for Lubuntu), this bug and that bug at least seem to be
related. See
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1509877
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ubiquity (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1523194
Title:
I'll just add that, as a workaround, I installed Ubuntu only into boot
(/boot) and root (/). I then booted into the installed Ubuntu and
created a new auto-mountable LUKS-encrypted volume formatted with Ext4,
to which I moved my home directory.
The above approach works, but for some reason,
28 matches
Mail list logo
