I've just been bitten by this yet again. I have been struggling with this for a long time:
http://ubuntuforums.org/showthread.php?t=457135 This time the kernel upgrade changed everything to a UUID that was listed in #kopt, ignoring the setting in #groot. I have the Grub manual and other documentation, but I can't figure out what the priority between the two lines is. In this case the UUID in #kopt was bogus, so rebooting after the kernel upgrade dumped me to an intramfs prompt. I also don't understand how the bogus UUID got into the #kopt line in the first place. And I can't find any documentation on how to write something in the #kopt line that will tell the update script where the root partition is, or tell it to ignore #kopt. I have to add my voice here -- I don't care how "logical" the existing code is and I don't care about philosophical issues. Leaving the user's computer unbootable is simply not acceptable. I participate in a local Linux user group. We hold Linux Clinics where we help people transition from "that other operating system" to Linux. Mostly we help new users install Linux on their computers, and we always push Ubuntu as our first suggestion. We hand out dozens of Ubuntu CDs every month. I hate it when something like this happens to one of our new users. This "bug" has been around for too long. -- edgy update-grub destroys kopt https://bugs.launchpad.net/bugs/62195 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
