GNU GRUB - Bugs: bug #38406, GRUB assembles wrong disks for md...
You are not allowed to post comments on this tracker with your current authentication level.
bug #38406: GRUB assembles wrong disks for md RAID device
Submitter: | Marc Warne (GigaTux) <gigatux> | ||
Submitted: | Mon 25 Feb 2013 11:25:32 AM UTC | ||
Category: | Booting | Severity: | Major |
Priority: | 5 - Normal | Item Group: | Software Error |
Status: | None | Privacy: | Public |
Assigned to: | None | Originator Name: | Marc Warne |
Open/Closed: | Open | Release: | 1.98 |
Release: | Reproducibility: | Every Time | |
Planned Release: | 2.03+ |
Sun 21 Oct 2018 08:32:20 PM UTC, comment #2: |
Phillip Susi <psusi> |
Wed 02 Mar 2016 02:21:24 PM UTC, comment #1: Fixing this is somewhat hairy. Postponing after release to avoid introducing worse bugs |
Vladimir Serbinenko <phcoder>![]() |
Mon 25 Feb 2013 11:25:32 AM UTC, original submission:
Hi,
|
Marc Warne (GigaTux) <gigatux> |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
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.