Re: [gentoo-user] [SOLVED] fsck.fat 4.1 - File system couldn't be fixed [SOLVED]

[Victor Ivanov <vic.m.ivanov@gmail.com>]

[-- Attachment #1.1: Type: text/plain, Size: 1500 bytes --]

On 13/12/2020 07:42, thelma@sys-concept.com wrote:
> I was following the Gentoo handbook, maybe I didn't read it correctly
> and/or miss the information on alternative setting.  I didn't see any
> explanation that I need to have support for "fsck.fat".
> I better stay away from any "vfat" format on boot partition, and I don't
> see a reason to have initramfs (another complexity).
> 
No worries at all, despite my using Gentoo for the better part of a 
decade I too sometimes do something silly without realising. And you're 
right that this part of the guidebook could be improved to make some 
clarifications.

In any case, I've looked at the fstab on one of my machines and I do 
have dump/pass set to "0 2" for the EFI partition (which is of course 
vfat). I changed that to "1 2" to match your previous setup, though I 
was sceptical if that would make any difference. I created a /forcefsck 
file and managed to reboot just fine which suggests that either:

1) my ramdisk has fsck.fat bundled; or
2) was able to use the binary from the root partition after it was 
mounted read-only

[I could check explicitly, but I'm feeling a bit lazy]

Out of curiosity, do you have the "sys-fs/dosfstools" package installed?

This is the package that provides the fsck.fat binary. It's not a 
dependency of commonly installed system packages so unless you install 
it manually it's probably missing which might explain why fsck is 
exiting with an error code.

- Victor


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]