Why have a function in a script, and then tell people not to use it? Or, later on, stop mentioning it at all even though it still is there?
Apparently, someone thought that option, which usually and mostly worked in the past, should not be mentioned any more, and people instead can just thrash around for an answer. The early versions of GRUB 2 produced a warning message that actually said to use the -force option if we really really wanted to. The -force option usually overcomes all of the objections and it works okay. So GRUB 2's grub-install script will always halt and spew the message when that is attempted. There is no place in a partition for it to go. P.S.: Just FYI, core.img can never be embedded when we attempt to install GRUB 2 in a partition boot sector (like you did in post #5). But we've been using blocklists in blissful ignorance with Legacy GRUB for years and mostly without issues. But instead of actually coming up with a better idea (than embedding) for GRUB 2, the GRUB developers made grub-install (or grub2-install in Fedora) halt and spew warnings that confuse everybody. But we never knew because Legacy GRUB never stopped to discuss the situation with us like GRUB 2 does. We have lived with a very similar situation for years with Legacy GRUB and stage1.5. The GRUB developers consider that unreliable meaning it is vulnerable to breakage if the file /boot/grub/core.img gets moved to different sectors. It causes grub2-install to skip attempting to embed core.img in that area between the master boot record and first partition, and instead gives boot.img the sector address of the file named core.img in /boot/grub of the filesystem. When core.img doesn't fit in the preferred location, an easy thing to try is the -force option of the grub2-install command. In some situations, core.img does not fit in the sectors between the MBR and first partition. Boot.img then loads and executes core.img. That's important because boot.img, which is the part of GRUB 2 located in the master boot record and runs first, finds core.img by its sector address. That area is the preferred location for core.img because it is outside of a filesystem and safe from being moved by filesystem activities.
It normally gets embedded in the unused sectors between the master boot record and the first partition. It varies in size as required by each situation.
0 kommentar(er)
