I freshly installed F17 on a SSD (/dev/sda1) which worked fine.
Next I installed Ubuntu on /dev/sda3, my intention was to create a multiboot system. After rebooting grub failed with an error message "unknown filesystem". Using the F17 CD I could restore grub2 to boot into F17 again.
My problem: within F17 I created a new grub.conf by calling grub2-mkconfig. The second system (Ubuntu) was detected correctly, and a grub2-entry with the correct UUID of /dev/sda3 was added to grub.conf. But now when I try to boot into Ubuntu, after selecting the Ubuntu-menuentry, I get following error messages:
error: no such device <UUID of /dev/sda3>
error: unknown filesystem
error: you need to load the kernel first
What I tried next:
- I defined GRUB_DISABLE_LINUX_UUID=”true” in /etc/default/grub to avoid that grub2-mkconfig creates menuentries with UUID - but that did not change anything, the UUIDs are still used instead of device names.
- I checked the filesystem on /dev/sda3, it is correct and readable, so no reason fror grub2 to not to use it.
So how can I solve this? I'm really not happy with the way too complex syntax of grub2 configuration (which is impossible to be edited manually since that very often leads to a non-bootable system because grub2 stops using it without any error message). And I'm really not happy with the fact that grub2-mkconfig creates entries that do not work!