On 27/11/2019 02.35, Chris Murphy wrote:
On Tue, Nov 26, 2019 at 4:53 PM Chris Murphy <lists@xxxxxxxxxxxxxxxxx> wrote:
On Tue, Nov 26, 2019 at 2:11 PM Goffredo Baroncelli <kreijack@xxxxxxxxx> wrote:
I think that the errors is due to the "rescan" logic (see grub commit [1]). Could you try a more recent grub (2.04 instead of 2.02) ?
Yes Fedora Rawhide has 2.04 in it, so I'll give that a shot next time
I rebuild this particular laptop, which should be relatively soon; or
even maybe I can reproduce this problem in a VM with two virtio
devices.
I was able to just update to the Fedora 2.04-4.fc32 packages. It's not
upstream's but it's a quick and dirty way to give it a shot. Turns
out, the same errors happen, although the line number for efidisk.c
has changed:
https://photos.app.goo.gl/aKWRYhJkkJRDtC1W7
For grins, I dropped to a grub prompt, and issued ls and get a different result:
https://photos.app.goo.gl/MvL9QZa6zGsiktAf9
Looking at the second picture, it seems that grub had problem to access the disk 0..3 not only when is doing a btrfs activity.
No problem accessing hd4 and hd5*
Could you enable the debug, doing
set pager=1
set debug=all
?
Also for what it's worth, the Btrfs in question is on hd5,gpt4 and
hd5gpt5 - same physical device, different partitions.
--
gpg @keyserver.linux.it: Goffredo Baroncelli <kreijackATinwind.it>
Key fingerprint BBF5 1610 0B64 DAC6 5F7D 17B2 0EDA 9B37 8B82 E0B5
