I think either linux-boot-prober or update-grub need a fix. As far as I remember, the point was that $mpoint/boot/grub/grub.cfg is not a reliable source of information. However, if you can do `mount $DEVICE $mpoint`, you can trust that $DEVICE correct, because the environment in which update-grub is called is mostly likely the new/current/correct one. At the very least, one could check if the "root" from linux-boot- prober is mountable and if not, fall back to what Peter's patch does.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/508901 Title: update-grub sets wrong root argument To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/508901/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
