Re: GRUB bug with Btrfs multiple devices

[Chris Murphy <lists@colorremedies.com>]

On Thu, Nov 28, 2019 at 10:58 AM Goffredo Baroncelli <kreijack@inwind.it> wrote:
>
> On 28/11/2019 01.42, Chris Murphy wrote:
> > On Tue, Nov 26, 2019 at 11:07 PM Goffredo Baroncelli <kreijack@inwind.it> wrote:
> >>
> [...]
> >> Could you enable the debug, doing
> >>
> >>          set pager=1
> >>          set debug=all
> >
> > I need to narrow the scope. Adding 'set debug=all', there's just way
> > too much to video, minutes of pages just holding down space bar full
> > time which is even too fast to video. There must be over 1000 pages, a
> > tiny minority contain efidisk.c references, the vast majority are
> > btrfs.c references. As many pages as there are, I was never able to
> > stop right on a boundary between efidisk.c and btrfs.c. So I gave up
> > on that approach.
>
> If I remember correctly, in the previous email you reports that even a simple "ls" at the grub prompt raises an error.
> So you could watch what happens when doing something simpler like "ls" or "ls (hd0)"

Errors with only ls.
https://photos.app.goo.gl/BJpsLvwpL6yf19uj6

Errors with ls per device
https://photos.app.goo.gl/pgxQDdj1JDjq86mZ9

But without rebooting, just repeating the ls for the same devices, I
don't get the error for hd4 again.
https://photos.app.goo.gl/M6yraHfgfAsMigaP8

From the first ls, it shows GPT on hd5, shouldn't 'ls (hd5)' report
GPT rather than no file system? gdisk finds no problem with the GPT on
/dev/sda which is hd5.


-- 
Chris Murphy