[SOLVED] What is the correct way to auto-mount the EFI system on start

wnaBee · 2021-06-20 10:29:35

Hello,
I've recently installed Arch and run across the wonders of kernel updates.
After running pacman -Syu and rebooting, the system broke. Research has told me that mounting the EFI partition to /boot before an update solves the issue (i haven't had time to test this since a kernel update hasn't come by again, yet).
Mounting the EFI partition manually on startup works fine, but since this is a mild inconvenience I'd rather automate it.
I created the final entry here in /etc/fstab based on a few archwiki articles ( https://wiki.archlinux.org/title/Fstab , https://wiki.archlinux.org/title/EFI_system_partition ):

# Static information about the filesystems.
# See fstab(5) for details.

# <file system> <dir> <type> <options> <dump> <pass>

# /dev/sda3
UUID=3b63a5b7-0e67-4f80-8a7a-96deea0b4007       /               ext4            rw,relatime     0 1

# /dev/sda2
UUID=4a502e90-800e-4ac3-a0bd-371f3eddc24c       none            swap            defaults        0 0

# /dev/sda1 (boot partition entry)
#UUID=77F5-6ED2                                  /boot           vfat            defaults,bind   0 2

This fails, creating the following entries in journalctl -xb:

Jun 20 12:00:14 ArchS mount[336]: mount: /boot: mount(2) system call failed: Not a directory.
Jun 20 12:00:14 ArchS systemd[1]: boot.mount: Mount process exited, code=exited, status=32/n/a
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ An n/a= process belonging to unit boot.mount has exited.
░░ 
░░ The process' exit code is 'exited' and its exit status is 32.
Jun 20 12:00:14 ArchS systemd[1]: boot.mount: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ The unit boot.mount has entered the 'failed' state with result 'exit-code'.
Jun 20 12:00:14 ArchS systemd[1]: Failed to mount /boot.
░░ Subject: A start job for unit boot.mount has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A start job for unit boot.mount has finished with a failure.
░░ 
░░ The job identifier is 32 and the job result is failed.

Since the first line states that /boot is "not a directory" i tried changing the order of the entries in the fstab file but this didn't help.
Considering that mounting the EFI partition manually when logged in works i could write a simple bash script to do it on startup, but this seems insecure and a bit like cheating.
Is there a proper way to do it (through fstab or other) and if so, what is it?

Last edited by wnaBee (2021-06-20 10:54:54)

tucuxi · 2021-06-20 10:42:50

You sure added the line after /. Please post your complete /etc/fstab.

progandy · 2021-06-20 10:45:08

Do not add "bind" to the options, that is trying to create a bind mount and is wrong if you want to mount a partition.

wnaBee · 2021-06-20 10:47:21

tucuxi wrote:

You sure added the line after /. Please post your complete /etc/fstab.

changed my OP as per your request.

wnaBee · 2021-06-20 10:53:29

progandy wrote:

Do not add "bind" to the options, that is trying to create a bind mount and is wrong if you want to mount a partition.

This seems to have worked, changing title to solved.

Thank you very much!

Arch Linux

#1 2021-06-20 10:29:35

[SOLVED] What is the correct way to auto-mount the EFI system on start

#2 2021-06-20 10:42:50

Re: [SOLVED] What is the correct way to auto-mount the EFI system on start

#3 2021-06-20 10:45:08

Re: [SOLVED] What is the correct way to auto-mount the EFI system on start

#4 2021-06-20 10:47:21

Re: [SOLVED] What is the correct way to auto-mount the EFI system on start

#5 2021-06-20 10:53:29

Re: [SOLVED] What is the correct way to auto-mount the EFI system on start

Board footer