GNU GRUB - Bugs: bug #48228, grub-mkconfig assumes grub-probe...
You are not allowed to post comments on this tracker with your current authentication level.
bug #48228: grub-mkconfig assumes grub-probe will only produce 1 line of output, breaks with mirrored zfs volumes
Submitter: | Will Rouesnel <wrouesnel> | ||
Submitted: | Tue 14 Jun 2016 11:49:58 PM UTC | ||
Category: | Booting | Severity: | Major |
Priority: | 6 | Item Group: | Software Error |
Status: | None | Privacy: | Public |
Assigned to: | None | Originator Name: | Will Rouesnel |
Open/Closed: | Open | Release: | 2.02~beta1 |
Release: | Reproducibility: | Every Time | |
Planned Release: | 2.02 |
Jump to the original submission
Thu 31 May 2018 05:10:13 PM UTC, comment #7: |
Marcel Sackermann <m0gg> |
Wed 26 Oct 2016 07:04:59 PM UTC, comment #6: i cannot right now as I'm not using that configuration any longer.
|
spongman <spongman> |
Wed 26 Oct 2016 04:38:48 PM UTC, comment #5: Please provide debug information I asked for. |
Andrei Borzenkov <arvidjaar> |
Wed 26 Oct 2016 03:32:03 AM UTC, comment #4: I'm seeing the same issue - the grub-mkconfig is written entirely with the assumption that only one device is returned from grub-probe. which is not true in the case of multi-device zfs pools.
|
spongman <spongman> |
Wed 29 Jun 2016 06:03:22 PM UTC, comment #3: Did you test upstream GIT? If root is zfs, we should get
|
Andrei Borzenkov <arvidjaar> |
Wed 29 Jun 2016 04:53:29 PM UTC, comment #2: I've attached grub.cfg from a system with the following setup:
|
Will Rouesnel <wrouesnel> |
Wed 15 Jun 2016 03:22:35 AM UTC, comment #1: Your patch is wrong - we need to know all devices to build full list of drivers. You do not say what exactly is broken in your case. One problem with multi-device filesystem was fixed in 2.02~beta3; please test with current GIT. If it does not work, attach bad grub.cfg. |
Andrei Borzenkov <arvidjaar> |
Tue 14 Jun 2016 11:49:58 PM UTC, original submission:
Using 2.02~beta2-36ubuntu3 and a ZFS root setup with mirrored, encrypted drives, I've had multiple problems with the grub-mkconfig script and libraries assuming that the output from grub-probe will only ever be a single line.
|
Will Rouesnel <wrouesnel> |
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.
Follow 6 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2018-05-31 | m0gg | Attached File | - | Added mkconfig-out, #44263 | |
2016-10-11 | phcoder | Priority | 5 - Normal | 6 | |
Planned Release | None | 2.02 | |||
2016-06-29 | wrouesnel | Attached File | - | Added grub.cfg, #37624 | |
2016-06-14 | wrouesnel | Attached File | - | Added mkconfig.patch, #37478 | |
Attached File | - | Added grub-mkconfig.patch, #37479 |
Powered by Savane 3.13-02a9.
Corresponding source code
This is an issue for btrfs volumes with multiple devices aswell.
# grub-probe --target=device /
will give two lines of output:
/dev/mapper/vg0-root
/dev/mapper/vg0-root1
which causes grub-mkconfig to output a linebreak in the kernel cmdline aswell.
In case of btrfs, it's sufficient to trim the $GRUB_DEVICE after the first blank, don't know about zfs though.
Latest git (cda0a857dd7a27cd5d621747464bfe71e8727fff) does not fix this issue.
(file #44263)