Hi,
наб <nabijaczleweli@nabijaczleweli.xyz> (2025-12-14):
> I recently installed trixie on an EFI amd64 system.
>
> By definition, this means I have a vfat partition which is required for
> booting (and indeed I had an ESP on /dev/vda1).
> Additionally, /etc/fstab for /boot/efi has a fs_passno field of 1,
> so fscking is explicitly enabled.
>
> And yet! I don't have a fsck.vfat, so it doesn't get checked, ever.
>
> I think the target ought to have a fsck for all the filesystems
> configured in d-i anyway (but especially when it's part of the boot
> sequence), so d-i ought to pull in dosfstools I think?
Without knowing much about any possible decision against doing so… what
you're suggesting makes sense to me.
But from a quick look, I think this should be happening already?
commit 859ba462b5b1fc4e2c2a654a7263856905af51ce (tag: 163)
Author: Steve McIntyre <steve@einval.com>
Date: Mon May 15 22:59:30 2023 +0100
Install dosfstools if we have a FAT ESP
That should be the case for bookworm (164) and trixie (174).
https://salsa.debian.org/installer-team/partman-basicfilesystems/-/commit/859ba462b5b1fc4e2c2a654a7263856905af51ce
Any traces of trying (and maybe failing) to get that package installed?
See /var/log/syslog at runtime, and /var/log/installer/syslog afterwards.
Cheers,
--
Cyril Brulebois (kibi@debian.org) <https://debamax.com/>
D-I release manager -- Release team member -- Freelance Consultant
Attachment:
signature.asc
Description: PGP signature