I think you could be right. For no good reason I'd commented out the line #UUID=9d6412d7-0277-4b1e-b56e-76eb9fb7e898 / ext3 errors=remount-ro 0 1 on the source partition, so the new one was the same.
Nothing else was effected, the old one still booted ok, so I didn't notice. The interesting thing is that it seems grub2 didn't find that line (unless it did a grep /), so I spose it then just kept the old "linux /boot/vml..." line. I don't spose we can really call this a bug then - software writers can't be expected to cope with every unusual dumb thing that people might do. Thanks for your help. Garry -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1012025 Title: update-grub not reading UUID's properly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1012025/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
