This bug was fixed in the package grub2 - 2.04-1ubuntu4
---
grub2 (2.04-1ubuntu4) eoan; urgency=medium
* d/patches/ubuntu-boot-from-multipath-dependent-symlink.patch: when / is
multipathed there will be multiple paths to the partition, so using
root=UUID= exposes the boot
** Changed in: grub2 (Ubuntu)
Assignee: (unassigned) => Michael Hudson-Doyle (mwhudson)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1429327
Title:
Boot from a unique, stable,
I had a stab at this
https://code.launchpad.net/~mwhudson/ubuntu/+source/grub2/+git/grub2/+merge/370896
-- all comments welcome! (my brain now hurts)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Merge proposal linked:
https://code.launchpad.net/~mwhudson/ubuntu/+source/grub2/+git/grub2/+merge/370896
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1429327
Title:
Boot from a unique,
** Tags added: id-5c00556f000dd8799c9361aa
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1429327
Title:
Boot from a unique, stable, multipath-dependent symlink
To manage notifications about this
Scott was right when he wrote:
> It seems there is a grub component of this bug also, to make grub
> correctly identify the 'abstraction' of multipath and auomatically
> set GRUB_DEVICE=/dev/disk/by-uuid/multipath-UUID rather than
> UUID=
I understand that curtin has been working around grub's
** Also affects: grub2 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1429327
Title:
Boot from a unique, stable, multipath-dependent symlink
To
** Description changed:
-- Problem Description --
- We try to install Ubuntu version 15.04 build 20150218 on our system which use
the ibmveth for the network and bluefin (lpfc) for this disks.
+ We try to install Ubuntu version 15.04 build 20150218 on our system which use
the ibmveth for the
** Description changed:
-- Problem Description --
- We try to install Ubuntu version 15.04 build 20150218 on our system which use
the ibmveth for the network and bluefin (lpfc) for this disks.
+ We try to install Ubuntu version 15.04 build 20150218 on our system which use
the ibmveth for the
** Summary changed:
- Boot from an unique, stable, multipath-dependent symlink
+ Boot from a unique, stable, multipath-dependent symlink
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
** Summary changed:
- Boot from an unique, stable, multipath-dependent symlink
+ Boot from a unique, stable, multipath-dependent symlink
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1429327
Title:
To rule that out, I wondered about using /root/by-id/multipath-uuid-uuid,
for example -- or anything that doesn't mean anything more than a symlink,
that could hit the UUID interpretation bug I suspected.
Yes; I don't think we should be overloading the behavior of UUID= since
that is meant to
To rule that out, I wondered about using /root/by-id/multipath-uuid-uuid,
for example -- or anything that doesn't mean anything more than a symlink,
that could hit the UUID interpretation bug I suspected.
Yes; I don't think we should be overloading the behavior of UUID= since
that is meant to
@smoser
Yeah, its been fun.
Hahah, I do understand the quotes.
Well, it's the way that turned out to be more fruitful to put it. :)
Well, I'm not positive the change to root=UUID=multipath- (done via ROOT=)
would be well accepted by boot userspace,
I'm not sure what you mean by
@smoser
Yeah, its been fun.
Hahah, I do understand the quotes.
Well, it's the way that turned out to be more fruitful to put it. :)
Well, I'm not positive the change to root=UUID=multipath- (done via ROOT=)
would be well accepted by boot userspace,
I'm not sure what you mean by
Hi Scott,
I believe that your re-setting of ROOT= guarantees failure of boot if you
install multipath-tools-boot on a system that does not have multipath.
Good to see more opinions on the this topic.
Well, I'm not positive the change to root=UUID=multipath- (done via ROOT=)
would be well
Hi Scott,
I believe that your re-setting of ROOT= guarantees failure of boot if you
install multipath-tools-boot on a system that does not have multipath.
Good to see more opinions on the this topic.
Well, I'm not positive the change to root=UUID=multipath- (done via ROOT=)
would be well
another comment, the path that i was pursuing, and almost have in place
was to have /etc/multipath/bindings with consitent names and then boot
with root=/dev/mappings/mpathX[-partY].
Mauricio's suggestion of boting with root=multipath-UUID is nicer in the
event of a disk being replaced. As my
another comment, the path that i was pursuing, and almost have in place
was to have /etc/multipath/bindings with consitent names and then boot
with root=/dev/mappings/mpathX[-partY].
Mauricio's suggestion of boting with root=multipath-UUID is nicer in the
event of a disk being replaced. As my
Yeah, its been fun.
I'm not sure what you mean by accepted. as in accepted upstream or
as in the initramfs would respect your change to ROOT. initramfs will
respect your change to root. Your path *will* work, but will break
anyone that doesn't have their root device on multipath.
For curtin,
Yeah, its been fun.
I'm not sure what you mean by accepted. as in accepted upstream or
as in the initramfs would respect your change to ROOT. initramfs will
respect your change to root. Your path *will* work, but will break
anyone that doesn't have their root device on multipath.
For curtin,
I'm working on curtin support for multipath, and after a very long set
of things, I believe I'm down to this bug, and are seeing it
reproducibly using trusty+hwe-v on ppc64el (note, I've never seen it in
trusty+hwe-u).
I believe that your re-setting of ROOT= guarantees failure of boot if
you
well, i lied. I've seen it on hwe-u also now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1429327
Title:
Boot from an unique, stable, multipath-dependent symlink
To manage notifications about
well, i lied. I've seen it on hwe-u also now.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1429327
Title:
Boot from an unique, stable, multipath-dependent symlink
To
I'm working on curtin support for multipath, and after a very long set
of things, I believe I'm down to this bug, and are seeing it
reproducibly using trusty+hwe-v on ppc64el (note, I've never seen it in
trusty+hwe-u).
I believe that your re-setting of ROOT= guarantees failure of boot if
you
It seems there is a grub component of this bug also, to make grub
correctly identify the 'abstraction' of multipath and auomatically set
GRUB_DEVICE=/dev/disk/by-uuid/multipath-UUID rather than UUID=
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
It seems there is a grub component of this bug also, to make grub
correctly identify the 'abstraction' of multipath and auomatically set
GRUB_DEVICE=/dev/disk/by-uuid/multipath-UUID rather than UUID=
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Patch added: partman-multipath_uuid-multipath.debdiff
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1429327/+attachment/4396257/+files/partman-multipath_uuid-multipath.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Patch added: partman-multipath_uuid-multipath.debdiff
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1429327/+attachment/4396257/+files/partman-multipath_uuid-multipath.debdiff
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Hi Mathieu,
(I have no idea what the 3 attachments above are related to. :-)
This is the patch missing for the installer.
I did some testing and noticed some problems w/ it, which made me to reconsider
how/if we should really make this based on an UUID= field. Let me describe the
issue.
IIRC,
Hi Mathieu,
(I have no idea what the 3 attachments above are related to. :-)
This is the patch missing for the installer.
I did some testing and noticed some problems w/ it, which made me to reconsider
how/if we should really make this based on an UUID= field. Let me describe the
issue.
IIRC,
Now that the vivid release is done, let's revisit these patches. I'll do
some testing on my end, but looking briefly at them, they make sense.
What other installer changes (since you mention them in your comment
#20) are necessary?
** Changed in: multipath-tools (Ubuntu)
Status: Confirmed
Now that the vivid release is done, let's revisit these patches. I'll do
some testing on my end, but looking briefly at them, they make sense.
What other installer changes (since you mention them in your comment
#20) are necessary?
** Changed in: multipath-tools (Ubuntu)
Status: Confirmed
33 matches
Mail list logo
