Am Samstag, den 19.12.2009, 16:59 +0000 schrieb ceg: > Hi, thanks for that quick response. Is there any workaround for > "Cannot read `/grub/core.img'"?
Either make sure you don't need to use blocklists by using (g)parted to resize the first partition so there's enough room between MBR and it for core.img or make sure you don't need to use --root-directory= option. Else you need the lucid package or compile the karmic one yourself with a workaround for this. > >> 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? No. device.map isn't at all used during booting. Only the Utilities ever used it. > 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?) > If you only need core.img and don't care about the MBR/bootsector code you can use grub-install with --grub-setup=/bin/true which we use in the postinst if you choose to chainload GRUB 2 from GRUB Legacy. -- Felix Zielcke Proud Debian Maintainer and GNU GRUB developer -- 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 [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
