I’ve just tried that command and it didn’t display any output.
so its probably mounted so try to reinstall grub:
grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=manjaro --recheck
Here’s the output of that command:
grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=manjaro --recheck ✔
Installing for x86_64-efi platform.
grub-install: error: failed to get canonical path of `/boot/efi'.
so try this:
sudo mount /dev/nvme0n1p1 /boot/efi
sudo mount /dev/nvme0n1p1 /boot/efi 1 ✘
mount: /boot/efi: mount point does not exist.
dmesg(1) may have more information after failed mount system call.
Because…
Should be this. Note the /mnt/ that leads.
sudo mount /dev/nvme0n1p1 /mnt/boot/efi 32 ✘
mount: /mnt/boot/efi: mount point does not exist.
dmesg(1) may have more information after failed mount system call.
Still experiencing the issue where the mount point does not exist.
so hopefully @winnie is going to assist, because i dont knot why it dont want to mount it
yeah, because I just tried remounting it and this displayed:
sudo mount /dev/nvme0n1p1 /mnt 32 ✘
mount: /mnt: /dev/nvme0n1p1 already mounted on /mnt.
dmesg(1) may have more information after failed mount system call.
I then also tried going into the /boot directory to see what’s exactly going on and found this:
cd /boot
/boot ls
amd-ucode.img initramfs-5.15-x86_64-fallback.img intel-ucode.img memtest86+
grub initramfs-5.15-x86_64.img linux515-x86_64.kver vmlinuz-5.15-x86_64
Perhaps I try making an efi folder within the /boot directory and maybe that’ll work for the grub-install?
i really dont know … and whats the output from:
ls /boot/efi
I created an efi folder within the /boot directory and then I tried mounting it again and got the same result. Also, I just tried this:
sudo ls /boot/efi
and got nothing.
hm so you dont have anything there… you had a good idea to create a directory in there
sudo mkdir /boot/efi
Yup, that’s the command I used to create that /boot/efi directory and it sounded really promising but alas, didn’t do much. Also, after I made that directory, I did
cd /boot
/boot ls
amd-ucode.img initramfs-5.15-x86_64-fallback.img linux515-x86_64.kver
efi initramfs-5.15-x86_64.img memtest86+
grub intel-ucode.img vmlinuz-5.15-x86_64
I noticed that the efi folder was there after and was even highlighted as the same color as grub and memtest86+.
you need to mount it now:
sudo mount /dev/nvme0n1p1 /boot/efi
There’s confusion going on.
p1 is your ESP
p5 is your root partition
Reboot into a live ISO session (from the USB again) to start all over. I fear you’re creating directories redundantly.
After you reboot, setup your mounts like so:
sudo mount /dev/nvme0n1p5 /mnt
sudo mount /dev/nvme0n1p1 /mnt/boot/efi
Now you can use manjaro-chroot -a to enter a chroot session. It is inside of this chroot that you can run the Grub commands.
Alright, I’ll restart the live ISO and see where it goes. Brb.
why does he need to mount also the root partition when he only needs to reinstall grub?
Because Grub needs the entire root filesystem (and boot directory) available; not just the EFI system partition (“esp”).
Chroot’ing into the full root filesystem is what contains all the Grub commands to the proper system.
i understand now, thank you, good to know