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

[Ing. Josef Klotzner]

Btw: i like Your Atari logo ... i am still owning a Mega STE and a Falcon,
which i had to repair last time as battery of battery buffered NVRAM was
dead. Now it still and again is alive !!  :D


2013/8/24 Josef Klotzner <josef.klotzner at gmail.com>

> Sorry, but in the moment it will not be a good idea to destroy my RAID
> again only to know, if this would work also with new install.
> I have several OS Systems on the Raid besides ~ 1 TB data.
> It would take me days of work to test and bring my machine back to state
> of before via Backup.
> I need it currently every day an am not able to.
>
> I have already tested was P. Susi created to fix that bug. You can trust
> it works and implement as it is.
> Fact is: if you don't implement susi's fix ubuntu installs will still
> TOTALLY fail if you want to install on extended partitions of a Raid. If
> you implement it only can improve.
>
> What i can imagine to do, is to test with a life CD, updated to include
> fix, if the Raid is mounted and accessible, because either this did not
> work properly as far as i can remember. But please don't ask me to destroy
> my RAID for a further test. Thank You.
>
> kind regards
> Josef
>
>
> 2013/8/18 Launchpad Bug Tracker <1093918 at bugs.launchpad.net>
>
>> ** Branch linked: lp:~ubuntu-branches/ubuntu/precise/multipath-tools
>> /precise-proposed
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> 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
>>
>
>

-- 
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