On 03/01/2017 06:51 PM, Peter Sangas wrote:
>
>> { Convention on kernel.org is to reply-to-all, trim unneeded quoted material, and bottom post or interleave. Please do so. }
>
> Yes. thank you.
>
>> Grub1 needs its boot partitions to use v0.90 or v1.0 superblocks. Grub2 needs the md module in its core to boot from v1.1 or v1.2 superblocks.
>> Anyways, because the content of a v1.2 array does not start at the beginning of the member devices, stupid grub doesn't connect sd[abc]1 with your /boot mount >and therefore delivers 'null'.
>> And then doesn't know how to link the core together.
>
> can't say I understand all that but does this mean the server can't boot from the replacement drive?
Correct. But it shouldn't be able to boot from the others either, with
grub1. Something has changed in your grub install since you set up the
original drives. Only grub2 would be able to boot from your v1.2 md0.
{ Sorry. I don't know how to fix grub2's md module. }
Phil
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
