@John: You may want to open a Question on Launchpad Questions for your particular case, so as to avoid creating noise on this bug.
In response to your query: Try hd(0,4) or hd(0,5) -- if you created a "logical" partition, the partition numbers start at 4 (counting from 0, e.g. hd(0,4)) or 5 (counting from one, e.g. sda5). Basically you need to give grub the ID of your separate /boot, not of the root ubuntu partition itself. Alternatively, if you can boot the Live CD mode of the installer, you can mount your new install and do a "chroot" into the install, and then run the update from the command line to install the new grub packages. Then you can run update-grub. One other thing -- if you have a copy of the old menu.lst file (perhaps called menu.lst~ or something) in /boot/grub (if you have a seperate /boot, look for a small ext partition with a folder called "grub" in it) -- you can try moving the current menu.lst to something like menu.lst.broken and then copying the old menu.lst back in place. Note that this will likely put you back in the hardy kernel instead of the intrepid one, so you will want to run a dist upgrade again once you get it to boot. -- UUID conversion fails to handle separate /boot https://bugs.launchpad.net/bugs/285269 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
