GNU GRUB - Bugs: bug #62756, grub-install fails with...
You are not allowed to post comments on this tracker with your current authentication level.
bug #62756: grub-install fails with /dev/md_NAME style device names
Submitter: | Hunor Csordás <hunor> | ||
Submitted: | Tue 12 Jul 2022 05:36:30 PM UTC | ||
Category: | Installation | Severity: | Major |
Priority: | 5 - Normal | Item Group: | None |
Status: | None | Privacy: | Public |
Assigned to: | None | Originator Name: | |
Open/Closed: | Open | Release: | Git master |
Release: | Reproducibility: | Every Time | |
Planned Release: | None |
Tue 12 Jul 2022 05:38:53 PM UTC, comment #1: |
Hunor Csordás <hunor> |
Tue 12 Jul 2022 05:36:30 PM UTC, original submission:
I get the following error from grub-install on Linux with named md devices:
|
Hunor Csordás <hunor> |
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.
Follows 1 latest change.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2022-07-12 | hunor | Attached File | - | ![]() |
Added named-md-device.patch, #53423 |
Possible patch attached. This maps all the "numbered" device filenames that were previously recognized to the same grub device as before:
And it allows the following "named" device filenames:
In addition, the entire device filename is checked, instead of relying only on the prefix, allowing the name in the "named" filenames to begin with a 'd' or a number. This is still not perfect -- naming an array "d1" will still give md1 instead of md/d1, but giving an array such a misleading name is probably a bad idea anyway.
The device is still rejected even if an mduuid/UUID style device could be found. This is unchanged behavior.
Finally, named devices are now always treated as unpartitioned. This is because it's pretty much impossible to figure out the layout from the name alone: /dev/md/ap1p2 could refer to either
This patch always chooses option 1. The previous behavior was inconsistent:
(file #53423)