Bug 2166412 - ext4 filessystem support missing
Summary: ext4 filessystem support missing
Alias: None
Product: Fedora
Classification: Fedora
Component: grub2
Version: 38
Hardware: aarch64
OS: Unspecified
Target Milestone: ---
Assignee: Javier Martinez Canillas
QA Contact: Fedora Extras Quality Assurance
Depends On:
Blocks: F38BetaBlocker
TreeView+ depends on / blocked
Reported: 2023-02-01 18:34 UTC by Dennis Gilmore
Modified: 2023-02-10 17:50 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2023-02-10 17:50:12 UTC
Type: Bug

Attachments (Terms of Use)

Description Dennis Gilmore 2023-02-01 18:34:39 UTC
Description of problem:
when booting my system the configfile was not automatically loaded. when trying to load it I get the following output 

grub> configfile (hd0,g
Possible partitions are:

        Partition hd0,gpt1: No known filesystem detected - Partition start at
1024KiB - Total size 1049600KiB
        Partition hd0,gpt2: Filesystem type fat - Label `ESP', UUID A19D-3026 -
Partition start at 1050624KiB - Total size 1049600KiB
        Partition hd0,gpt3: No known filesystem detected - Partition start at
2100224KiB - Total size 974661632KiB

hd0,gpt1 is /boot and ext4, insmod ext2 did not result in the system being able to read the partition.

I used the livecd and downgraded to grub2-2.06-76.fc38 which had no issues booting

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:

Actual results:

Expected results:

Additional info:

Comment 1 Dennis Gilmore 2023-02-01 19:40:08 UTC
Proposing as a blocker as it renders the system unbootable

Comment 2 Robbie Harwood 2023-02-01 21:28:11 UTC
Can you retest with grub2-2.06-80.fc38?

Comment 3 Ben Cotton 2023-02-07 15:07:53 UTC
This bug appears to have been reported against 'rawhide' during the Fedora Linux 38 development cycle.
Changing version to 38.

Comment 4 Ben Cotton 2023-02-10 13:28:27 UTC
Needinfo'ing reporter for comment #2

Comment 5 Dennis Gilmore 2023-02-10 17:50:12 UTC
closing as this is now working

Note You need to log in before you can comment on or make changes to this bug.