Hi, thanks for that quick response. Is there any workaround for "Cannot read `/grub/core.img'"?
>> normally). -> Grub2 needed "grub-install /dev/sda5" to work again. >Should never happen if both the directory given with --root-directory is >the drive/partition you want and also the device you give grub-install. Might be related to grub-mkconfig allways writing to /boot/grub/device.map? >Though you should always install to MBR and not a bootsector. I found installing to MBR is no good with multiple installations (even if all are same distro). You get told "install into MBR" every time, every distro claims it to be its own MBR, and if it breaks you don't get into any system/grub prompt any more at all. Dedicated primary boot partition with bootflag set and chainloaded from a plain dos MBR is way easier to maintain. And when using "kernel /grub/core.img" in the dedicated grub partition to boot the grub2 installs from each distribution (instead of really chainloading the partitions) you actually don't even have to use a blocklist. (I guess that is what many dislike from installing into a partition?) -- failures on grub-install to create rescue boot media https://bugs.launchpad.net/bugs/498533 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
