[Bug 1093918] Re: grub-probe auto-detection fails on raid

[Adam Conrad]

Hello Ing., or anyone else affected,

Accepted multipath-tools into precise-proposed. The package will build
now and be available at http://launchpad.net/ubuntu/+source/multipath-
tools/0.4.9-3ubuntu5.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: multipath-tools (Ubuntu Precise)
       Status: In Progress => Fix Committed

** Tags added: verification-needed

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1093918

Title:
  grub-probe auto-detection fails on raid

Status in “multipath-tools” package in Ubuntu:
  Fix Released
Status in “multipath-tools” source package in Precise:
  Fix Committed
Status in “multipath-tools” source package in Quantal:
  Triaged

Bug description:
  kpartx was mapping the entire extended partition then stacking the
  logical partitions on that device.  This exposes a device that
  otherwise appears to be an entire disk device containing the logical
  partitions, and this confuses grub.  The extended partition is
  supposed to only expose the first two sectors to allow LILO to be
  installed.

  The patch has been applied upstream now, and since this is the only
  change since quantal, a simple copy to quantal-updates should resolve
  it there as well.  I have done this in my ppa and the reporter has
  verified it has fixed the issue.

  TEST CASE:

  Use fdisk to create an extended parition either on a fakeraid disk or
  an LVM logical volume.  Run kpartx -a /dev/mapper/whatever to activate
  the partitions on the disk.  Assuming the extended partition is number
  3, then sudo blockdev --getsz /dev/mapper/whatever3 will report the
  apparent size of the extended partition.  The size should only be 2
  sectors regardless of the size of the extended partition.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1093918/+subscriptions