Bug#1054644: xfsprogs-udeb: causes D-I to fail, reporting errors about missing partition devices

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, Oct 27, 2023 at 05:20:42PM +0200, Philip Hands wrote:
> Philip Hands <phil@xxxxxxxxx> writes:
> ...
> > Could this be related to #1051543?
> >
> > I'll try testing D-I while using the patch from that bug, to see if that helps.
> 
> It seems (to me at least) that the patch there does not apply usefully
> to the version we're talking about, so I'll leave it to people that know
> more about grub & XFS to look further.

>From https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054644#5:

> > I note that if one runs e.g.:  grub-probe -d /dev/vda1
> > at the moment of failure, the XFS filesystem is not recognised
> > (despite being mounted as XFS at that moment).
> > 
> > Could this be related to #1051543?
> > 
> > I'll try testing D-I while using the patch from that bug, to see if that
> > helps.

I noticed this too while migrating to Debian 12 -- if you mkfs.xfs a
/boot with feature flags that grub doesn't know about, grub-install
unhelpfully refuses to recognize that there's a filesystem there at all.

mkfs.xfs in xfsprogs 6.5 turned on both the large extent counts and
reverse mapping btree features by default.  My guess is that grub hasn't
caught up with those changes to the ondisk format yet.

Ah, yeah, upstream grub hasn't picked up large extent counts (internally
called nrext64) yet.
https://git.savannah.gnu.org/cgit/grub.git/tree/grub-core/fs/xfs.c#n83

If you can manually reformat the filesystem from within the installer
with

mkfs.xfs -c /usr/share/xfsprogs/mkfs/lts_6.1.conf

Does grub start to recognize the filesystem again?

> 
> =-=-=
> 
> BTW the jobs where this failure first occured are:
> 
> (BIOS)  https://openqa.debian.net/tests/198911
> (UEFI)  https://openqa.debian.net/tests/198912
> 
> and the immediately previous working jobs are these:
> 
> (BIOS)  https://openqa.debian.net/tests/198840
> (UEFI)  https://openqa.debian.net/tests/198841
> 
> In the jobs you can see a 'Logs & Assets' tab, where you can find e.g.
> the syslog from the D-I run.
> 
> Here's the one from the first BIOS failure:
> 
>   https://openqa.debian.net/tests/198911/logfile?filename=DI_syslog.txt

Curiously, this log says:

Oct 24 05:35:32 in-target: Setting up xfsprogs (6.4.0-1) ...^M

So ... is it running 6.4 and not 6.5?

--D

> 
> One thing I notice when comparing that to the matching successful log:
> 
>   https://openqa.debian.net/tests/198840/logfile?filename=complete_install-DI_syslog.txt
> 
> is that they both include a block of lines like:
> 
>    grub-installer: Unknown device "/dev/vda1": No such device
> 
> so that's just noise by the looks of it, since it was also saying that
> when it was working.
> 
> I've since slightly reorganised the openQA jobs, to have a job that only
> differs from the normal minimal install by the selection of XFS, so if
> you want to see currently failing jobs, they will be the ones called
> nonGUI_XFS@64bit & nonGUI_XFS (for BIOS & UEFI installs, respectively)
> in this overview:
> 
>   https://openqa.debian.net/tests/overview?distri=debian&groupid=10
> 
> HTH
> 
> Cheers, Phil.
> -- 
> Philip Hands -- https://hands.com/~phil



[Index of Archives]     [XFS Filesystem Development (older mail)]     [Linux Filesystem Development]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux RAID]     [Linux SCSI]


  Powered by Linux