GRUB broken after upgrade to F38

,

Ran the recommended here grub2-install as part of F38 post-upgrade cleanup tasks on a VM guest, just like before with F37. Upon reboot, my guest spews paginated screens after screens of error: ../../grub-core/fs/xfs.c:541:not a correct XFS inode. but eventually displays the boot menu, and finally boots F38 fine. Anyone has seen this issue and/or knows how to correct it?

Have you tried running fsck on your xfa file systems to see if there is a problem?

fsck -NV reports exactly nothing, xfs_repair -nv doesn’t seem to pick on anything suspicious, either:

Phase 1 - find and verify superblock...
        - block cache size set to 184712 entries
Phase 2 - using internal log
        - zero log...
zero_log: head block 186 tail block 186
        - scan filesystem freespace and inode maps...
        - found root inode chunk
Phase 3 - for each AG...
        - scan (but don't clear) agi unlinked lists...
        - process known inodes and perform inode discovery...
        - agno = 0
        - agno = 1
        - agno = 2
        - agno = 3
        - process newly discovered inodes...
Phase 4 - check for duplicate blocks...
        - setting up duplicate extent list...
        - check for inodes claiming duplicate blocks...
        - agno = 0
        - agno = 1
        - agno = 2
        - agno = 3
No modify flag set, skipping phase 5
Phase 6 - check inode connectivity...
        - traversing filesystem ...
        - agno = 0
        - agno = 1
        - agno = 2
        - agno = 3
        - traversal finished ...
        - moving disconnected inodes to lost+found ...
Phase 7 - verify link counts...
No modify flag set, skipping filesystem flush and exiting.

        XFS_REPAIR Summary    Wed Dec 27 09:45:00 2023

Phase           Start           End             Duration
Phase 1:        12/27 09:45:00  12/27 09:45:00
Phase 2:        12/27 09:45:00  12/27 09:45:00
Phase 3:        12/27 09:45:00  12/27 09:45:00
Phase 4:        12/27 09:45:00  12/27 09:45:00
Phase 5:        Skipped
Phase 6:        12/27 09:45:00  12/27 09:45:00
Phase 7:        12/27 09:45:00  12/27 09:45:00

Total run time:

Are you planning to upgrade to F39? If so do that upgrade and see if the problem still exists.

A little queasy about doing a system upgrade from an unstable state…

Ran a few more check & the sequence is quite predictable, requiring (initially) 43 spacebar presses to page through the errors until the menu, then 33 more until Press any key to continue..., after which F38 boots fine. Ran xfs_repair -v, after which the number of errors remained the same, but then ran grub2-install and upon reboot the number of error jumped to 98 spacebar presses until the menu & 121 more until Press any key to continue...

My system has grub2-tools-2.06-108.fc38.x86_64, F37 (last successful GRUB install) had grub2-tools-2.06-94.fc37.x86_64, while F39 seems to have grub2-tools-2.06-110.fc39.x86_64.rpm–will review the changes on both sides before proceeding with the upgrade…

It seems F39 has the exact same issue: Grub2-install results in “not a correct XFS inode”

Fixed my issue by doing a dnf downgrade grub2-tools, which downgraded grub2-tools to rev. 2.06-89 (and pulled along grub2-common, grub2-pc, grub2-pc-modules, and grub2-tools-minimal as dependencies), then issuing grub2-install again; upon reboot all the errors are gone.

QA team identified an offending patch that introduced the problem in -108 in F38 & -110 in F39 and the fix should be available shortly (see Red Hat Bugzilla – Bug 2254370); marking this as solution in the meantime.

The following workaround is also available: Grub2-install results in "not a correct XFS inode" - #28 by alexonoliveira