© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
73416ba
(Get the code!)
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 I first submitted the bug report (and from what I have observed on many other attempts). Nonetheless, the effect is the same: Installation does not proceed.
Note that, as can be seen in the attached screen shot, the mke2fs process wasn't running just after the installation failed.
You ask why I think that this bug isn't a duplicate of Bug #1361951. I acknowledge that this bug may be related to that bug. And indeed, the bug that I am reporting may very well be a manifestation of whatever error gives rise to that bug. But as far as being a "duplicate" of that bug, I don't think so. For one reason, as I mentioned above, the mke2fs process wasn't running just after the installation failed. But beyond that, the issues reported in Bug #1361951 seems to be hardware dependent, and in many cases aren't reproducible. In contrast, as I mentioned in Comment #64 of Bug #1361951, the bug that I am reporting "is reproducible 100% of the time on every computer that I own as well as on virtualbox and QEMU/KVM." In any case, I don't want to mark this bug as a duplicate until we know more.
Also, in addition to preventing a clean installation of /home into separate LUKS encrypted volume, I have noticed that I am unable to upgrade from a working (non-broken) installation of Ubuntu 15.04 in which /home has been previously installed into separate LUKS encrypted volume.
I hope that the above is of some help.
Best regards,
GizmoChicken