From bb0523f038e600a645380c0540726f70ed3e2070 Mon Sep 17 00:00:00 2001 From: Arne Wiebalck Date: Fri, 2 Jul 2021 16:58:10 +0200 Subject: [PATCH] [doc] Bootloader reinstallations on Software RAID Add a section to the docs how to handle grub reinstallations with Ironic software RAID on BIOS nodes, e.g. during disk replacements. Change-Id: I2c1d1a61a3340f6785ab6f63cb96f2c045f8eabe --- doc/source/admin/raid.rst | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/doc/source/admin/raid.rst b/doc/source/admin/raid.rst index 5930b45740..7d9c87a07d 100644 --- a/doc/source/admin/raid.rst +++ b/doc/source/admin/raid.rst @@ -408,6 +408,15 @@ There are certain limitations to be aware of: are installed or the bootloader is updated, so measures to keep these partitions in sync need to be taken. +* In BIOS mode, the Ironic Python Agent installs the boot loader onto all + disks. While nothing is required for kernel or grub package updates, + re-installing the bootloader on one disk, e.g. during a disk replacement, + may require to re-install the bootloader on all disks. Otherwise, there + is a risk of an incompatibility of the grub components stored on the device + (i.e. stage1/boot.img in the MBR and stage1.5/core.img in the MBR gap) with + the ones stored in /boot (stage2). This incompatibility can render the node + unbootable if the wrong disk is selected for booting. + Image requirements ------------------