On Tue, Mar 25, 2025 at 09:00:09PM -0600, Thayne Harbaugh wrote:
> Response in-line:
>
> On Tue, 2025-03-25 at 16:53 -0600, Thayne Harbaugh wrote:
> > Greetings,
> >
> > systemd-repart MountPoint fails to generate a correct fstab entry for
> > esp partitions. It generates a standard partition UU
This is about fs UUID, not GPT PARTUUID. vfat filesystems do not support
standard UUID format for historical reason.
On 4/2/25 14:32, Karel Zak wrote:
On Tue, Mar 25, 2025 at 09:00:09PM -0600, Thayne Harbaugh wrote:
Response in-line:
On Tue, 2025-03-25 at 16:53 -0600, Thayne Harbaugh wrote:
On Di, 25.03.25 16:53, Thayne Harbaugh (tha...@mastodonlabs.com) wrote:
> Greetings,
>
> systemd-repart MountPoint fails to generate a correct fstab entry for
> esp partitions. It generates a standard partition UUID which does not
> work for FAT file systems - a FAT volume ID must be used analogo
Response in-line:
On Tue, 2025-03-25 at 16:53 -0600, Thayne Harbaugh wrote:
> Greetings,
>
> systemd-repart MountPoint fails to generate a correct fstab entry for
> esp partitions. It generates a standard partition UUID which does
> not
> work for FAT file systems - a FAT volume ID must be used
Greetings,
systemd-repart MountPoint fails to generate a correct fstab entry for
esp partitions. It generates a standard partition UUID which does not
work for FAT file systems - a FAT volume ID must be used analogous to
what is generated for vfat in mkfs-util.c:make_filesystem(). The FAT
volume
