Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Bug#1021846: grub-install is broken since 2.06-3: error: unknown filesystem

33 views
Skip to first unread message

программист некто

unread,
Oct 16, 2022, 1:00:03 AM10/16/22
to
Output already captured. See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021846 the first message - it have an attached files with grub-install output.

Steve McIntyre

unread,
Oct 16, 2022, 5:40:04 PM10/16/22
to
On Sun, Oct 16, 2022 at 09:57:35PM +0100, Steve McIntyre wrote:
>On Sun, Oct 16, 2022 at 07:37:53AM +0300, программист некто wrote:
>>Output already captured. See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021846 the first message - it have an attached files with grub-install output.
>
>Ah, sorry; I missed them. Looking now.

So I can see from the logs is that from 2.06-3 is just failing to
detect a f2fs filesyste. There *was* a significant set of changes
before we shipped that version: upstream security updates that fixed a
big set of bugs, including in the f2fs code. I'm thinking that one of
those changes might have caused this issue.

Are you happy to try rebuilding grub from source yourself? If so, I'd
suggest to rebuild without those f2fs changes included. If you're not
sure, let me know and I'll do a rebuild for you.

--
Steve McIntyre, Cambridge, UK. st...@einval.com
< Aardvark> I dislike C++ to start with. C++11 just seems to be
handing rope-creating factories for users to hang multiple
instances of themselves.

Steve McIntyre

unread,
Oct 19, 2022, 7:00:04 AM10/19/22
to
On Wed, Oct 19, 2022 at 11:07:36AM +0300, программист некто wrote:
>I rebuilt grub2 v.2.06-4  without 3  f2fs patches.
>Results of   # /usr/sbin/grub-install -v /dev/sda
>in file attachment. No error!

Excellent, and thanks for testing!

OK, so the patches from upstream have broken f2fs support for
you. Looking at the patches, I'm not seeing anything *obvious* there
that might be an issue. They're all trying to add checks to avoid
crashes with an invalid/corrupt f2fs filesystem.

Silly question: does your filesystem have errors? Does fsck.f2fs
report anything?

--
Steve McIntyre, Cambridge, UK. st...@einval.com
< sladen> I actually stayed in a hotel and arrived to find a post-it
note stuck to the mini-bar saying "Paul: This fridge and
fittings are the correct way around and do not need altering"

программист некто

unread,
Oct 20, 2022, 1:20:03 PM10/20/22
to
# fsck.f2fs -f /dev/sda1
didn't report any errors.
I can continue testing - rebuild without patches in turn, to reveal patch which break f2fs support.

19.10.2022, 13:47, "Steve McIntyre" <st...@einval.com>:

Steve McIntyre

unread,
Oct 20, 2022, 1:30:03 PM10/20/22
to
On Thu, Oct 20, 2022 at 08:09:15PM +0300, программист некто wrote:
># fsck.f2fs -f /dev/sda1
>didn't report any errors.

OK, that's good to know.

>I can continue testing - rebuild without patches in turn, to reveal patch which break f2fs support.

If you're happy to do that, then that would be excellent!

--
Steve McIntyre, Cambridge, UK. st...@einval.com
"We're the technical experts. We were hired so that management could
ignore our recommendations and tell us how to do our jobs." -- Mike Andrews

программист некто

unread,
Nov 12, 2022, 7:20:03 AM11/12/22
to
Hello. I rebuilt and tested grub only with patch
0087-fs-f2fs-Do-not-read-past-the-end-of-nat-journal-entr.patch
Result: error: unknown filesystem.
0 new messages