Duplicate entry in /etc/fstab

checking dmesg:

systemd-fstab-generator[872]: Failed to create unit file /run/systemd/generator/boot.mount, as it already exists. Duplicate entry in /etc/fstab?

/etc/fstab :
PARTUUID=00055c43-01 /boot vfat defaults 0 0
PARTUUID=00055c43-02 / ext4 defaults 0 1
LABEL=BOOT_MNJRO /boot vfat defaults,noexec,nodev,showexec 0 0

wich line to remove, or change?

run as root in a terminal “blkid” and you will see that first and third line will belog to the same partion.

Make the first line into… :arrow_down:

PARTUUID=00055c43-01  /boot vfat defaults,noexec,nodev,showexec 0 0

… and remove the last line. :slight_smile:


First line is the boot-partition of a non-UEFI Installation
Second line is the root-directory of the installation.
Duplicate??? 00055c43-01 is not the same as 00055c43-02

Do you have an actual problem?

That message says that a file already exists
and that the reason for that may be because of duplicate entries in fstab

… don’t know what triggers the message - it’s not an error
and if you do not have a problem …

maybe someone can explain why the message is there
It’ll satisfy some curiosity - but as it is not an error it is probably not urgent to find out. :sunglasses:

Incorrectamundo, Señor. :stuck_out_tongue:

The first line contains a PARTUUID, which is an indicator of a GPT-partitioned drive, and the ARM platform does not support the legacy x86 BIOS — the firmware is always going to be some variant of EFI, and on more recent devices, UEFI.

Those are not the duplicates the OP is referring to. The first and the third line both specify that /boot is the mountpoint. The difference is that the first line does it by way of a PARTUID and the third line by way of a filesystem LABEL. :wink:

It’s because the Sith Lord Darth Poettering ordained it so when he conceived systemd-mount. :smiley:


He brought order to the system. :face_with_peeking_eye:

1 Like

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.