U1604-2016-02-03.png is a screenshot showing sysmon running on a system
installed using the U1604 daily build from 2016-02-03.
** Attachment added: "U1604-2016-02-03.png"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1531387/+attachment/4583143/+files/U1604-2016-02-03.png
**
U1604-2016-02-26.png is a screenshot showing sysmon running on a system
installed using the U1604 daily build from 2016-02-26.
** Attachment added: "U1604-2016-02-26.png"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1531387/+attachment/4583142/+files/U1604-2016-02-26.png
**
Looks like this bug/inconsistency has been fixed, at least for the time
being.
Just to clarify my previous observation…
Prior to the fix, when installing root (/) into an Ext4 formatted LUKS
partition, the system recognized the LUKS device as /dev/dm-0, rather
than as /dev/mapper/sdaX_crypt.
Sure -- that's what incomplete is for: waiting for more information.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1531387
Title:
U1604: Installing root (/) into an Ext4 formatted LUKS partition
I'm not able to reproduce this. I've tried installing with both ext4
and btrfs and in both cases I get /dev/mapper/xvda_crypt as a symlink to
/dev/dm-0, which is the actual block device. Can you provide more
details?
** Changed in: ubiquity (Ubuntu)
Status: Confirmed => Incomplete
--
Phillip,
Thanks much for the comment. Also, thanks for you involvement in Bug
#1523194. I originally reported the current bug/observation because I
thought maybe it was related to Bug #1523194, which at least for me, is
a fairly important bug. Now, I doubt that there is a relationship, and
so
As I said before, both should be created. The /dev/mapper one is the
one you should normally use, but /dev/dm-x also should exist.
** Changed in: ubiquity (Ubuntu)
Importance: High => Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Tags added: wily xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1531387
Title:
U1604: Installing root (/) into an Ext4 formatted LUKS partition
creates /dev/dm-0, rather than
** 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/1531387
Title:
U1604: Installing root (/) into an Ext4 formatted LUKS partition
** 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/1531387
Title:
U1604: Installing root (/) into an Ext4 formatted LUKS partition
Both files should be created with one being a symbolic link to the
other. What is the actual problem that you experience? Does the
install not boot?
** Changed in: ubiquity (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of
It boots. And like I said, I'm not sure if this constitutes a full bug.
But it certainly is an inconsistency.
That is:
1) Installing root (/) into an Ext4 formatted LUKS partition creates
/dev/dm-0, rather than /dev/mapper/sdaX_crypt.
2) Installing root (/) into a Btrfs formatted LUKS
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/1531387
Title:
13 matches
Mail list logo
