The first problem is that the efi partition is mounted at two places:
/boot/efi
/efi
In fstab, its mounted only /boot/efi
Edit: It stays mounted on /efi as well for like 10 minutes after bootup, after which it’s only mounted at /boot/efi
The second one is that logs of previous boots are not stored anymore,
journalctl --list-boots only list the current boot.
Also there is no /var/log/journal in the /var/log/ directory.
Any ideas?
Update: I fixed the journal not storing logs by reinstalling systemd as the /var/log/journal folder was not present
I wonder how it got deleted as I haven’t done it nor executed such a script etc
The mounting problem still persists.
Are you using Grub or systemd-boot?
If the former, I wonder why there is an /efi directory in your system at all 
that’s what I’m wondering.
Im using grub but this is not normal.
the efi folder is also available on my installation, a few days ago the folder wasn’t there. had checked another installation, the efi folder was also there. both installations are up to date. I have an installation in the vm (6.4.7.arch1-1) that I created at the beginning of the week, the efi folder is not there, only after the update of the following packages.
gcc-13.2.1-3-x86_64 46,8 MiB 1030 KiB/s 00:47 100%
breeze-5.27.7-1-... 70,7 MiB 999 KiB/s 01:12 100%
gcc-libs-13.2.1-... 35,3 MiB 894 KiB/s 00:40 100%
linux-headers-6.... 29,6 MiB 797 KiB/s 00:38 100%
firefox-116.0-1-... 62,1 MiB 550 KiB/s 01:56 100%
noto-fonts-1:23.... 27,0 MiB 846 KiB/s 00:33 100%
linux-lts-6.1.39... 115,9 MiB 988 KiB/s 02:00 100%
glibc-2.38-1-x86_64 9,9 MiB 892 KiB/s 00:11 100%
qt5-base-5.15.10... 13,1 MiB 972 KiB/s 00:14 100%
linux-6.4.7.arch... 125,4 MiB 946 KiB/s 02:16 100%
systemd-254-1-x86_64 7,6 MiB 757 KiB/s 00:10 100%
openssl-3.1.2-1-... 4,5 MiB 736 KiB/s 00:06 100%
linux-api-header... 1233,3 KiB 1466 KiB/s 00:01 100%
libopenraw-0.3.7... 1219,7 KiB 954 KiB/s 00:01 100%
openexr-3.1.10-1... 1213,5 KiB 724 KiB/s 00:02 100%
linux-lts-header... 26,7 MiB 808 KiB/s 00:34 100%
systemd-libs-254... 1083,1 KiB 628 KiB/s 00:02 100%
libelf-0.189-3-x... 551,2 KiB 904 KiB/s 00:01 100%
binutils-2.41-2-... 7,6 MiB 687 KiB/s 00:11 100%
gmp-6.3.0-1-x86_64 443,5 KiB 930 KiB/s 00:00 100%
firefox-i18n-de-... 500,6 KiB 904 KiB/s 00:01 100%
mpfr-4.2.0.p12-3... 427,7 KiB 936 KiB/s 00:00 100%
harfbuzz-8.1.1-1... 962,6 KiB 707 KiB/s 00:01 100%
libtool-2.4.7+4+... 412,4 KiB 1189 KiB/s 00:00 100%
libkscreen-5.27.... 391,2 KiB 1038 KiB/s 00:00 100%
polkit-123-1-x86_64 396,7 KiB 920 KiB/s 00:00 100%
breeze-gtk-5.27.... 200,9 KiB 999 KiB/s 00:00 100%
dracut-059-3-x86_64 287,3 KiB 667 KiB/s 00:00 100%
gupnp-1:1.6.5-1-... 124,3 KiB 1243 KiB/s 00:00 100%
unrar-1:6.2.10-1... 140,3 KiB 1080 KiB/s 00:00 100%
libsysprof-captu... 45,2 KiB 904 KiB/s 00:00 100%
welcome-3.68-2-any 31,3 KiB 348 KiB/s 00:00 100%
kdecoration-5.27... 78,5 KiB 671 KiB/s 00:00 100%
reflector-simple... 21,3 KiB 1066 KiB/s 00:00 100%
eos-update-notif... 22,5 KiB 258 KiB/s 00:00 100%
eos-rankmirrors-... 18,2 KiB 911 KiB/s 00:00 100%
harfbuzz-icu-8.1... 8,0 KiB 501 KiB/s 00:00 100%
eos-log-tool-23-... 18,4 KiB 211 KiB/s 00:00 100%
systemd-sysvcomp... 6,0 KiB 261 KiB/s 00:00 100%
systemd-resolvco... 3,1 KiB 120 KiB/s 00:00 100%
eos-bash-shared-... 50,1 KiB 142 KiB/s 00:00 100%
webkit2gtk-2.40.... 26,6 MiB 631 KiB/s 00:43 100%
the efi folder appears to be an image of /boot/efi since the timestamps are identical.
Can you test that it gets mounted at bootup as well along with /boot/efi?
it is /boot/efi
I mean does it get mounted at /efi as well when u bootup?
To check, type lsblk as soon as you bootup.
after reboot i get this:
[pycrk@eno ~]$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
nvme0n1 259:0 0 476,9G 0 disk
├─nvme0n1p1 259:1 0 260M 0 part /efi
│ /boot/efi
├─nvme0n1p2 259:2 0 16M 0 part
├─nvme0n1p3 259:3 0 283,2G 0 part
└─nvme0n1p4 259:4 0 190G 0 part /
yeah same it means its not just me.
Can you specify that you did manual partitioning or automatic while installing?
I did manual partitioning.
mee too, i chosen manual partitioning, without swap.
I don’t think so it would be related to that.
But let’s see. Do you have a test bench without manual partitioning? If you can test on that, that would be good.
yes i have it on a VM, same result:
[pycrk@pycrk-virtualbox ~]$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
sda 8:0 0 15,5G 0 disk
├─sda1 8:1 0 1000M 0 part /efi
│ /boot/efi
└─sda2 8:2 0 14,5G 0 part /
I guess it’s a bug then. Let’s see if other people can reproduce it as well.
This is a highly intriguing and interesting “phenomenon”.
On two Arch installs ( different hardware: Intel and AMD -based), fully updated, I don’t see this behaviour.
I wonder what process has created that /efi directory and when. I mean, at some point, a process must have run mkdir /efi as root, or …?
Is there a corresponding systemd mount unit for /efi as well?
systemctl | grep efi.mount
[pycrk@eno ~]$ systemctl | grep efi.mount
boot-efi.mount
➜ ~ systemctl | grep efi.mount
boot-efi.mount loaded active mounted /boot/efi
how old are your installations?