From: Wols Lists <antlists@youngman.org.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] [SOLVED] fsck.fat 4.1 - File system couldn't be fixed [SOLVED]
Date: Mon, 14 Dec 2020 10:09:30 +0000 [thread overview]
Message-ID: <5FD739DA.1040505@youngman.org.uk> (raw)
In-Reply-To: <20201214054146.0CC61E09F5@pigeon.gentoo.org>
On 14/12/20 05:41, Thomas Mueller wrote:
> Excerpt from Michael:
>
>> Right, on UEFI MoBos the ESP partition used by the UEFI firmware to locate and
>> run *.EFI executables must be FAT32. Such .EFI executables stored on the ESP
>> may be OS boot managers/loaders, or other UEFI compatible applications. The
>> boot manager loaded by UEFI is then left to its own mechanisms (boot loader
>> and fs drivers) to load whatever fs the kernel image resides on.
>
> Is it necessary for the ESP to be FAT32, as opposed to FAT16 or FAT12?
>
> What happens if the ESP is formatted FAT12 or FAT16?
>
I think the spec actually says it must comply with a specific version of
the FAT definition. Not sure which version, but that does specify all
three FAT layouts, so all three are acceptable. Look at mjg's blog for
more detail, I guess.
That protects against updates to the spec making incompatible changes,
but doesn't protect against clueless manufacturers not following the
spec - "works with Windows" is so often the de-facto spec.
Cheers,
Wol
prev parent reply other threads:[~2020-12-14 9:30 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-11 21:36 [gentoo-user] fsck.fat 4.1 - File system couldn't be fixed thelma
2020-12-11 22:06 ` Jack
2020-12-11 22:29 ` thelma
2020-12-11 23:50 ` Michael
2020-12-12 1:16 ` thelma
2020-12-12 7:32 ` Dan Egli
2020-12-12 18:48 ` thelma
2020-12-12 19:25 ` Dan Egli
2020-12-12 19:47 ` thelma
2020-12-13 0:04 ` Dan Egli
2020-12-12 20:24 ` thelma
2020-12-12 10:59 ` Tamer Higazi
2020-12-12 19:49 ` thelma
2020-12-13 0:06 ` Dan Egli
2020-12-12 22:40 ` Neil Bothwick
2020-12-13 3:07 ` [gentoo-user] [SOLVED] fsck.fat 4.1 - File system couldn't be fixed [SOLVED] thelma
2020-12-13 6:00 ` Victor Ivanov
2020-12-13 7:42 ` thelma
2020-12-13 7:57 ` [gentoo-user] How to config nullmailer bobwxc
2020-12-13 13:33 ` [gentoo-user] [SOLVED] fsck.fat 4.1 - File system couldn't be fixed [SOLVED] Victor Ivanov
2020-12-14 6:07 ` thelma
2020-12-14 12:06 ` Michael
2020-12-13 14:17 ` Michael
2020-12-13 14:33 ` Neil Bothwick
2020-12-13 15:02 ` Victor Ivanov
2020-12-13 16:52 ` Neil Bothwick
2020-12-14 5:41 ` Thomas Mueller
[not found] ` <20201214054146.415BCE0A03@pigeon.gentoo.org>
2020-12-14 10:02 ` Michael
[not found] ` <20201214054146.0CC61E09F5@pigeon.gentoo.org>
2020-12-14 10:09 ` Wols Lists [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5FD739DA.1040505@youngman.org.uk \
--to=antlists@youngman.org.uk \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox