On 24Dec2021 12:09, Gordon Messmer <gordon.messmer@xxxxxxxxx> wrote:
>># install bootloader on new disk
>>grub2-install /dev/sdd1
>
>That looks wrong, it should probably be 'grub2-install /dev/sdd'.
>Additionally, it should be performed *after* adding the replacement
>disk to the RAID set, not before.
Is that true? My (blurry) mental model for this issue is that the boot
block isn't in the area maintained by the RAID, which is also the reason
that RAID1 doesn't automatically make all drives in the set bootable.
That suggests that you could do this before or after.
Can you explain what's going on here?
Aside: external ("hardware") RAIDs don't have this problem because they
present you a single logical drive - linux doesn't see the blocks
associated with marking the physicial drive RAID stuff, only the result.
So Linux/grub writes a single boot block to the logical drive and it
gets mirrored by the hardware RAID.
>(Note that this step is not required and should not be performed on
>UEFI systems, only BIOS.)
This also I'd like explained. Is this because the UEFI stuff _will_ be
in the area mirrored by the RAID?
Cheers,
Cameron Simpson <cs@xxxxxxxxxx>
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
