GNU GRUB - Bugs: bug #63784, grub-mkconfig generates invalid...
You are not allowed to post comments on this tracker with your current authentication level.
bug #63784: grub-mkconfig generates invalid code that passes grub-script-check when / is ZFS and there is no initrd
Submitter: | Arsen Arsenović <arsen> | ||
Submitted: | Fri 10 Feb 2023 08:33:49 PM UTC | ||
Category: | Configuration | Severity: | Major |
Priority: | 5 - Normal | Item Group: | Software Error |
Status: | None | Privacy: | Public |
Assigned to: | None | Originator Name: | |
Open/Closed: | Open | Release: | 2.02~rc1 |
Release: | Reproducibility: | Every Time | |
Planned Release: | None |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
Carbon-Copy List
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.
No changes have been made to this item
Note: I'm actually on 2.06. This release isn't listed on the submit page, though.
If / is ZFS and there's no initrd, a rather peculiar sequences of failures happens.
Let's suppose the following:
Later, in 10_linux, the following block replaces the root device with "$GRUB_DEVICE" from above:
This results in the following menuentry:
In general, 10_linux (and presumably others) seem unprepared for odd GRUB_DEVICE values.
I'm unsure what a correct, or even decent, fix here is.. perhaps failing when GRUB_DEVICE is determined to be more than one device? While that is, of course, an error while running mkconfig, it's presumably better to an unbootable system.
In that case, the user could specify their root device manually, maybe?
Thanks in advance, have a lovely day.