did you chroot correctly?
#the same arch grub issue people have had
hardy lark
... grub-issue
torpid cargoBOT
#8780 📣 -issue https://endeavouros.com/news/full-transparency-on-the-grub-issue/
sterile canopy
and do that
hardy lark
.aw chroot
torpid cargoBOT
mortal mantle
.aw chroot
the chroot in the arch wiki is bad
it doesnt use rbinds and doesnt set then as slave
did you turn it into an slave mount
cus otherwise it wouldnt be unmountable
grub-install --target=x86_64-efi --efi-directory=/path/to/your/esp
then grub-mkconfig -o /boot/grub/grub.cfg
your efi partition's mountpoint
esp
efi system partition
when you rbind
if you create a file from the host
it will also show in the bind vice versa
but if you turn the bind into a slave mount
you creating a file on the host will still show in the bind
but creating a file on the bind wont show on the host
depends
sure
but where is it mounted
cat /etc/fstab | grep vfat
ok
sudo mount /dev/sda3 /boot/efi
mortal mantle
grub-install --target=x86_64-efi --efi-directory=/path/to/your/esp
then do this but /boot/efi instead
| pipes the output to grep
which in turn finds the line with vfat
you arent
yeah
you have to 💀
tired vortex
if you're chrooted can you just reinstall your kernel?
ohhh, fun, never seen that before
probably a good idea, but I'll search first
wife's gonna kill me, it's 3am and I'm not in bed xD
do you use nvidia?
ahh doesn't matter, didn't read issue properly
meh, I say chroot in and try reinstalling your kernel and your drivers
iObz might have better information?
as someone who does that a lot, let me say, don't hold yourself to it, it will be fixable still in the morning
only other thing I can think is there is still some mis match, like UEFI BIOS mode related
mortal mantle
oh oh god
not this 
the only fix to this that ik is redeploying the kernel and initrd
pacman -S linux
or reformatting the esp and redoing all of it
tired vortex
oh oh god
not this <:empty:904500974767452192>
the only fix to this that ik is ...
Out of interest is the cause related to uefi/ bios?
mortal mantle
Out of interest is the cause related to uefi/ bios?
no
it's the filesystem hosting the file grub is trying to find
which in this case is the kernel
tired vortex
@hardy lark what filesystem are you using for root?
Ext4? Btrfs? Zfs? Something else?
lsblk -f or fdisk -l might tel you if you’re unsure.
And what was your mount command for chrooting?