General TC > General TC Talk
[Solved] grub cannot read usb drive's ext4 partition
patrikg:
HI GNUser,
It's so great that you don't give up, and now found the problem.
Now I can understand why my Arch being updating grub a lot.
So just one question more if you have time to answer of course ?
Is this only related to grub when using it to usb drive ?
I haven't seen any evidences with this to any other drives I have worked with.
Maybe this because me not using UEFI a lot, yes because i don't have so many computers that uses that.
Thanks again, I like the Linux community a lot that we can help each other like we do.
Leee:
FWIW, I've used juanito's instructions (referenced in the OP) to install Core on several different USB sticks using ext4 without any problems. With a new stick, I usually zero the first gigabyte or so with dd before starting, just so I have a clean slate.
gadget42:
i am going to quote @GNUser and also add the complete URL links below the quote(so screenshots will include the complete webpage address).
--- Quote from: GNUser on February 07, 2024, 11:22:56 PM ---The fix is in this commit to grub from July 2021, which unfortunately happened just after the release of grub 2.06 in June 2021.
The problem did turn out to be related to metadata, with the grub and e2fsprogs projects being briefly out of sync regarding how partition metadata is handled. Theodore Ts'o explains the issue here.
The latest grub release, version 2.12, includes the fix.
--- End quote ---
(from circa 2021)
https://git.savannah.gnu.org/cgit/grub.git/commit/?id=7fd5feff97c4b1f446f8fcf6d37aca0c64e7c763
(from circa 2023)
https://groups.google.com/g/linux.debian.bugs.dist/c/HiBoBMllrlU/m/RNQ6jmEuAQAJ
(and following a link from Andreas Henriksson in the above group back to circa 2018)
https://github.com/go-debos/debos/issues/78
this years-long potential-for-breakage saga is a learning-lesson, teaching-moment, and given the severity(as evidenced by this very thread) might even be a candidate for some type of "sticky-posting" perhaps...sigh...
jazzbiker:
Hi smart guys!
I'm too stupid to understand the drama, could You be so kind to say one word for the dumb ones: are MBRs affected?
GNUser:
Hello friends. The bottomline is that an ext4 filesystem created with e2fsprogs version 1.47.0 with the new default options will not be recognized by grub version 2.06. I don't know whether other filesystems are also affected.
The issue has to do with filesystem metadata, so hardware (HDD, SDD, USB) and partition table (MBR, GPT) make no difference.
Among TCL versions, the problem only affects TCL15 x86_64 because it is the only TCL version whose repo has this new e2fsprogs version (1.47.0) that doesn't play nice with grub 2.06.
If you are not on TCL15 x86_64, you have nothing to worry about.
If you are on TCL15 x86_64, use grub 2.06, and need to create a new ext4 partition that will contain files that grub needs to find (e.g., vmlinuz64, corepure64.gz), you have several options:
- use an older version of e2fsprogs (e.g., 1.46.5 in TCL14 x86_64) to create the ext4 filesystem
- use repo's e2fsprogs 1.47.0 but disable checksum seed feature (see Rich's post above)
- wait until Juanito updates grub2-multi.tcz to version 2.12, reinstall grub, then use e2fsprogs 1.47.0 with default options
I hope that's clear. Rich, thread may be marked as solved.
Happy hacking!
----------
P.S. In my original post, I mentioned that my SDD worked when I converted it from BIOS-only to BIOS+UEFI. The reason is that my SDD's ext4 partition was created a long time ago with an old version of e2fsprogs. When I tried to create the bootable USB drive, I had to create a new ext4 partition on it and was doing this in TCL15 x86_64 with e2fsprogs 1.47.0. This is how I discovered the problem.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version