http://lists.gnu.org/archive/html/grub-devel/2009-12/msg00095.html
Has a possible fix for this bug. If I understand the patch correctly it doesn't actually get search by UUID to succeed but makes it no longer a "fatal" error. So rather than the menu entry failing, the search --fs- uuid --set command will fail but allow the other commands to run. Since root was set first by drive and partition number if those are still correct then boot will succeed. There are two problems with this: 1: If you move your drives around then the hard coded device will be incorrect and booting will fail 2: Since this is caused by grub not being able to read the entire drive due to BIOS limitations, if you don't have a separate small /boot at the beginning of the drive you could run into problems later on even if things are work initially. For instance if you ever have a kernel update where the new kernel happens to be stored past what the BIOS can read that kernel will fail to boot. Similarly with a grub upgrade, with important files like the grub.cfg or modules being written past what the BIOS can read, grub could fail to load entirely. But it's still better than the current situation. It is basically the same as removing the search line for those with this BIOS limitation while allowing search by UUID for those without. This is all only true if I am understanding what the patch does correctly though :) -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
