[Bug 1371634] Re: block devices appear twice [install does not use multipath]
This bug is believed to be fixed in curtin in 17.1. If this is still a problem for you, please make a comment and set the state back to New Thank you. ** Changed in: curtin Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1371634 Title: block devices appear twice [install does not use multipath] To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1371634/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1371634] Re: block devices appear twice [install does not use multipath]
This bug was fixed in the package curtin - 0.1.0~bzr221-0ubuntu1~14.10.1 --- curtin (0.1.0~bzr221-0ubuntu1~14.10.1) vivid-proposed; urgency=medium * New upstream snapshot. - support installation to multipath devices. (LP: #1371634) - know that kernel version 4.2.0 maps to linux-generic-lts-wily - support install to arm64 systems that use UEFI for boot (LP: #1447834) - fix remaining usage of 'lsblk --out' rather than 'lsblk --output' (LP: #1386275) - retry 'apt-get update' on failure to avoid transient failures (LP: #1403133) - run udevadm settle before unmounting /dev in a target to avoid transient failures (LP: #1462139) - fixes and additions to tools used in development. - Add --no-nvram to the grub-install command for UEFI. (LP: #1311827) - avoid race condition and transient failure due busy device in mkfs (LP: #1443542) - improvements to device and partition naming code which allow installation devices with HP cciss smart array drives(LP: #1401190, #1263181) - do not consider devices 1G as installable targets * debian/README.source fix doc on how to create new upstream snapshots -- Scott Moser smo...@ubuntu.com Wed, 24 Jun 2015 16:12:59 -0400 ** Changed in: curtin (Ubuntu Vivid) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1371634 Title: block devices appear twice [install does not use multipath] To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1371634/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1371634] Re: block devices appear twice [install does not use multipath]
This bug was fixed in the package curtin - 0.1.0~bzr221-0ubuntu1~14.04.1 --- curtin (0.1.0~bzr221-0ubuntu1~14.04.1) trusty-proposed; urgency=medium * New upstream snapshot. - support installation to multipath devices. (LP: #1371634) - know that kernel version 4.2.0 maps to linux-generic-lts-wily - support install to arm64 systems that use UEFI for boot (LP: #1447834) - fix remaining usage of 'lsblk --out' rather than 'lsblk --output' (LP: #1386275) - retry 'apt-get update' on failure to avoid transient failures (LP: #1403133) - run udevadm settle before unmounting /dev in a target to avoid transient failures (LP: #1462139) - fixes and additions to tools used in development. - Add --no-nvram to the grub-install command for UEFI. (LP: #1311827) - avoid race condition and transient failure due busy device in mkfs (LP: #1443542) - improvements to device and partition naming code which allow installation devices with HP cciss smart array drives(LP: #1401190, #1263181) - do not consider devices 1G as installable targets * debian/README.source fix doc on how to create new upstream snapshots -- Scott Moser smo...@ubuntu.com Wed, 24 Jun 2015 14:31:14 -0400 ** Changed in: curtin (Ubuntu Trusty) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to curtin in Ubuntu. https://bugs.launchpad.net/bugs/1371634 Title: block devices appear twice [install does not use multipath] To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1371634/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1371634] Re: block devices appear twice [install does not use multipath]
This bug was fixed in the package curtin - 0.1.0~bzr221-0ubuntu1~14.04.1 --- curtin (0.1.0~bzr221-0ubuntu1~14.04.1) trusty-proposed; urgency=medium * New upstream snapshot. - support installation to multipath devices. (LP: #1371634) - know that kernel version 4.2.0 maps to linux-generic-lts-wily - support install to arm64 systems that use UEFI for boot (LP: #1447834) - fix remaining usage of 'lsblk --out' rather than 'lsblk --output' (LP: #1386275) - retry 'apt-get update' on failure to avoid transient failures (LP: #1403133) - run udevadm settle before unmounting /dev in a target to avoid transient failures (LP: #1462139) - fixes and additions to tools used in development. - Add --no-nvram to the grub-install command for UEFI. (LP: #1311827) - avoid race condition and transient failure due busy device in mkfs (LP: #1443542) - improvements to device and partition naming code which allow installation devices with HP cciss smart array drives(LP: #1401190, #1263181) - do not consider devices 1G as installable targets * debian/README.source fix doc on how to create new upstream snapshots -- Scott Moser smo...@ubuntu.com Wed, 24 Jun 2015 14:31:14 -0400 ** Changed in: curtin (Ubuntu Trusty) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1371634 Title: block devices appear twice [install does not use multipath] To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1371634/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1371634] Re: block devices appear twice [install does not use multipath]
This bug was fixed in the package curtin - 0.1.0~bzr221-0ubuntu1~14.10.1 --- curtin (0.1.0~bzr221-0ubuntu1~14.10.1) vivid-proposed; urgency=medium * New upstream snapshot. - support installation to multipath devices. (LP: #1371634) - know that kernel version 4.2.0 maps to linux-generic-lts-wily - support install to arm64 systems that use UEFI for boot (LP: #1447834) - fix remaining usage of 'lsblk --out' rather than 'lsblk --output' (LP: #1386275) - retry 'apt-get update' on failure to avoid transient failures (LP: #1403133) - run udevadm settle before unmounting /dev in a target to avoid transient failures (LP: #1462139) - fixes and additions to tools used in development. - Add --no-nvram to the grub-install command for UEFI. (LP: #1311827) - avoid race condition and transient failure due busy device in mkfs (LP: #1443542) - improvements to device and partition naming code which allow installation devices with HP cciss smart array drives(LP: #1401190, #1263181) - do not consider devices 1G as installable targets * debian/README.source fix doc on how to create new upstream snapshots -- Scott Moser smo...@ubuntu.com Wed, 24 Jun 2015 16:12:59 -0400 ** Changed in: curtin (Ubuntu Vivid) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to curtin in Ubuntu. https://bugs.launchpad.net/bugs/1371634 Title: block devices appear twice [install does not use multipath] To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1371634/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1371634] Re: block devices appear twice [install does not use multipath]
I've tested curtin installations on both multipath systems and non-multipath systems. marking this as verfication-done. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1371634 Title: block devices appear twice [install does not use multipath] To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1371634/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1371634] Re: block devices appear twice [install does not use multipath]
I've tested curtin installations on both multipath systems and non-multipath systems. marking this as verfication-done. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to curtin in Ubuntu. https://bugs.launchpad.net/bugs/1371634 Title: block devices appear twice [install does not use multipath] To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1371634/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1371634] Re: block devices appear twice [install does not use multipath]
Hello Scott, or anyone else affected, Accepted curtin into vivid-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/curtin/0.1.0~bzr221-0ubuntu1~14.10.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: curtin (Ubuntu Vivid) Status: Confirmed = Fix Committed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to curtin in Ubuntu. https://bugs.launchpad.net/bugs/1371634 Title: block devices appear twice [install does not use multipath] To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1371634/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1371634] Re: block devices appear twice [install does not use multipath]
** Branch linked: lp:ubuntu/vivid-proposed/curtin -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1371634 Title: block devices appear twice [install does not use multipath] To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1371634/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1371634] Re: block devices appear twice [install does not use multipath]
** Branch linked: lp:ubuntu/trusty-proposed/curtin -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to curtin in Ubuntu. https://bugs.launchpad.net/bugs/1371634 Title: block devices appear twice [install does not use multipath] To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1371634/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1371634] Re: block devices appear twice [install does not use multipath]
Hello Scott, or anyone else affected, Accepted curtin into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/curtin/0.1.0~bzr221-0ubuntu1~14.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: curtin (Ubuntu Trusty) Status: Confirmed = Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to curtin in Ubuntu. https://bugs.launchpad.net/bugs/1371634 Title: block devices appear twice [install does not use multipath] To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1371634/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1371634] Re: block devices appear twice [install does not use multipath]
** Branch linked: lp:ubuntu/trusty-proposed/curtin -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1371634 Title: block devices appear twice [install does not use multipath] To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1371634/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1371634] Re: block devices appear twice [install does not use multipath]
Hello Scott, or anyone else affected, Accepted curtin into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/curtin/0.1.0~bzr221-0ubuntu1~14.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: curtin (Ubuntu Trusty) Status: Confirmed = Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1371634 Title: block devices appear twice [install does not use multipath] To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1371634/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1371634] Re: block devices appear twice [install does not use multipath]
** Branch linked: lp:ubuntu/vivid-proposed/curtin -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to curtin in Ubuntu. https://bugs.launchpad.net/bugs/1371634 Title: block devices appear twice [install does not use multipath] To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1371634/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1371634] Re: block devices appear twice [install does not use multipath]
Hello Scott, or anyone else affected, Accepted curtin into vivid-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/curtin/0.1.0~bzr221-0ubuntu1~14.10.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: curtin (Ubuntu Vivid) Status: Confirmed = Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1371634 Title: block devices appear twice [install does not use multipath] To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1371634/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1371634] Re: block devices appear twice [install does not use multipath]
** Branch linked: lp:ubuntu/wily-proposed/curtin -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1371634 Title: block devices appear twice [install does not use multipath] To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1371634/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1371634] Re: block devices appear twice [install does not use multipath]
** Branch linked: lp:ubuntu/wily-proposed/curtin -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to curtin in Ubuntu. https://bugs.launchpad.net/bugs/1371634 Title: block devices appear twice [install does not use multipath] To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1371634/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1371634] Re: block devices appear twice [install does not use multipath]
** Description changed: + === Begin SRU Information === + [Description] + When curtin installs to a system that has multipath devices, it does not recognize this and enable them. + The result is that a system that has multipath devices installed will have Ubuntu installed to one of the non-multipath paths. The end user is then confused because they see root installed on /dev/sda1 and another device /dev/sdg1 (or other name) that has the same content as /dev/sda1. In addition to this confusion, if the user decides to use /dev/sdg1 and format it, they'll have shot themselves in the foot by destroying their root partition. + + The general solution is to install multipath-tools-boot when the system is detected to have multipath devices. To do this, curtin does: + curtin currently does: + a.) installs multipath-boot *only* when multipath devices are found, avoiding bug 1463046. + b.) writes /etc/multipath.conf to use user_friendly_names, avoiding bug 1432062. + c.) writes /etc/multipath/bindings file to provide a consistent named /dev/mapper/mpath name (solving bug 1429327) + + [Impact] + Without this fix, most power 8 systems will install to /dev/sda1 and let the user modify /dev/sdg1 (or whatever device name that multipath device appears as). This is not very user friendly, and quite confusing. + + [Test Case] + Positive case: + a.) install system that has multipath + b.) verify that multipath-tools-boot is installed. + c.) verify that system is booted with root=/dev/mapper/mpath0-part2 + + Negative case: + a.) install system with 2 disks without multipath + b.) verify that no multipath-tools-boot is installed. + + [Regression Potential] + The regression potential falls into 2 places: + a.) a system with multipath that installed without multipath fails to install or work after this + this is really a bug in multipath in kenrel or the package if we get here. We've done fairly significant testing to show that we're reliably installing. + + b.) a system without multipath is identified as multipath + The detection of multipath basically consists of looking for 2 devices that have a filesystem with the same UUID on them after creating a filesystem with that UUID. This is essentially not more than a check for a random sequence of bytes on all disks rather than a fully determinable identification of multipath. So, the failure case is: + 1.) we install to system and 'mkfs' the root partition + 2.) we find 2 disks that have the same UUID as the root device (the root device and one other) + In all likelyhood, that would mean that a filesytem with this UUID already existed on the system. That seems quite unlikley. + + In the event that the user does not have multipath systems and just wants to disable multipath to avoid that scenario, they can do so by config in maas setting the following in /etc/maas/preseeds/curtin_userdata will disable multipath and boot quite reliably without multipath. + multipath: + mode: false + + [Other] + Related bugs: + * bug 1432062 : multipath-tools-boot: support booting without user_friendly_names on devices with spaces in identifiers + * bug 1463043 : some SM15K systems fail to boot after deployment - drop into initramfs shell + * bug 1462530 : multipath errors on vivid, wily kernel + * bug 1463046 : installation of multipath-tools-boot can break boot + * bug 1447167 : [d-i] multipath-install: Installing with multipath enabled does not install multipath-tools + * bug 1429327 : Boot from an unique, stable, multipath-dependent symlink + + === End SRU Information === + + === Original bug report === $ sudo blkid /dev/sr0: LABEL=Ubuntu-Server 14.04 LTS ppc64el TYPE=iso9660 /dev/sda2: UUID=795a6e14-ea4e-4718-9e98-c6df3696920c TYPE=ext4 /dev/sda3: UUID=0a91d81f-6a16-4b96-a92c-11ca8bdc4bf4 TYPE=swap /dev/sdb2: UUID=1d14c1f3-716f-4fb8-9070-d321b39ffcb3 TYPE=ext4 /dev/sdb3: UUID=9c228177-d65c-4d19-a462-db1891e9781e TYPE=swap /dev/sdg2: UUID=795a6e14-ea4e-4718-9e98-c6df3696920c TYPE=ext4 /dev/sdg3: UUID=0a91d81f-6a16-4b96-a92c-11ca8bdc4bf4 TYPE=swap /dev/sdh2: UUID=1d14c1f3-716f-4fb8-9070-d321b39ffcb3 TYPE=ext4 /dev/sdh3: UUID=9c228177-d65c-4d19-a462-db1891e9781e TYPE=swap I'm not sure what exactly those block devices are (as in if they're raided in hardware or they actually represent physical spinning disks). But I do know that writing data to sda causes that data to be readable from sdg. The same is true: sda - sdg sdb - sdh That is what causes those UUIDs to be similar. Everything is functional, you just have to know that if your root device is /dev/sdg that you should probably not write data to /dev/sda thinking you can use it as a disk. - - Related bugs: - * bug 1432062 : multipath-tools-boot: support booting without user_friendly_names on devices with spaces in identifiers - * bug 1463043 : some SM15K systems fail to boot after deployment - drop into initramfs shell - * bug
[Bug 1371634] Re: block devices appear twice [install does not use multipath]
** Description changed: + === Begin SRU Information === + [Description] + When curtin installs to a system that has multipath devices, it does not recognize this and enable them. + The result is that a system that has multipath devices installed will have Ubuntu installed to one of the non-multipath paths. The end user is then confused because they see root installed on /dev/sda1 and another device /dev/sdg1 (or other name) that has the same content as /dev/sda1. In addition to this confusion, if the user decides to use /dev/sdg1 and format it, they'll have shot themselves in the foot by destroying their root partition. + + The general solution is to install multipath-tools-boot when the system is detected to have multipath devices. To do this, curtin does: + curtin currently does: + a.) installs multipath-boot *only* when multipath devices are found, avoiding bug 1463046. + b.) writes /etc/multipath.conf to use user_friendly_names, avoiding bug 1432062. + c.) writes /etc/multipath/bindings file to provide a consistent named /dev/mapper/mpath name (solving bug 1429327) + + [Impact] + Without this fix, most power 8 systems will install to /dev/sda1 and let the user modify /dev/sdg1 (or whatever device name that multipath device appears as). This is not very user friendly, and quite confusing. + + [Test Case] + Positive case: + a.) install system that has multipath + b.) verify that multipath-tools-boot is installed. + c.) verify that system is booted with root=/dev/mapper/mpath0-part2 + + Negative case: + a.) install system with 2 disks without multipath + b.) verify that no multipath-tools-boot is installed. + + [Regression Potential] + The regression potential falls into 2 places: + a.) a system with multipath that installed without multipath fails to install or work after this + this is really a bug in multipath in kenrel or the package if we get here. We've done fairly significant testing to show that we're reliably installing. + + b.) a system without multipath is identified as multipath + The detection of multipath basically consists of looking for 2 devices that have a filesystem with the same UUID on them after creating a filesystem with that UUID. This is essentially not more than a check for a random sequence of bytes on all disks rather than a fully determinable identification of multipath. So, the failure case is: + 1.) we install to system and 'mkfs' the root partition + 2.) we find 2 disks that have the same UUID as the root device (the root device and one other) + In all likelyhood, that would mean that a filesytem with this UUID already existed on the system. That seems quite unlikley. + + In the event that the user does not have multipath systems and just wants to disable multipath to avoid that scenario, they can do so by config in maas setting the following in /etc/maas/preseeds/curtin_userdata will disable multipath and boot quite reliably without multipath. + multipath: + mode: false + + [Other] + Related bugs: + * bug 1432062 : multipath-tools-boot: support booting without user_friendly_names on devices with spaces in identifiers + * bug 1463043 : some SM15K systems fail to boot after deployment - drop into initramfs shell + * bug 1462530 : multipath errors on vivid, wily kernel + * bug 1463046 : installation of multipath-tools-boot can break boot + * bug 1447167 : [d-i] multipath-install: Installing with multipath enabled does not install multipath-tools + * bug 1429327 : Boot from an unique, stable, multipath-dependent symlink + + === End SRU Information === + + === Original bug report === $ sudo blkid /dev/sr0: LABEL=Ubuntu-Server 14.04 LTS ppc64el TYPE=iso9660 /dev/sda2: UUID=795a6e14-ea4e-4718-9e98-c6df3696920c TYPE=ext4 /dev/sda3: UUID=0a91d81f-6a16-4b96-a92c-11ca8bdc4bf4 TYPE=swap /dev/sdb2: UUID=1d14c1f3-716f-4fb8-9070-d321b39ffcb3 TYPE=ext4 /dev/sdb3: UUID=9c228177-d65c-4d19-a462-db1891e9781e TYPE=swap /dev/sdg2: UUID=795a6e14-ea4e-4718-9e98-c6df3696920c TYPE=ext4 /dev/sdg3: UUID=0a91d81f-6a16-4b96-a92c-11ca8bdc4bf4 TYPE=swap /dev/sdh2: UUID=1d14c1f3-716f-4fb8-9070-d321b39ffcb3 TYPE=ext4 /dev/sdh3: UUID=9c228177-d65c-4d19-a462-db1891e9781e TYPE=swap I'm not sure what exactly those block devices are (as in if they're raided in hardware or they actually represent physical spinning disks). But I do know that writing data to sda causes that data to be readable from sdg. The same is true: sda - sdg sdb - sdh That is what causes those UUIDs to be similar. Everything is functional, you just have to know that if your root device is /dev/sdg that you should probably not write data to /dev/sda thinking you can use it as a disk. - - Related bugs: - * bug 1432062 : multipath-tools-boot: support booting without user_friendly_names on devices with spaces in identifiers - * bug 1463043 : some SM15K systems fail to boot after deployment - drop into initramfs shell - * bug
[Bug 1371634] Re: block devices appear twice [install does not use multipath]
** Branch linked: lp:~smoser/ubuntu/trusty/curtin/trusty-sru -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1371634 Title: block devices appear twice [install does not use multipath] To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1371634/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1371634] Re: block devices appear twice [install does not use multipath]
** Branch linked: lp:~smoser/ubuntu/trusty/curtin/trusty-sru -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to curtin in Ubuntu. https://bugs.launchpad.net/bugs/1371634 Title: block devices appear twice [install does not use multipath] To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1371634/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1371634] Re: block devices appear twice
** No longer affects: linux (Ubuntu Trusty) ** Summary changed: - block devices appear twice + block devices appear twice [install does not use multipath] ** No longer affects: multipath-tools (Ubuntu Trusty) ** No longer affects: multipath-tools (Ubuntu Vivid) ** Also affects: curtin Importance: Undecided Status: New ** Changed in: curtin Status: New = Fix Committed ** Changed in: curtin Importance: Undecided = Medium ** Changed in: curtin Importance: Medium = High ** No longer affects: linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1371634 Title: block devices appear twice [install does not use multipath] To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1371634/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1371634] Re: block devices appear twice
** No longer affects: linux (Ubuntu Trusty) ** Summary changed: - block devices appear twice + block devices appear twice [install does not use multipath] ** No longer affects: multipath-tools (Ubuntu Trusty) ** No longer affects: multipath-tools (Ubuntu Vivid) ** Also affects: curtin Importance: Undecided Status: New ** Changed in: curtin Status: New = Fix Committed ** Changed in: curtin Importance: Undecided = Medium ** Changed in: curtin Importance: Medium = High ** No longer affects: linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to curtin in Ubuntu. https://bugs.launchpad.net/bugs/1371634 Title: block devices appear twice [install does not use multipath] To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1371634/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1371634] Re: block devices appear twice [install does not use multipath]
this is a set of logs collected by https://gist.github.com/smoser/e0cd7fafef8f52c24571 I'm posting them here to show that this seems pretty functional and reliable at the moment. It installed trusty-hwe-u, trusty-hwe-v, vivid, wily in a loop 15 times each. It did fail on runs 16-20, but I believe the ipmi serial died, and since check for success was based on that, it marked them as failed and I did not get logs. ** Changed in: curtin (Ubuntu Trusty) Status: New = Confirmed ** Changed in: curtin (Ubuntu Vivid) Status: New = Confirmed ** Changed in: curtin (Ubuntu Trusty) Importance: Undecided = High ** Changed in: curtin (Ubuntu Vivid) Importance: Undecided = High ** Attachment added: console logs from a deploy loop https://bugs.launchpad.net/curtin/+bug/1371634/+attachment/4418544/+files/deploy-loop-logs.tar.xz ** No longer affects: linux (Ubuntu Vivid) ** No longer affects: multipath-tools (Ubuntu) ** Description changed: $ sudo blkid /dev/sr0: LABEL=Ubuntu-Server 14.04 LTS ppc64el TYPE=iso9660 /dev/sda2: UUID=795a6e14-ea4e-4718-9e98-c6df3696920c TYPE=ext4 /dev/sda3: UUID=0a91d81f-6a16-4b96-a92c-11ca8bdc4bf4 TYPE=swap /dev/sdb2: UUID=1d14c1f3-716f-4fb8-9070-d321b39ffcb3 TYPE=ext4 /dev/sdb3: UUID=9c228177-d65c-4d19-a462-db1891e9781e TYPE=swap /dev/sdg2: UUID=795a6e14-ea4e-4718-9e98-c6df3696920c TYPE=ext4 /dev/sdg3: UUID=0a91d81f-6a16-4b96-a92c-11ca8bdc4bf4 TYPE=swap /dev/sdh2: UUID=1d14c1f3-716f-4fb8-9070-d321b39ffcb3 TYPE=ext4 /dev/sdh3: UUID=9c228177-d65c-4d19-a462-db1891e9781e TYPE=swap I'm not sure what exactly those block devices are (as in if they're raided in hardware or they actually represent physical spinning disks). But I do know that writing data to sda causes that data to be readable from sdg. The same is true: sda - sdg sdb - sdh That is what causes those UUIDs to be similar. Everything is functional, you just have to know that if your root device is /dev/sdg that you should probably not write data to /dev/sda thinking you can use it as a disk. Related bugs: - * bug 1432062: multipath-tools-boot: support booting without user_friendly_names on devices with spaces in identifiers - * bug 1463043 : some SM15K systems fail to boot after deployment - drop into initramfs shell - * bug 1462530 : multipath errors on vivid, wily kernel - * bug 1463046: installation of multipath-tools-boot can break boot + * bug 1432062 : multipath-tools-boot: support booting without user_friendly_names on devices with spaces in identifiers + * bug 1463043 : some SM15K systems fail to boot after deployment - drop into initramfs shell + * bug 1462530 : multipath errors on vivid, wily kernel + * bug 1463046: installation of multipath-tools-boot can break boot + * bug 1447167: multipath-install: Installing with multipath enabled does not install multipath-tools ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-35-generic 3.13.0-35.62 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic ppc64le AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.4 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: Error: [Errno 2] No such file or directory: 'iw' CurrentDmesg: [ 88.736220] init: plymouth-upstart-bridge main process ended, respawning Date: Fri Sep 19 14:31:20 2014 HibernationDevice: RESUME=UUID=9c228177-d65c-4d19-a462-db1891e9781e Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: root=UUID=1d14c1f3-716f-4fb8-9070-d321b39ffcb3 ro console=hvc0 BOOTIF=01-6c-ae-8b-6a-a0-88 quiet RelatedPackageVersions: linux-restricted-modules-3.13.0-35-generic N/A linux-backports-modules-3.13.0-35-generic N/A linux-firmware 1.127.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) ** Also affects: curtin (Ubuntu Utopic) Importance: Undecided Status: New ** Changed in: curtin (Ubuntu Utopic) Status: New = Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1371634 Title: block devices appear twice [install does not use multipath] To manage notifications about this bug go to:
[Bug 1371634] Re: block devices appear twice [install does not use multipath]
** Description changed: $ sudo blkid /dev/sr0: LABEL=Ubuntu-Server 14.04 LTS ppc64el TYPE=iso9660 /dev/sda2: UUID=795a6e14-ea4e-4718-9e98-c6df3696920c TYPE=ext4 /dev/sda3: UUID=0a91d81f-6a16-4b96-a92c-11ca8bdc4bf4 TYPE=swap /dev/sdb2: UUID=1d14c1f3-716f-4fb8-9070-d321b39ffcb3 TYPE=ext4 /dev/sdb3: UUID=9c228177-d65c-4d19-a462-db1891e9781e TYPE=swap /dev/sdg2: UUID=795a6e14-ea4e-4718-9e98-c6df3696920c TYPE=ext4 /dev/sdg3: UUID=0a91d81f-6a16-4b96-a92c-11ca8bdc4bf4 TYPE=swap /dev/sdh2: UUID=1d14c1f3-716f-4fb8-9070-d321b39ffcb3 TYPE=ext4 /dev/sdh3: UUID=9c228177-d65c-4d19-a462-db1891e9781e TYPE=swap I'm not sure what exactly those block devices are (as in if they're raided in hardware or they actually represent physical spinning disks). But I do know that writing data to sda causes that data to be readable from sdg. The same is true: sda - sdg sdb - sdh That is what causes those UUIDs to be similar. Everything is functional, you just have to know that if your root device is /dev/sdg that you should probably not write data to /dev/sda thinking you can use it as a disk. Related bugs: * bug 1432062 : multipath-tools-boot: support booting without user_friendly_names on devices with spaces in identifiers * bug 1463043 : some SM15K systems fail to boot after deployment - drop into initramfs shell * bug 1462530 : multipath errors on vivid, wily kernel - * bug 1463046: installation of multipath-tools-boot can break boot - * bug 1447167: multipath-install: Installing with multipath enabled does not install multipath-tools + * bug 1463046 : installation of multipath-tools-boot can break boot + * bug 1447167 : [d-i] multipath-install: Installing with multipath enabled does not install multipath-tools + * bug 1429327 : Boot from an unique, stable, multipath-dependent symlink + ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-35-generic 3.13.0-35.62 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic ppc64le AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.4 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: Error: [Errno 2] No such file or directory: 'iw' CurrentDmesg: [ 88.736220] init: plymouth-upstart-bridge main process ended, respawning Date: Fri Sep 19 14:31:20 2014 HibernationDevice: RESUME=UUID=9c228177-d65c-4d19-a462-db1891e9781e Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: root=UUID=1d14c1f3-716f-4fb8-9070-d321b39ffcb3 ro console=hvc0 BOOTIF=01-6c-ae-8b-6a-a0-88 quiet RelatedPackageVersions: linux-restricted-modules-3.13.0-35-generic N/A linux-backports-modules-3.13.0-35-generic N/A linux-firmware 1.127.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1371634 Title: block devices appear twice [install does not use multipath] To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1371634/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1371634] Re: block devices appear twice [install does not use multipath]
** Description changed: $ sudo blkid /dev/sr0: LABEL=Ubuntu-Server 14.04 LTS ppc64el TYPE=iso9660 /dev/sda2: UUID=795a6e14-ea4e-4718-9e98-c6df3696920c TYPE=ext4 /dev/sda3: UUID=0a91d81f-6a16-4b96-a92c-11ca8bdc4bf4 TYPE=swap /dev/sdb2: UUID=1d14c1f3-716f-4fb8-9070-d321b39ffcb3 TYPE=ext4 /dev/sdb3: UUID=9c228177-d65c-4d19-a462-db1891e9781e TYPE=swap /dev/sdg2: UUID=795a6e14-ea4e-4718-9e98-c6df3696920c TYPE=ext4 /dev/sdg3: UUID=0a91d81f-6a16-4b96-a92c-11ca8bdc4bf4 TYPE=swap /dev/sdh2: UUID=1d14c1f3-716f-4fb8-9070-d321b39ffcb3 TYPE=ext4 /dev/sdh3: UUID=9c228177-d65c-4d19-a462-db1891e9781e TYPE=swap I'm not sure what exactly those block devices are (as in if they're raided in hardware or they actually represent physical spinning disks). But I do know that writing data to sda causes that data to be readable from sdg. The same is true: sda - sdg sdb - sdh That is what causes those UUIDs to be similar. Everything is functional, you just have to know that if your root device is /dev/sdg that you should probably not write data to /dev/sda thinking you can use it as a disk. Related bugs: * bug 1432062 : multipath-tools-boot: support booting without user_friendly_names on devices with spaces in identifiers * bug 1463043 : some SM15K systems fail to boot after deployment - drop into initramfs shell * bug 1462530 : multipath errors on vivid, wily kernel - * bug 1463046: installation of multipath-tools-boot can break boot - * bug 1447167: multipath-install: Installing with multipath enabled does not install multipath-tools + * bug 1463046 : installation of multipath-tools-boot can break boot + * bug 1447167 : [d-i] multipath-install: Installing with multipath enabled does not install multipath-tools + * bug 1429327 : Boot from an unique, stable, multipath-dependent symlink + ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-35-generic 3.13.0-35.62 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic ppc64le AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.4 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: Error: [Errno 2] No such file or directory: 'iw' CurrentDmesg: [ 88.736220] init: plymouth-upstart-bridge main process ended, respawning Date: Fri Sep 19 14:31:20 2014 HibernationDevice: RESUME=UUID=9c228177-d65c-4d19-a462-db1891e9781e Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: root=UUID=1d14c1f3-716f-4fb8-9070-d321b39ffcb3 ro console=hvc0 BOOTIF=01-6c-ae-8b-6a-a0-88 quiet RelatedPackageVersions: linux-restricted-modules-3.13.0-35-generic N/A linux-backports-modules-3.13.0-35-generic N/A linux-firmware 1.127.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to curtin in Ubuntu. https://bugs.launchpad.net/bugs/1371634 Title: block devices appear twice [install does not use multipath] To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1371634/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1371634] Re: block devices appear twice [install does not use multipath]
Some status here. I believe this is fixed in curtin trunk. Curtin should properly identify systems with multipath devices and install multipath-tools-boot and configure the system to boot from a reliable path. curtin at revision 220 should be good. That is available in: wily archive: https://launchpad.net/ubuntu/+source/curtin maas experimental ppa for trusty utopic vivid: https://launchpad.net/~maas-maintainers/+archive/ubuntu/experimental maas testing ppa for trusty utopic vivid: https://launchpad.net/~maas-maintainers/+archive/ubuntu/testing/+packages The things left to get this functional in all supported places are: a.) copy to maas stable ppa b.) SRU to trusty and vivid (i'm not planning on bothering with utopic). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1371634 Title: block devices appear twice [install does not use multipath] To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1371634/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1371634] Re: block devices appear twice [install does not use multipath]
Some status here. I believe this is fixed in curtin trunk. Curtin should properly identify systems with multipath devices and install multipath-tools-boot and configure the system to boot from a reliable path. curtin at revision 220 should be good. That is available in: wily archive: https://launchpad.net/ubuntu/+source/curtin maas experimental ppa for trusty utopic vivid: https://launchpad.net/~maas-maintainers/+archive/ubuntu/experimental maas testing ppa for trusty utopic vivid: https://launchpad.net/~maas-maintainers/+archive/ubuntu/testing/+packages The things left to get this functional in all supported places are: a.) copy to maas stable ppa b.) SRU to trusty and vivid (i'm not planning on bothering with utopic). -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to curtin in Ubuntu. https://bugs.launchpad.net/bugs/1371634 Title: block devices appear twice [install does not use multipath] To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1371634/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1371634] Re: block devices appear twice [install does not use multipath]
this is a set of logs collected by https://gist.github.com/smoser/e0cd7fafef8f52c24571 I'm posting them here to show that this seems pretty functional and reliable at the moment. It installed trusty-hwe-u, trusty-hwe-v, vivid, wily in a loop 15 times each. It did fail on runs 16-20, but I believe the ipmi serial died, and since check for success was based on that, it marked them as failed and I did not get logs. ** Changed in: curtin (Ubuntu Trusty) Status: New = Confirmed ** Changed in: curtin (Ubuntu Vivid) Status: New = Confirmed ** Changed in: curtin (Ubuntu Trusty) Importance: Undecided = High ** Changed in: curtin (Ubuntu Vivid) Importance: Undecided = High ** Attachment added: console logs from a deploy loop https://bugs.launchpad.net/curtin/+bug/1371634/+attachment/4418544/+files/deploy-loop-logs.tar.xz ** No longer affects: linux (Ubuntu Vivid) ** No longer affects: multipath-tools (Ubuntu) ** Description changed: $ sudo blkid /dev/sr0: LABEL=Ubuntu-Server 14.04 LTS ppc64el TYPE=iso9660 /dev/sda2: UUID=795a6e14-ea4e-4718-9e98-c6df3696920c TYPE=ext4 /dev/sda3: UUID=0a91d81f-6a16-4b96-a92c-11ca8bdc4bf4 TYPE=swap /dev/sdb2: UUID=1d14c1f3-716f-4fb8-9070-d321b39ffcb3 TYPE=ext4 /dev/sdb3: UUID=9c228177-d65c-4d19-a462-db1891e9781e TYPE=swap /dev/sdg2: UUID=795a6e14-ea4e-4718-9e98-c6df3696920c TYPE=ext4 /dev/sdg3: UUID=0a91d81f-6a16-4b96-a92c-11ca8bdc4bf4 TYPE=swap /dev/sdh2: UUID=1d14c1f3-716f-4fb8-9070-d321b39ffcb3 TYPE=ext4 /dev/sdh3: UUID=9c228177-d65c-4d19-a462-db1891e9781e TYPE=swap I'm not sure what exactly those block devices are (as in if they're raided in hardware or they actually represent physical spinning disks). But I do know that writing data to sda causes that data to be readable from sdg. The same is true: sda - sdg sdb - sdh That is what causes those UUIDs to be similar. Everything is functional, you just have to know that if your root device is /dev/sdg that you should probably not write data to /dev/sda thinking you can use it as a disk. Related bugs: - * bug 1432062: multipath-tools-boot: support booting without user_friendly_names on devices with spaces in identifiers - * bug 1463043 : some SM15K systems fail to boot after deployment - drop into initramfs shell - * bug 1462530 : multipath errors on vivid, wily kernel - * bug 1463046: installation of multipath-tools-boot can break boot + * bug 1432062 : multipath-tools-boot: support booting without user_friendly_names on devices with spaces in identifiers + * bug 1463043 : some SM15K systems fail to boot after deployment - drop into initramfs shell + * bug 1462530 : multipath errors on vivid, wily kernel + * bug 1463046: installation of multipath-tools-boot can break boot + * bug 1447167: multipath-install: Installing with multipath enabled does not install multipath-tools ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-35-generic 3.13.0-35.62 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic ppc64le AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.4 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: Error: [Errno 2] No such file or directory: 'iw' CurrentDmesg: [ 88.736220] init: plymouth-upstart-bridge main process ended, respawning Date: Fri Sep 19 14:31:20 2014 HibernationDevice: RESUME=UUID=9c228177-d65c-4d19-a462-db1891e9781e Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: root=UUID=1d14c1f3-716f-4fb8-9070-d321b39ffcb3 ro console=hvc0 BOOTIF=01-6c-ae-8b-6a-a0-88 quiet RelatedPackageVersions: linux-restricted-modules-3.13.0-35-generic N/A linux-backports-modules-3.13.0-35-generic N/A linux-firmware 1.127.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) ** Also affects: curtin (Ubuntu Utopic) Importance: Undecided Status: New ** Changed in: curtin (Ubuntu Utopic) Status: New = Won't Fix -- 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/1371634 Title: block devices appear twice [install does not use multipath] To manage
[Bug 1371634] Re: block devices appear twice
** Branch linked: lp:ubuntu/curtin -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1371634 Title: block devices appear twice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1371634/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1371634] Re: block devices appear twice
** Branch linked: lp:ubuntu/curtin -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to curtin in Ubuntu. https://bugs.launchpad.net/bugs/1371634 Title: block devices appear twice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1371634/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1371634] Re: block devices appear twice
Mike, Please move issues with multipath (like are shown in that log) to bug 1462530. Stefan had actually asked for almost exactly what you captured. This bug is fixed as we're now booting into system correctly with multipath enabled from installation under curtin. I'll copy your comment and attachment there. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1371634 Title: block devices appear twice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1371634/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1371634] Re: block devices appear twice
Mike, Please move issues with multipath (like are shown in that log) to bug 1462530. Stefan had actually asked for almost exactly what you captured. This bug is fixed as we're now booting into system correctly with multipath enabled from installation under curtin. I'll copy your comment and attachment there. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to curtin in Ubuntu. https://bugs.launchpad.net/bugs/1371634 Title: block devices appear twice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1371634/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1371634] Re: block devices appear twice
** Also affects: multipath-tools (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: curtin (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: multipath-tools (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: curtin (Ubuntu Vivid) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to curtin in Ubuntu. https://bugs.launchpad.net/bugs/1371634 Title: block devices appear twice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1371634/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1371634] Re: block devices appear twice
** Also affects: multipath-tools (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: curtin (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: multipath-tools (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: curtin (Ubuntu Vivid) 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/1371634 Title: block devices appear twice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1371634/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1371634] Re: block devices appear twice
I have tried the latest curtin-common and python-curtin from the wily repositories running on 14.04.2: #leftyfb@maaster[0]:~$ apt-cache policy curtin-common curtin-common: Installed: 0.1.0~bzr214-0ubuntu1 Candidate: 0.1.0~bzr214-0ubuntu1 Version table: *** 0.1.0~bzr214-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages 100 /var/lib/dpkg/status 0.1.0~bzr201-0ubuntu1~14.04.1 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 0.1.0~bzr201-0ubuntu1~14.04.1~ppa0 0 500 http://ppa.launchpad.net/maas-maintainers/stable/ubuntu/ trusty/main amd64 Packages 0.1.0~bzr126-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages #leftyfb@maaster[0]:~$ apt-cache policy python-curtin python-curtin: Installed: 0.1.0~bzr214-0ubuntu1 Candidate: 0.1.0~bzr214-0ubuntu1 Version table: *** 0.1.0~bzr214-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages 100 /var/lib/dpkg/status 0.1.0~bzr201-0ubuntu1~14.04.1 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 0.1.0~bzr201-0ubuntu1~14.04.1~ppa0 0 500 http://ppa.launchpad.net/maas-maintainers/stable/ubuntu/ trusty/main amd64 Packages 0.1.0~bzr126-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages #leftyfb@maaster[0]:~$ apt-cache policy maas maas: Installed: 1.7.5+bzr3369-0ubuntu1~trusty1 Candidate: 1.7.5+bzr3369-0ubuntu1 Version table: 1.7.5+bzr3369-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages *** 1.7.5+bzr3369-0ubuntu1~trusty1 0 500 http://ppa.launchpad.net/maas-maintainers/stable/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status 1.5.4+bzr2294-0ubuntu1.3 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 1.5.4+bzr2294-0ubuntu1.2 0 500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages 1.5+bzr2252-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages The deployment never fully boots up. It never gets to a console or allows an ssh connection. Attached is a log of the deployment and first boot process to debug. ** Attachment added: multipath.log https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1371634/+attachment/4412768/+files/multipath.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1371634 Title: block devices appear twice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1371634/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1371634] Re: block devices appear twice
I have tried the latest curtin-common and python-curtin from the wily repositories running on 14.04.2: #leftyfb@maaster[0]:~$ apt-cache policy curtin-common curtin-common: Installed: 0.1.0~bzr214-0ubuntu1 Candidate: 0.1.0~bzr214-0ubuntu1 Version table: *** 0.1.0~bzr214-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages 100 /var/lib/dpkg/status 0.1.0~bzr201-0ubuntu1~14.04.1 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 0.1.0~bzr201-0ubuntu1~14.04.1~ppa0 0 500 http://ppa.launchpad.net/maas-maintainers/stable/ubuntu/ trusty/main amd64 Packages 0.1.0~bzr126-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages #leftyfb@maaster[0]:~$ apt-cache policy python-curtin python-curtin: Installed: 0.1.0~bzr214-0ubuntu1 Candidate: 0.1.0~bzr214-0ubuntu1 Version table: *** 0.1.0~bzr214-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages 100 /var/lib/dpkg/status 0.1.0~bzr201-0ubuntu1~14.04.1 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 0.1.0~bzr201-0ubuntu1~14.04.1~ppa0 0 500 http://ppa.launchpad.net/maas-maintainers/stable/ubuntu/ trusty/main amd64 Packages 0.1.0~bzr126-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages #leftyfb@maaster[0]:~$ apt-cache policy maas maas: Installed: 1.7.5+bzr3369-0ubuntu1~trusty1 Candidate: 1.7.5+bzr3369-0ubuntu1 Version table: 1.7.5+bzr3369-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages *** 1.7.5+bzr3369-0ubuntu1~trusty1 0 500 http://ppa.launchpad.net/maas-maintainers/stable/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status 1.5.4+bzr2294-0ubuntu1.3 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 1.5.4+bzr2294-0ubuntu1.2 0 500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages 1.5+bzr2252-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages The deployment never fully boots up. It never gets to a console or allows an ssh connection. Attached is a log of the deployment and first boot process to debug. ** Attachment added: multipath.log https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1371634/+attachment/4412768/+files/multipath.log -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to curtin in Ubuntu. https://bugs.launchpad.net/bugs/1371634 Title: block devices appear twice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1371634/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1371634] Re: block devices appear twice
** Description changed: $ sudo blkid /dev/sr0: LABEL=Ubuntu-Server 14.04 LTS ppc64el TYPE=iso9660 /dev/sda2: UUID=795a6e14-ea4e-4718-9e98-c6df3696920c TYPE=ext4 /dev/sda3: UUID=0a91d81f-6a16-4b96-a92c-11ca8bdc4bf4 TYPE=swap /dev/sdb2: UUID=1d14c1f3-716f-4fb8-9070-d321b39ffcb3 TYPE=ext4 /dev/sdb3: UUID=9c228177-d65c-4d19-a462-db1891e9781e TYPE=swap /dev/sdg2: UUID=795a6e14-ea4e-4718-9e98-c6df3696920c TYPE=ext4 /dev/sdg3: UUID=0a91d81f-6a16-4b96-a92c-11ca8bdc4bf4 TYPE=swap /dev/sdh2: UUID=1d14c1f3-716f-4fb8-9070-d321b39ffcb3 TYPE=ext4 /dev/sdh3: UUID=9c228177-d65c-4d19-a462-db1891e9781e TYPE=swap I'm not sure what exactly those block devices are (as in if they're raided in hardware or they actually represent physical spinning disks). But I do know that writing data to sda causes that data to be readable from sdg. The same is true: sda - sdg sdb - sdh That is what causes those UUIDs to be similar. Everything is functional, you just have to know that if your root device is /dev/sdg that you should probably not write data to /dev/sda thinking you can use it as a disk. Related bugs: - * bug 1432062: multipath-tools-boot: support booting without user_friendly_names on devices with spaces in identifiers - + * bug 1432062: multipath-tools-boot: support booting without user_friendly_names on devices with spaces in identifiers + * bug 1463043 : some SM15K systems fail to boot after deployment - drop into initramfs shell + * bug 1462530 : multipath errors on vivid, wily kernel + * bug 1463046: installation of multipath-tools-boot can break boot ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-35-generic 3.13.0-35.62 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic ppc64le AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.4 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: Error: [Errno 2] No such file or directory: 'iw' CurrentDmesg: [ 88.736220] init: plymouth-upstart-bridge main process ended, respawning Date: Fri Sep 19 14:31:20 2014 HibernationDevice: RESUME=UUID=9c228177-d65c-4d19-a462-db1891e9781e Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: root=UUID=1d14c1f3-716f-4fb8-9070-d321b39ffcb3 ro console=hvc0 BOOTIF=01-6c-ae-8b-6a-a0-88 quiet RelatedPackageVersions: linux-restricted-modules-3.13.0-35-generic N/A linux-backports-modules-3.13.0-35-generic N/A linux-firmware 1.127.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1371634 Title: block devices appear twice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1371634/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1371634] Re: block devices appear twice
** Description changed: $ sudo blkid /dev/sr0: LABEL=Ubuntu-Server 14.04 LTS ppc64el TYPE=iso9660 /dev/sda2: UUID=795a6e14-ea4e-4718-9e98-c6df3696920c TYPE=ext4 /dev/sda3: UUID=0a91d81f-6a16-4b96-a92c-11ca8bdc4bf4 TYPE=swap /dev/sdb2: UUID=1d14c1f3-716f-4fb8-9070-d321b39ffcb3 TYPE=ext4 /dev/sdb3: UUID=9c228177-d65c-4d19-a462-db1891e9781e TYPE=swap /dev/sdg2: UUID=795a6e14-ea4e-4718-9e98-c6df3696920c TYPE=ext4 /dev/sdg3: UUID=0a91d81f-6a16-4b96-a92c-11ca8bdc4bf4 TYPE=swap /dev/sdh2: UUID=1d14c1f3-716f-4fb8-9070-d321b39ffcb3 TYPE=ext4 /dev/sdh3: UUID=9c228177-d65c-4d19-a462-db1891e9781e TYPE=swap I'm not sure what exactly those block devices are (as in if they're raided in hardware or they actually represent physical spinning disks). But I do know that writing data to sda causes that data to be readable from sdg. The same is true: sda - sdg sdb - sdh That is what causes those UUIDs to be similar. Everything is functional, you just have to know that if your root device is /dev/sdg that you should probably not write data to /dev/sda thinking you can use it as a disk. Related bugs: - * bug 1432062: multipath-tools-boot: support booting without user_friendly_names on devices with spaces in identifiers - + * bug 1432062: multipath-tools-boot: support booting without user_friendly_names on devices with spaces in identifiers + * bug 1463043 : some SM15K systems fail to boot after deployment - drop into initramfs shell + * bug 1462530 : multipath errors on vivid, wily kernel + * bug 1463046: installation of multipath-tools-boot can break boot ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-35-generic 3.13.0-35.62 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic ppc64le AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.4 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: Error: [Errno 2] No such file or directory: 'iw' CurrentDmesg: [ 88.736220] init: plymouth-upstart-bridge main process ended, respawning Date: Fri Sep 19 14:31:20 2014 HibernationDevice: RESUME=UUID=9c228177-d65c-4d19-a462-db1891e9781e Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: root=UUID=1d14c1f3-716f-4fb8-9070-d321b39ffcb3 ro console=hvc0 BOOTIF=01-6c-ae-8b-6a-a0-88 quiet RelatedPackageVersions: linux-restricted-modules-3.13.0-35-generic N/A linux-backports-modules-3.13.0-35-generic N/A linux-firmware 1.127.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) -- 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/1371634 Title: block devices appear twice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1371634/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1371634] Re: block devices appear twice
** Branch linked: lp:curtin -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1371634 Title: block devices appear twice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1371634/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1371634] Re: block devices appear twice
** Branch linked: lp:curtin -- 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/1371634 Title: block devices appear twice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1371634/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1371634] Re: block devices appear twice
Mike, Oleg, others. I've opened bug 1462530 to address the errors I'm seeing like those Mike pointed at. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1371634 Title: block devices appear twice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1371634/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1371634] Re: block devices appear twice
Mike, Oleg, others. I've opened bug 1462530 to address the errors I'm seeing like those Mike pointed at. -- 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/1371634 Title: block devices appear twice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1371634/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1371634] Re: block devices appear twice
This bug was fixed in the package curtin - 0.1.0~bzr213-0ubuntu1 --- curtin (0.1.0~bzr213-0ubuntu1) wily; urgency=medium * New upstream snapshot. * retry apt-get update to avoid transient failures (LP: #1403133) * detect and handle multipath devices (LP: #1371634) * udevadm settle before unmounting target's /dev (LP: #1462139) * doc/ improved developer doc and tools using maas images for test * use --no-nvram option to grub-install if available (LP: #1311827) -- Scott Moser smo...@ubuntu.com Fri, 05 Jun 2015 15:06:31 -0400 ** Changed in: curtin (Ubuntu) Status: Confirmed = Fix Released -- 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/1371634 Title: block devices appear twice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1371634/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1371634] Re: block devices appear twice
This bug was fixed in the package curtin - 0.1.0~bzr213-0ubuntu1 --- curtin (0.1.0~bzr213-0ubuntu1) wily; urgency=medium * New upstream snapshot. * retry apt-get update to avoid transient failures (LP: #1403133) * detect and handle multipath devices (LP: #1371634) * udevadm settle before unmounting target's /dev (LP: #1462139) * doc/ improved developer doc and tools using maas images for test * use --no-nvram option to grub-install if available (LP: #1311827) -- Scott Moser smo...@ubuntu.com Fri, 05 Jun 2015 15:06:31 -0400 ** Changed in: curtin (Ubuntu) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1371634 Title: block devices appear twice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1371634/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1371634] Re: block devices appear twice
** Branch linked: lp:~strikov/curtin/multipath-2 -- 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/1371634 Title: block devices appear twice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1371634/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1371634] Re: block devices appear twice
** Branch linked: lp:~strikov/curtin/multipath-2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1371634 Title: block devices appear twice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1371634/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1371634] Re: block devices appear twice
I tried following the above workaround on the IBM Power 8 twice on new deployments. Attached is the log. ** Attachment added: multipath.log https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1371634/+attachment/4409977/+files/multipath.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1371634 Title: block devices appear twice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1371634/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1371634] Re: block devices appear twice
I tried following the above workaround on the IBM Power 8 twice on new deployments. Attached is the log. ** Attachment added: multipath.log https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1371634/+attachment/4409977/+files/multipath.log -- 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/1371634 Title: block devices appear twice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1371634/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1371634] Re: block devices appear twice
** Description changed: - $ sudo blkid - /dev/sr0: LABEL=Ubuntu-Server 14.04 LTS ppc64el TYPE=iso9660 - /dev/sda2: UUID=795a6e14-ea4e-4718-9e98-c6df3696920c TYPE=ext4 - /dev/sda3: UUID=0a91d81f-6a16-4b96-a92c-11ca8bdc4bf4 TYPE=swap - /dev/sdb2: UUID=1d14c1f3-716f-4fb8-9070-d321b39ffcb3 TYPE=ext4 - /dev/sdb3: UUID=9c228177-d65c-4d19-a462-db1891e9781e TYPE=swap - /dev/sdg2: UUID=795a6e14-ea4e-4718-9e98-c6df3696920c TYPE=ext4 - /dev/sdg3: UUID=0a91d81f-6a16-4b96-a92c-11ca8bdc4bf4 TYPE=swap - /dev/sdh2: UUID=1d14c1f3-716f-4fb8-9070-d321b39ffcb3 TYPE=ext4 - /dev/sdh3: UUID=9c228177-d65c-4d19-a462-db1891e9781e TYPE=swap + $ sudo blkid + /dev/sr0: LABEL=Ubuntu-Server 14.04 LTS ppc64el TYPE=iso9660 + /dev/sda2: UUID=795a6e14-ea4e-4718-9e98-c6df3696920c TYPE=ext4 + /dev/sda3: UUID=0a91d81f-6a16-4b96-a92c-11ca8bdc4bf4 TYPE=swap + /dev/sdb2: UUID=1d14c1f3-716f-4fb8-9070-d321b39ffcb3 TYPE=ext4 + /dev/sdb3: UUID=9c228177-d65c-4d19-a462-db1891e9781e TYPE=swap + /dev/sdg2: UUID=795a6e14-ea4e-4718-9e98-c6df3696920c TYPE=ext4 + /dev/sdg3: UUID=0a91d81f-6a16-4b96-a92c-11ca8bdc4bf4 TYPE=swap + /dev/sdh2: UUID=1d14c1f3-716f-4fb8-9070-d321b39ffcb3 TYPE=ext4 + /dev/sdh3: UUID=9c228177-d65c-4d19-a462-db1891e9781e TYPE=swap I'm not sure what exactly those block devices are (as in if they're raided in hardware or they actually represent physical spinning disks). But I do know that writing data to sda causes that data to be readable from sdg. The same is true: - sda - sdg - sdb - sdh + sda - sdg + sdb - sdh That is what causes those UUIDs to be similar. Everything is functional, you just have to know that if your root device is /dev/sdg that you should probably not write data to /dev/sda thinking you can use it as a disk. + + Related bugs: + * bug 1432062: multipath-tools-boot: support booting without user_friendly_names on devices with spaces in identifiers + ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-35-generic 3.13.0-35.62 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic ppc64le AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.4 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: Error: [Errno 2] No such file or directory: 'iw' CurrentDmesg: [ 88.736220] init: plymouth-upstart-bridge main process ended, respawning Date: Fri Sep 19 14:31:20 2014 HibernationDevice: RESUME=UUID=9c228177-d65c-4d19-a462-db1891e9781e Lsusb: - Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub - Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub - Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub - Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProcEnviron: - TERM=screen - PATH=(custom, no user) - XDG_RUNTIME_DIR=set - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=screen + PATH=(custom, no user) + XDG_RUNTIME_DIR=set + LANG=en_US.UTF-8 + SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: root=UUID=1d14c1f3-716f-4fb8-9070-d321b39ffcb3 ro console=hvc0 BOOTIF=01-6c-ae-8b-6a-a0-88 quiet RelatedPackageVersions: - linux-restricted-modules-3.13.0-35-generic N/A - linux-backports-modules-3.13.0-35-generic N/A - linux-firmware 1.127.6 + linux-restricted-modules-3.13.0-35-generic N/A + linux-backports-modules-3.13.0-35-generic N/A + linux-firmware 1.127.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1371634 Title: block devices appear twice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1371634/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1371634] Re: block devices appear twice
** Description changed: - $ sudo blkid - /dev/sr0: LABEL=Ubuntu-Server 14.04 LTS ppc64el TYPE=iso9660 - /dev/sda2: UUID=795a6e14-ea4e-4718-9e98-c6df3696920c TYPE=ext4 - /dev/sda3: UUID=0a91d81f-6a16-4b96-a92c-11ca8bdc4bf4 TYPE=swap - /dev/sdb2: UUID=1d14c1f3-716f-4fb8-9070-d321b39ffcb3 TYPE=ext4 - /dev/sdb3: UUID=9c228177-d65c-4d19-a462-db1891e9781e TYPE=swap - /dev/sdg2: UUID=795a6e14-ea4e-4718-9e98-c6df3696920c TYPE=ext4 - /dev/sdg3: UUID=0a91d81f-6a16-4b96-a92c-11ca8bdc4bf4 TYPE=swap - /dev/sdh2: UUID=1d14c1f3-716f-4fb8-9070-d321b39ffcb3 TYPE=ext4 - /dev/sdh3: UUID=9c228177-d65c-4d19-a462-db1891e9781e TYPE=swap + $ sudo blkid + /dev/sr0: LABEL=Ubuntu-Server 14.04 LTS ppc64el TYPE=iso9660 + /dev/sda2: UUID=795a6e14-ea4e-4718-9e98-c6df3696920c TYPE=ext4 + /dev/sda3: UUID=0a91d81f-6a16-4b96-a92c-11ca8bdc4bf4 TYPE=swap + /dev/sdb2: UUID=1d14c1f3-716f-4fb8-9070-d321b39ffcb3 TYPE=ext4 + /dev/sdb3: UUID=9c228177-d65c-4d19-a462-db1891e9781e TYPE=swap + /dev/sdg2: UUID=795a6e14-ea4e-4718-9e98-c6df3696920c TYPE=ext4 + /dev/sdg3: UUID=0a91d81f-6a16-4b96-a92c-11ca8bdc4bf4 TYPE=swap + /dev/sdh2: UUID=1d14c1f3-716f-4fb8-9070-d321b39ffcb3 TYPE=ext4 + /dev/sdh3: UUID=9c228177-d65c-4d19-a462-db1891e9781e TYPE=swap I'm not sure what exactly those block devices are (as in if they're raided in hardware or they actually represent physical spinning disks). But I do know that writing data to sda causes that data to be readable from sdg. The same is true: - sda - sdg - sdb - sdh + sda - sdg + sdb - sdh That is what causes those UUIDs to be similar. Everything is functional, you just have to know that if your root device is /dev/sdg that you should probably not write data to /dev/sda thinking you can use it as a disk. + + Related bugs: + * bug 1432062: multipath-tools-boot: support booting without user_friendly_names on devices with spaces in identifiers + ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-35-generic 3.13.0-35.62 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic ppc64le AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.4 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: Error: [Errno 2] No such file or directory: 'iw' CurrentDmesg: [ 88.736220] init: plymouth-upstart-bridge main process ended, respawning Date: Fri Sep 19 14:31:20 2014 HibernationDevice: RESUME=UUID=9c228177-d65c-4d19-a462-db1891e9781e Lsusb: - Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub - Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub - Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub - Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProcEnviron: - TERM=screen - PATH=(custom, no user) - XDG_RUNTIME_DIR=set - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=screen + PATH=(custom, no user) + XDG_RUNTIME_DIR=set + LANG=en_US.UTF-8 + SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: root=UUID=1d14c1f3-716f-4fb8-9070-d321b39ffcb3 ro console=hvc0 BOOTIF=01-6c-ae-8b-6a-a0-88 quiet RelatedPackageVersions: - linux-restricted-modules-3.13.0-35-generic N/A - linux-backports-modules-3.13.0-35-generic N/A - linux-firmware 1.127.6 + linux-restricted-modules-3.13.0-35-generic N/A + linux-backports-modules-3.13.0-35-generic N/A + linux-firmware 1.127.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) -- 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/1371634 Title: block devices appear twice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1371634/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1371634] Re: block devices appear twice
OK, so for trivial workaround fix, you can do:
a.) install with curtin as you have
b.) sudo apt-get install multipath-tools-boot
c.) printf defaults {\n\tuser_friendly_names yes\n}\n | sudo tee
/etc/multipath.conf
d.) sudo update-initramfs -u -k all
e.) sudo reboot
You'll come back up with multipath as the root device.
Oleg is working on a merge proposal for curtin that will do that by
default.
When the fix for bug 1432062 lands, then we wont even specifically need
the user_friendly_names patch.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1371634
Title:
block devices appear twice
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1371634/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1371634] Re: block devices appear twice
OK, so for trivial workaround fix, you can do:
a.) install with curtin as you have
b.) sudo apt-get install multipath-tools-boot
c.) printf defaults {\n\tuser_friendly_names yes\n}\n | sudo tee
/etc/multipath.conf
d.) sudo update-initramfs -u -k all
e.) sudo reboot
You'll come back up with multipath as the root device.
Oleg is working on a merge proposal for curtin that will do that by
default.
When the fix for bug 1432062 lands, then we wont even specifically need
the user_friendly_names patch.
--
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/1371634
Title:
block devices appear twice
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1371634/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1371634] Re: block devices appear twice
this script attempts to do the following for img=working.img device=/dev/working0 img=broken.img device='/dev/broken 0' - create a file $img - partition it with sfdisk - losetup a device pointing to $img - kpartx -a -v -p -part $LODEV run the script and you can see, it will work for 'working0' and fail for 'broken 0' $ sudo ./show === img=working.img devname=/dev/working0 lodev=/dev/loop1 === add map working0-part1 (252:0): 0 202752 linear /dev/working0 2048 === 0 == brw-rw 3 root disk 7, 1 Jun 3 20:46 /dev/working0 === img=broken.img devname=/dev/broken 0 lodev=/dev/loop0 === device-mapper: reload ioctl on broken\x200-part1 failed: Invalid argument create/reload failed on broken 0-part1 add map broken 0-part1 (0:0): 0 202752 linear /dev/broken 0 2048 === 1 == brw-rw 2 root disk 7, 0 Jun 3 20:46 /dev/broken 0 failed kpartx to /dev/broken 0 that is basically the same way the multipath-boot setup fails. ** Attachment added: show-kpartx-bug https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1371634/+attachment/4409447/+files/show-kpartx-bug -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1371634 Title: block devices appear twice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1371634/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1371634] Re: block devices appear twice
this script attempts to do the following for img=working.img device=/dev/working0 img=broken.img device='/dev/broken 0' - create a file $img - partition it with sfdisk - losetup a device pointing to $img - kpartx -a -v -p -part $LODEV run the script and you can see, it will work for 'working0' and fail for 'broken 0' $ sudo ./show === img=working.img devname=/dev/working0 lodev=/dev/loop1 === add map working0-part1 (252:0): 0 202752 linear /dev/working0 2048 === 0 == brw-rw 3 root disk 7, 1 Jun 3 20:46 /dev/working0 === img=broken.img devname=/dev/broken 0 lodev=/dev/loop0 === device-mapper: reload ioctl on broken\x200-part1 failed: Invalid argument create/reload failed on broken 0-part1 add map broken 0-part1 (0:0): 0 202752 linear /dev/broken 0 2048 === 1 == brw-rw 2 root disk 7, 0 Jun 3 20:46 /dev/broken 0 failed kpartx to /dev/broken 0 that is basically the same way the multipath-boot setup fails. ** Attachment added: show-kpartx-bug https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1371634/+attachment/4409447/+files/show-kpartx-bug -- 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/1371634 Title: block devices appear twice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1371634/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1371634] Re: block devices appear twice
also just now verified that it is broken in debian's unstable version also (0.5.0-7) -- 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/1371634 Title: block devices appear twice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1371634/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1371634] Re: block devices appear twice
verified the attached script also fails on both trusty and wily trusty: 0.4.9-3ubuntu7.2 wily: 0.4.9-3ubuntu12 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1371634 Title: block devices appear twice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1371634/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1371634] Re: block devices appear twice
verified the attached script also fails on both trusty and wily trusty: 0.4.9-3ubuntu7.2 wily: 0.4.9-3ubuntu12 -- 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/1371634 Title: block devices appear twice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1371634/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1371634] Re: block devices appear twice
also just now verified that it is broken in debian's unstable version also (0.5.0-7) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1371634 Title: block devices appear twice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1371634/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1371634] Re: block devices appear twice
Ok, so Oleg and I were looking at a solution, and figured we'd give the maybe
it just works path a try.
I installed a system, it installed onto /dev/sda (as this bug shows).
I then 'apt-get install multipath-tools-boot'
I rebooted, with the 'root=LABEL=cloudimg-rootfs' on the cmdline (as
normal). It died in initramfs unable to find root. The full bootlog at
http://paste.ubuntu.com/11547135/ .
The multipath-tools-boot package puts some code into the initramfs
(/usr/share/initramfs-tools/scripts/local-top/multipath) that does this:
| if [ -x /sbin/kpartx -a -x /sbin/dmsetup ]; then
| /sbin/dmsetup ls --target multipath --exec /sbin/kpartx -a -p -part
/dev/null
| fi
That looks all well and good.
In the initramfs I did some debugging:
(initramfs) /sbin/dmsetup ls --target multipath
1IBM IPR-0 5EC2A9A0 (252, 1)
1IBM IPR-0 5EC2A920 (252, 2)
1IBM IPR-0 5EC2A980 (252, 5)
1IBM IPR-0 5EC2A960 (252, 3)
1IBM IPR-0 5EC2A9C0 (252, 4)
1IBM IPR-0 5EC2A940 (252, 0)
And then further debug, I find that dmsetup is calling kpartx seemingly
correctly, but kpartx is I think messing up.
I was able to fix this by booting with:
root=UUID=f7c3b31d-3411-420e-a57d-9318e43248ba ro console=hvc0
break=post-multipath
Then doing:
(initramfs) cat /tmp/myprog
#!/bin/sh
tgt=$1
fixed=$(echo $tgt | sed 's, ,\\x20,g')
{
echo input: '$tgt'
echo fixed: '$fixed'
echo /sbin/kpartx -a -v -p -part $fixed
/sbin/kpartx -a -v -p -part $fixed
ret=$?
echo $ret
} /tmp/log 21
exit $ret
(initramfs) rm /tmp/log
(initramfs) /sbin/dmsetup ls --target multipath --exec /bin/myprog
(initramfs) cat /tmp/log
input: '/dev/mapper/1IBM IPR-0 5EC2A9A0'
fixed: '/dev/mapper/1IBM\x20\x20\x20\x20\x20IPR-0\x20\x20\x205EC2A9A0'
/sbin/kpartx -a -v -p -part
/dev/mapper/1IBM\x20\x20\x20\x20\x20IPR-0\x20\x20\x205EC2A9A0
0
input: '/dev/mapper/1IBM IPR-0 5EC2A920'
fixed: '/dev/mapper/1IBM\x20\x20\x20\x20\x20IPR-0\x20\x20\x205EC2A920'
/sbin/kpartx -a -v -p -part
/dev/mapper/1IBM\x20\x20\x20\x20\x20IPR-0\x20\x20\x205EC2A920
0
input: '/dev/mapper/1IBM IPR-0 5EC2A980'
fixed: '/dev/mapper/1IBM\x20\x20\x20\x20\x20IPR-0\x20\x20\x205EC2A980'
/sbin/kpartx -a -v -p -part
/dev/mapper/1IBM\x20\x20\x20\x20\x20IPR-0\x20\x20\x205EC2A980
add map 1IBM IPR-0 5EC2A980-part1 (252:6): 0 16384 linear
/dev/mapper/1IBM\x20\x20\x20\x20\x20IPR-0\x20\x20\x205EC2A980 2048
add map 1IBM IPR-0 5EC2A980-part2 (252:7): 0 554268639 linear
/dev/mapper/1IBM\x20\x20\x20\x20\x20IPR-0\x20\x20\x205EC2A980 18432
0
input: '/dev/mapper/1IBM IPR-0 5EC2A960'
fixed: '/dev/mapper/1IBM\x20\x20\x20\x20\x20IPR-0\x20\x20\x205EC2A960'
/sbin/kpartx -a -v -p -part
/dev/mapper/1IBM\x20\x20\x20\x20\x20IPR-0\x20\x20\x205EC2A960
0
input: '/dev/mapper/1IBM IPR-0 5EC2A9C0'
fixed: '/dev/mapper/1IBM\x20\x20\x20\x20\x20IPR-0\x20\x20\x205EC2A9C0'
/sbin/kpartx -a -v -p -part
/dev/mapper/1IBM\x20\x20\x20\x20\x20IPR-0\x20\x20\x205EC2A9C0
0
input: '/dev/mapper/1IBM IPR-0 5EC2A940'
fixed: '/dev/mapper/1IBM\x20\x20\x20\x20\x20IPR-0\x20\x20\x205EC2A940'
/sbin/kpartx -a -v -p -part
/dev/mapper/1IBM\x20\x20\x20\x20\x20IPR-0\x20\x20\x205EC2A940
Then ... after that, I have the devices I needed:
(initramfs) blkid
/dev/sda2: LABEL=cloudimg-rootfs UUID=f7c3b31d-3411-420e-a57d-9318e43248ba
TYPE=ext4
/dev/sdg2: LABEL=cloudimg-rootfs UUID=f7c3b31d-3411-420e-a57d-9318e43248ba
TYPE=ext4
/dev/mapper/1IBM\x20\x20\x20\x20\x20IPR-0\x20\x20\x205EC2A980-part2:
LABEL=cloudimg-rootfs UUID=f7c3b31d-3411-420e-a57d-9318e43248ba TYPE=ext4
I exited from there, the remaining boot took over, and mounted the device
mapper device as /.
All happy.
So, if there weren't a bug in kpartx we'd have a very easy solution in just
installing the multipath-tools-boot package.
That said, it looks like user_friendly_names in /etc/multipath.conf might be
relevant.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1371634
Title:
block devices appear twice
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1371634/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1371634] Re: block devices appear twice
Ok, so Oleg and I were looking at a solution, and figured we'd give the maybe
it just works path a try.
I installed a system, it installed onto /dev/sda (as this bug shows).
I then 'apt-get install multipath-tools-boot'
I rebooted, with the 'root=LABEL=cloudimg-rootfs' on the cmdline (as
normal). It died in initramfs unable to find root. The full bootlog at
http://paste.ubuntu.com/11547135/ .
The multipath-tools-boot package puts some code into the initramfs
(/usr/share/initramfs-tools/scripts/local-top/multipath) that does this:
| if [ -x /sbin/kpartx -a -x /sbin/dmsetup ]; then
| /sbin/dmsetup ls --target multipath --exec /sbin/kpartx -a -p -part
/dev/null
| fi
That looks all well and good.
In the initramfs I did some debugging:
(initramfs) /sbin/dmsetup ls --target multipath
1IBM IPR-0 5EC2A9A0 (252, 1)
1IBM IPR-0 5EC2A920 (252, 2)
1IBM IPR-0 5EC2A980 (252, 5)
1IBM IPR-0 5EC2A960 (252, 3)
1IBM IPR-0 5EC2A9C0 (252, 4)
1IBM IPR-0 5EC2A940 (252, 0)
And then further debug, I find that dmsetup is calling kpartx seemingly
correctly, but kpartx is I think messing up.
I was able to fix this by booting with:
root=UUID=f7c3b31d-3411-420e-a57d-9318e43248ba ro console=hvc0
break=post-multipath
Then doing:
(initramfs) cat /tmp/myprog
#!/bin/sh
tgt=$1
fixed=$(echo $tgt | sed 's, ,\\x20,g')
{
echo input: '$tgt'
echo fixed: '$fixed'
echo /sbin/kpartx -a -v -p -part $fixed
/sbin/kpartx -a -v -p -part $fixed
ret=$?
echo $ret
} /tmp/log 21
exit $ret
(initramfs) rm /tmp/log
(initramfs) /sbin/dmsetup ls --target multipath --exec /bin/myprog
(initramfs) cat /tmp/log
input: '/dev/mapper/1IBM IPR-0 5EC2A9A0'
fixed: '/dev/mapper/1IBM\x20\x20\x20\x20\x20IPR-0\x20\x20\x205EC2A9A0'
/sbin/kpartx -a -v -p -part
/dev/mapper/1IBM\x20\x20\x20\x20\x20IPR-0\x20\x20\x205EC2A9A0
0
input: '/dev/mapper/1IBM IPR-0 5EC2A920'
fixed: '/dev/mapper/1IBM\x20\x20\x20\x20\x20IPR-0\x20\x20\x205EC2A920'
/sbin/kpartx -a -v -p -part
/dev/mapper/1IBM\x20\x20\x20\x20\x20IPR-0\x20\x20\x205EC2A920
0
input: '/dev/mapper/1IBM IPR-0 5EC2A980'
fixed: '/dev/mapper/1IBM\x20\x20\x20\x20\x20IPR-0\x20\x20\x205EC2A980'
/sbin/kpartx -a -v -p -part
/dev/mapper/1IBM\x20\x20\x20\x20\x20IPR-0\x20\x20\x205EC2A980
add map 1IBM IPR-0 5EC2A980-part1 (252:6): 0 16384 linear
/dev/mapper/1IBM\x20\x20\x20\x20\x20IPR-0\x20\x20\x205EC2A980 2048
add map 1IBM IPR-0 5EC2A980-part2 (252:7): 0 554268639 linear
/dev/mapper/1IBM\x20\x20\x20\x20\x20IPR-0\x20\x20\x205EC2A980 18432
0
input: '/dev/mapper/1IBM IPR-0 5EC2A960'
fixed: '/dev/mapper/1IBM\x20\x20\x20\x20\x20IPR-0\x20\x20\x205EC2A960'
/sbin/kpartx -a -v -p -part
/dev/mapper/1IBM\x20\x20\x20\x20\x20IPR-0\x20\x20\x205EC2A960
0
input: '/dev/mapper/1IBM IPR-0 5EC2A9C0'
fixed: '/dev/mapper/1IBM\x20\x20\x20\x20\x20IPR-0\x20\x20\x205EC2A9C0'
/sbin/kpartx -a -v -p -part
/dev/mapper/1IBM\x20\x20\x20\x20\x20IPR-0\x20\x20\x205EC2A9C0
0
input: '/dev/mapper/1IBM IPR-0 5EC2A940'
fixed: '/dev/mapper/1IBM\x20\x20\x20\x20\x20IPR-0\x20\x20\x205EC2A940'
/sbin/kpartx -a -v -p -part
/dev/mapper/1IBM\x20\x20\x20\x20\x20IPR-0\x20\x20\x205EC2A940
Then ... after that, I have the devices I needed:
(initramfs) blkid
/dev/sda2: LABEL=cloudimg-rootfs UUID=f7c3b31d-3411-420e-a57d-9318e43248ba
TYPE=ext4
/dev/sdg2: LABEL=cloudimg-rootfs UUID=f7c3b31d-3411-420e-a57d-9318e43248ba
TYPE=ext4
/dev/mapper/1IBM\x20\x20\x20\x20\x20IPR-0\x20\x20\x205EC2A980-part2:
LABEL=cloudimg-rootfs UUID=f7c3b31d-3411-420e-a57d-9318e43248ba TYPE=ext4
I exited from there, the remaining boot took over, and mounted the device
mapper device as /.
All happy.
So, if there weren't a bug in kpartx we'd have a very easy solution in just
installing the multipath-tools-boot package.
That said, it looks like user_friendly_names in /etc/multipath.conf might be
relevant.
--
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/1371634
Title:
block devices appear twice
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1371634/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1371634] Re: block devices appear twice
Sorry for the vague comment earlier. What I meant was that, from a certification point of view, I can't certify a system that ships by default with dual RAID cards in a multipath configuration when Multipathing in Ubuntu doesn't work. That leads to a scenario where, out of the box on a fresh install you can destroy your own root filesystem by formatting a drive that you don't realize is actually your root fs... In other words, it is very easy to destroy data accidentally if you're unaware that sde and sda are the same physical device, as you would reasonably expect those to be separate devices. -- 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/1371634 Title: block devices appear twice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1371634/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1371634] Re: block devices appear twice
Sorry for the vague comment earlier. What I meant was that, from a certification point of view, I can't certify a system that ships by default with dual RAID cards in a multipath configuration when Multipathing in Ubuntu doesn't work. That leads to a scenario where, out of the box on a fresh install you can destroy your own root filesystem by formatting a drive that you don't realize is actually your root fs... In other words, it is very easy to destroy data accidentally if you're unaware that sde and sda are the same physical device, as you would reasonably expect those to be separate devices. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1371634 Title: block devices appear twice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1371634/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1371634] Re: block devices appear twice
I'm setting this to High for now... I really think this is critical as it is gating the PowerNV certification work. ** Changed in: multipath-tools (Ubuntu) Importance: Undecided = High ** Changed in: curtin (Ubuntu) Importance: Undecided = High ** Changed in: curtin (Ubuntu) Importance: High = Critical ** Changed in: multipath-tools (Ubuntu) Importance: High = Critical -- 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/1371634 Title: block devices appear twice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1371634/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1371634] Re: block devices appear twice
Actually, on advice of Andy C, lets go ahead and consider this critical... this cert needs to be completed as soon as possible and we can't do that without multipathing working properly. -- 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/1371634 Title: block devices appear twice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1371634/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1371634] Re: block devices appear twice
Actually, on advice of Andy C, lets go ahead and consider this critical... this cert needs to be completed as soon as possible and we can't do that without multipathing working properly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1371634 Title: block devices appear twice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1371634/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1371634] Re: block devices appear twice
I'm setting this to High for now... I really think this is critical as it is gating the PowerNV certification work. ** Changed in: multipath-tools (Ubuntu) Importance: Undecided = High ** Changed in: curtin (Ubuntu) Importance: Undecided = High ** Changed in: curtin (Ubuntu) Importance: High = Critical ** Changed in: multipath-tools (Ubuntu) Importance: High = Critical -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1371634 Title: block devices appear twice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1371634/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1371634] Re: block devices appear twice
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: curtin (Ubuntu) Status: New = Confirmed -- 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/1371634 Title: block devices appear twice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1371634/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1371634] Re: block devices appear twice
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: multipath-tools (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/1371634 Title: block devices appear twice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1371634/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1371634] Re: block devices appear twice
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: multipath-tools (Ubuntu) Status: New = Confirmed -- 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/1371634 Title: block devices appear twice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1371634/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1371634] Re: block devices appear twice
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: curtin (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/1371634 Title: block devices appear twice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1371634/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1371634] Re: block devices appear twice
Quickly reading over the report I would think this is a result of the installer bug I reported as bug #1447167. The problem is that if you configure a system for multipath, it will present each path as an independent drive. And that causes a lot of confusion when a system has data on those and comes up without the multipath tools installed. To the OS this looks like multiple disks having the same filesystem UUIDs which conflict when creating disk-by/... links in /dev. Even worse LVM finds two PVs with the same ID and bails (iirc). I theory (with a lot knowledge and care) it is possible to install single-path and convert the whole system to multipath later. But frankly I think when the installer was told to enable multipath detect, it should automatically install the tools. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1371634 Title: block devices appear twice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1371634/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1371634] Re: block devices appear twice
Quickly reading over the report I would think this is a result of the installer bug I reported as bug #1447167. The problem is that if you configure a system for multipath, it will present each path as an independent drive. And that causes a lot of confusion when a system has data on those and comes up without the multipath tools installed. To the OS this looks like multiple disks having the same filesystem UUIDs which conflict when creating disk-by/... links in /dev. Even worse LVM finds two PVs with the same ID and bails (iirc). I theory (with a lot knowledge and care) it is possible to install single-path and convert the whole system to multipath later. But frankly I think when the installer was told to enable multipath detect, it should automatically install the tools. -- 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/1371634 Title: block devices appear twice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1371634/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1371634] Re: block devices appear twice
Related/possibly duplicate bug is bug 1447167. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1371634 Title: block devices appear twice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1371634/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1371634] Re: block devices appear twice
Related/possibly duplicate bug is bug 1447167. -- 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/1371634 Title: block devices appear twice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1371634/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1371634] Re: block devices appear twice
** Also affects: curtin (Ubuntu) Importance: Undecided Status: New ** Also affects: multipath-tools (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: Confirmed = Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to curtin in Ubuntu. https://bugs.launchpad.net/bugs/1371634 Title: block devices appear twice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1371634/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1371634] Re: block devices appear twice
** Also affects: curtin (Ubuntu) Importance: Undecided Status: New ** Also affects: multipath-tools (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: Confirmed = Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1371634 Title: block devices appear twice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1371634/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1371634] Re: block devices appear twice
This is a multipath issue. The box has two cards with redundant paths to each disk. Multipath is meant to create /dev/mapper/mpath* devices, and the installer should use them instead of the underlying /dev/sd* devices. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1371634 Title: block devices appear twice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1371634/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1371634] Re: block devices appear twice
Joseph, I honestly don't know how the systems are set up. I suspect you're right, that there are 2 physical disks raided together. I don't think that changes the bug at all though. The kernel should only show me one of those devices, right? If I configured hardware raid to show 2 disks as 1 in raid 1 I certainly wouldn't expect to have to know that from user-space (I'm kind of surprised the *kernel* ever see the individual disks there). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1371634 Title: block devices appear twice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1371634/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1371634] Re: block devices appear twice
** Changed in: linux (Ubuntu) Importance: Undecided = Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1371634 Title: block devices appear twice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1371634/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1371634] Re: block devices appear twice
It looks like you have a couple of RAID controllers in the machine. Do you have them configured with and volumes, etc? 0003:04:00.0 RAID bus controller [0104]: IBM PCI-E IPR SAS Adapter (ASIC) [1014:034a] (rev 01) Subsystem: IBM PCIe3 x8 Cache SAS RAID Internal Adapter 6Gb (57D8) [1014:03fe]0003:04:00.0 RAID bus controller [0104]: IBM PCI-E IPR SAS Adapter (ASIC) [1014:034a] (rev 01) Subsystem: IBM PCIe3 x8 Cache SAS RAID Internal Adapter 6Gb (57D8) [1014:03fe] ** Tags added: kernel-da-key -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1371634 Title: block devices appear twice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1371634/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
