I can also confirm that I have this bug. Editing out the --search part of the boot line gives me a working system. However... I just did some updates and part of the update was a new kernel linux-2.6.31-16-generic. After the updates my system reboots and instead of encountering the error listed above I now end up with just a "sh:grub>" line. If I manually type in my boot parameters I can get the system to boot.
After playing around trying to fix that issue somehow my whole boot record or something got hosed because eventually my system started booting to just a "initramfs>" prompt. I tried using the Super Grub Boot Disk to recover the MBR but it was unable to do anything to the disk (not sure why it couldn't. Even Puppy Linux from a USB flash drive was unable to mount the hard disk any more). I eventually gave up and formatted the disk. Of course now that I have re-installed Mythbuntu and grabbed all of the updates I am back to the "sh:grub>" error. The annoying thing is Grub2 will NOT give me a menu to go to with this error that I could simply edit to fix the offending lines. Instead I have to manually type everything in. Not fun when you have to do it 20 times over the course of an hour trying to figure out how to fix this issue. I am not sure if these two issues are related or completely different but I thought I would add it just in case. This is on two clean installs of Mythbuntu 9.10 by the way... The first time my Mythbox was all configured and set so you can imagine the frustration when I lost all of that work. -- Grub 2 problem, error: no such device https://bugs.launchpad.net/bugs/403408 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
