It is a know issue for Arch based systems and is caused by a recent change in grub
` ~ sudo umount /dev/sda5 
umount: /dev/sda5: not mounted.
~ sudo fsck 32 ✘
fsck from util-linux 2.38.1
~
~ grub-install INT ✘
Installing for x86_64-efi platform.
grub-install: error: cannot find EFI directory.
~ `
i dont know what that is, told you to use formatting, or just post a picture …
try the commands that aarhus linked above:
The grub-install should match the system - from your previous topic - I think your system is BIOS MBR.
There doesn’t seem to be an EFI system partition present in your disk layout and one partition sda3 has no info which lead me to think sda3 is an MBR extended partition holding sda4, -5, -6.
First verify if your system supports and is booted as efi - if you get a long list - your system supports efi and is booted as efi
ls /sys/firmware/efi/efivars
Next check the output of this command - if your get Disklabel type: mbr then your system supports efi but is installed as mbr - early Windows 8 was installed as bios/mbr
sudo fdisk -l /dev/sda
If the manjaro-chroot command fails - you must mount the partition manually and do a manual chroot
sudo mount /dev/sda5 /mnt
sudo chroot /mnt
As your disk is mbr formatted - you must use grub-install for a bios/mbr system - which you can find in the linked wiki.
sudo grub-install --force --target=i386-pc --recheck --boot-directory=/boot /dev/sda
Then rebuild the configuation
sudo grub-mkconfig -o /boot/grub/grub.cfg
When done - exit the chroot and reboot
exit
reboot
This is what I got from copying the console and yes I tried the first command that he sent
Im unsure if I should run these command in chroot so im gonna just try without chroot ok?
Alr so it seems to be EFI and disk label is gpt. So since its not mbr should I still try sudo grub-install --force --target=i386-pc --recheck --boot-directory=/boot /dev/sda or no ?
check with this command if you are using bios or uefi:
test -d /sys/firmware/efi && echo efi || echo bios
There’s something wrong with this it doesn’t return anything. On the side there’s a red thing saying INT and a cross
maybe there was a typo if you were writing it down, instead of copying …
you can check with this command:
so it looks like its efi, also your comment here:
so chroot first if you are not, and then install for efi:
grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=manjaro --recheck
if there are none errors run:
grub-mkconfig -o /boot/grub/grub.cfg
you are using btrfs, so you cant use manjaro-chroot -a command with it …
but it looks that it reinstalled the grub without errors …
but the update grub didnt detected any kernels…
post output from this so that we can properly chroot:
lsblk -o PATH,PTTYPE,PARTTYPE,FSTYPE,PARTTYPENAME
edit: checking above output you are not using btrfs, but ext4 so i dont know why the grub log mentions btrfs …
did you run fsck as i told you?
I think I ran fsck
[manjaro /]# lsblk -o PATH,PTTYPE,PARTTYPE,FSTYPE,PARTTYPENAME
PATH PTTYPE PARTTYPE FSTYPE PARTTYPENAME
/dev/loop0
/dev/loop1
/dev/loop2
/dev/loop3
/dev/sda
/dev/sda1
/dev/sda2
/dev/sda3
/dev/sda4
/dev/sda5
/dev/sda6
/dev/sdb
/dev/sdb1
/dev/sdb2
/dev/sr0
[manjaro /]#
~ sudo fsck /dev/sda5 INT ✘ 22m 59s
fsck from util-linux 2.38.1
e2fsck 1.46.5 (30-Dec-2021)
/dev/sda5: clean, 1030990/8749056 files, 26970776/34984960 blocks
~
this lsblk output doesnt show anything… and i told you to use formatting …
it all points to a broken file system…
do you copy the commands or write them down?
I copy them. O oops I think I used it in chroot
~ lsblk -o PATH,PTTYPE,PARTTYPE,FSTYPE,PARTTYPENAME INT ✘
PATH PTTYPE PARTTYPE FSTYPE PARTTYPENAME
/dev/loop0 squashfs
/dev/loop1 squashfs
/dev/loop2 squashfs
/dev/loop3 squashfs
/dev/sda gpt
/dev/sda1 gpt de94bba4-06d1-4d40-a16a-bfd50179d6ac ntfs Windows recovery environment
/dev/sda2 gpt c12a7328-f81f-11d2-ba4b-00a0c93ec93b vfat EFI System
/dev/sda3 gpt e3c9e316-0b5c-4db8-817d-f92df00215ae Microsoft reserved
/dev/sda4 gpt ebd0a0a2-b9e5-4433-87c0-68b6b72699c7 ntfs Microsoft basic data
/dev/sda5 gpt 0fc63daf-8483-4772-8e79-3d69d8477de4 ext4 Linux filesystem
/dev/sda6 gpt de94bba4-06d1-4d40-a16a-bfd50179d6ac ntfs Windows recovery environment
/dev/sdb dos iso9660
/dev/sdb1 dos 0x0 iso9660 Empty
/dev/sdb2 dos 0xef vfat EFI (FAT-12/16/32)
/dev/sr0
If you interrupted the update just install kernel(s) again.
he cant run pacman/pamac commands, update-grub also doesnt work, he gets bus error
looks better … post output from:
mhwd-kernel -li
Currently running: 5.15.60-1-MANJARO (linux515)
The following kernels are installed in your system:
warning: database file for 'core' does not exist (use '-Sy' to download)
warning: database file for 'extra' does not exist (use '-Sy' to download)
warning: database file for 'community' does not exist (use '-Sy' to download)
warning: database file for 'multilib' does not exist (use '-Sy' to download)
* linux515
warning: database file for 'core' does not exist (use '-Sy' to download)
warning: database file for 'extra' does not exist (use '-Sy' to download)
warning: database file for 'community' does not exist (use '-Sy' to download)
warning: database file for 'multilib' does not exist (use '-Sy' to download)