I confirm that updating the UUID in the grub.cfg file of the other Linux installation (Arch linux) fixed the root device UUID inserted by os- prober on my Ubuntu.
The root UUID returned by the os-prober is not detected, but instead is taken from the existing grub.cfg of the detected Linux partition. Fixing the UUID in the Arch grub.cfg also made os-prober run just several seconds, compared to over a minute before (with the non-existing UUID). My assumption is that the UUID on the target system changed after I set a new partition label -- apparently setting/modifying a partition label changes its UUID. -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
