From: Colin Watson Date: Thu, 11 Jul 2019 11:26:11 +0000 (+0100) Subject: grub2-boot-problems: Fix formatting X-Git-Url: https://www.chiark.greenend.org.uk/ucgi/~cjwatson/git?a=commitdiff_plain;h=b7824f6b9025c52702c3afe1723581abbac861ad;p=blog.git grub2-boot-problems: Fix formatting --- diff --git a/content/grub2-boot-problems.md b/content/grub2-boot-problems.md index 0cbaa8d8..ffe731a6 100644 --- a/content/grub2-boot-problems.md +++ b/content/grub2-boot-problems.md @@ -27,10 +27,10 @@ on the same disk as the boot sector. This core image then figures out where to find /boot/grub, and loads grub.cfg from it as well as more GRUB modules. The thing that tends to go wrong here is that the core image must be from -the same version of GRUB as any modules it loads. /boot/grub/*.mod are +the same version of GRUB as any modules it loads. `/boot/grub/*.mod` are updated only by grub-install, so this normally works OK. However, for various reasons (deliberate or accidental) some people install GRUB to -multiple disks. In this case, grub-install might update /boot/grub/*.mod +multiple disks. In this case, grub-install might update `/boot/grub/*.mod` along with the core image on one disk, but your BIOS might actually be booting from a different disk. The effect of this will be that you'll have an old core image and new modules, which will probably blow up in any number