grub-probe in the proposed package manages to actually use multipath's
/dev/mapper/* files.  Comparing /boot/grub/grub.cfg from this grub
package to the one using blkid in place of grub-probe produces the
following diff:

root@kickseed:/root# diff grub.cfg.new grub.cfg.serge
58,59c58
<       insmod ext2
<       set root='(hd5,1)'
---
>       insmod ext4
66,67c65
<       insmod ext2
<       set root='(hd5,1)'
---
>       insmod ext4
76,77c74
<       insmod ext2
<       set root='(hd5,1)'
---
>       insmod ext4
84,85c81
<       insmod ext2
<       set root='(hd5,1)'
---
>       insmod ext4
96,97c92
<       insmod ext2
<       set root='(hd5,1)'
---
>       insmod ext4
102,103c97
<       insmod ext2
<       set root='(hd5,1)'
---
>       insmod ext4

I'm having some trouble getting reliable good boots on the system, but I
don't think that's due to this grub package.  So as long as having
grub.cfg call an ext4 fs 'ext2' is ok (and adding the 'set root=' line,
for some reason) I would call this confirmed.

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

Title:
  when installer is multipath aware, grub fails to install

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to