Hi Charles,
So far, so good. However, please show us the complete command and
output by copy and paste. E.g.:
root@peregrine:~# grep efi /etc/fstab
# /boot/efi was on /dev/nvme0n1p1 during installation
UUID=91AE-3A24 /boot/efi vfat umask=0077 0 1 root@peregrine:~# df -h /boot/efi/
Filesystem Size Used Avail Use% Mounted on
/dev/nvme0n1p1 93M 5.9M 87M 7% /boot/efi
root@peregrine:~#
grep efi /etc/fstab
# /boot/efi was on /dev/nvme0n1p1 during installation
UUID=5ABD-D634 /boot/efi vfat umask=0077 0 1
For example, the output I show confirms that the correct partition is
mounted on /boot/efi.
But I also find the directory
/efi
which has the same content as /boot/efi. It shows, both are the same.
"It shows" ??? What shows? How?
See:
root@protheus3:~# ls -la /boot/efi/
insgesamt 7
drwx------ 4 root root 1024 1. Jan 1970 .
drwxrwxrwx 5 root root 4096 19. Jan 20:28 ..
drwx------ 5 root root 1024 18. Jan 12:10 EFI
drwx------ 2 root root 1024 18. Jan 12:43 'System Volume Information'
root@protheus3:~# ls -la /efi/
insgesamt 7
drwx------ 4 root root 1024 1. Jan 1970 .
drwxr-xr-x 26 root root 4096 22. Jan 16:43 ..
drwx------ 5 root root 1024 18. Jan 12:10 EFI
drwx------ 2 root root 1024 18. Jan 12:43 'System Volume Information' root@protheus3:~#
2. If not, how can I get rid of it?
That depends on what it is. If it is a regular directory, then "rm -r
/efi" should do it. However, if your EFI partition is also mounted on
/efi, or /efi is a symbolic or hard link to /boot/efi, that would be catastrophic.
Please take a look:
df
Dateisystem 1K-Blöcke Benutzt Verfügbar Verw% Eingehängt auf
udev 8058456 0 8058456 0% /dev
tmpfs 1618552 2812 1615740 1% /run /dev/nvme0n1p7 19046484 4556432 13497184 26% / /dev/mapper/nvme0n1p9_crypt 57342056 29104168 25292660 54% /usr
tmpfs 8092744 2420 8090324 1% /dev/shm
tmpfs 5120 8 5112 1% /run/lock
shm 8092744 0 8092744 0% /run/shm
tmp 8092744 28 8092716 1% /tmp /dev/nvme0n1p5 3764408 81732 3470964 3% /boot /dev/nvme0n1p1 98304 31927 66377 33% /efi /dev/mapper/nvme0n1p8_crypt 152671760 116433088 28410604 81% /home /dev/mapper/nvme0n1p10_crypt 28644260 12251508 14912356 46% /var
tmpfs 1618548 216 1618332 1% /run/user/ 1000
tmpfs 1618548 180 1618368 1% /run/user/0
Note: you see,
/dev/nvmne0n1p1 is mounted to /efi
and
/dev/nvme0n1p5 is mounted to /boot
/boot is ext4 formatted and it should mount according to /etc/fstab to /boot/ efi. Strange thing is, somtimes the efi-üpartition is mounted to /boot/efi AND /
efi, too.
However, in that state, using df -h, it does NOT show, that /efi is mounted somewhere, so it should be able to delete the folder /efi. BUT this canniot be done, as it says, it is mounted. Weired!
Probably not. If you used a Debian 12 (bookworm) netinst installer, you should have everything you need. For most people, grub and efi are
"fire and forget" systems: the system is set up once and runs
automatically as needed.
The installation I did was a little bit tricky. As I needed to transfer my old Debian from ssd to nvme and it is dual-boot, I first installed Windows, then installed debian. After ist, backuped /etc to somewhere. Then rsynced / , / home, /var, /usr and so on to the NVME. After ist, rsynced the backupped /etc back, so that I got all the devicenames back.
This worked well so far. Instead of this little issue.
Best
Hans
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)