Because I had a very similar problem, I just worked through your attachment. Some remarks:
* First I think, the relevant booting disk is sdd2, not sdb, as you wrote. Neither sdb1/boot/grub/menu.lst nor sdb1/boot/grub/grub.cfg contains entries refering to a OS on sdh, but sdd2/boot/grub/grub.cfg does. * The UUIDs in sdd2/boot/grub/grub.cfg (lines 950/959 in the attachment) are correct. * Instead, the parameter root=/dev/sda2 in sdd2/boot/grub/grub.cfg (lines 951/960 in the attachment) is incorrect. But I think, this is not a bug of ubuntus os-prober. It seems to me, that the problem is in your Arch Linux boot configuration in sdh1/grub/menu.lst. See lines 1046/1047 and 1052/1053 in the attachment: There the wrong partitions/drives are set. I suppose, the os-prober just takes these entries without re-checking them. Try to correct sdh1/grub/menu.lst and then run update-grub on your ubuntu installation on sdd2. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1017542 Title: grub2 update-grub puts wrong UUID in grub.cfg for system with separate /, /boot partitions when detected by os-prober To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/os-prober/+bug/1017542/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
