Follow-up Comment #2, bug #38406 (project grub):
I think I recently got bit by this as well. I have 3 disks with part in a 3
way raid10 for my root fs, and the rest in a raid5 for media storage. After
some updates, I rebooted and got all kinds of weird errors trying to load any
kernel. I booted from a liveusb and poked around and it turned out that one
of the disks had been marked as failed in the raid10 for some reason a month
or two before and I hadn't noticed. After re-adding the disk to the array and
resyncing it, I was able to boot again. GRUB really needs to pay attention to
the failed flags in the most recently updated metadata block.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?38406>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
_______________________________________________
Bug-grub mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/bug-grub
