GRUB: Filesystem unknown

Hello everyone!

This week I deleted my Manjaro partition using Windows (the /) and now I can’t boot to EndeavourOS, using Manjaro’s GRUB nor EndeavourOS’ GRUB. I can only boot to Windows. GRUB says “Filesystem unknown”. Any ideas on how to solve this?

Thank you very much!

I would try booting off the installer ISO, chrooting into your system using arch-chroot and then running sudo grub-mkconfig -o /boot/grub/grub.cfg.

If that doesn’t work, that boot off the ISO, go back into the arch-chroot and re-install grub.

If you need more detailed instructions for any of that, please let us know.

2 Likes

What is the output of efibootmgr?

This will tell you if you need to re-order your boot entries, chroot update grub, or chroot re-install grub.

3 Likes
[liveuser@eos-2021.02.03 ~]$ efibootmgr
BootCurrent: 0004
Timeout: 0 seconds
BootOrder: 0001,0003,0002,0006,0000,0005,2001,2002,2003
Boot0000* Unknown Device: 
Boot0001* HDD0: TOSHIBA MQ04ABF100
Boot0002* Windows Boot Manager
Boot0003* Manjaro
Boot0004* USB HDD: KingstonDataTraveler 2.0
Boot0005* EndeavourOS
Boot0006* Unknown Device: 
Boot2001* EFI USB Device
Boot2002* EFI DVD/CDROM
Boot2003* EFI Network
[liveuser@eos-2021.02.03 ~]$ 

How can I do that? Through the terminal?

sudo efibootmgr -o 0005,0002,0003,0001,0004,2001,2002,2003

Edit: After we could remove some of those entries that are not needed such as the manjaro.

1 Like

To remove any entries not needed use the following.

sudo efibootmgr -b 0003 -B

Edit: This will remove the Manjaro entry and you can remove any others not required.

1 Like

Ok so I just need to put that on the terminal?
If so, here’s the output:

[liveuser@eos-2021.02.03 ~]$ sudo efibootmgr -o 0005,0002,0003,0001,0004,2001,2002,2003
BootCurrent: 0004
Timeout: 0 seconds
BootOrder: 0005,0002,0003,0001,0004,2001,2002,2003
Boot0000* Unknown Device: 
Boot0001* HDD0: TOSHIBA MQ04ABF100
Boot0002* Windows Boot Manager
Boot0003* Manjaro
Boot0004* USB HDD: KingstonDataTraveler 2.0
Boot0005* EndeavourOS
Boot0006* Unknown Device: 
Boot2001* EFI USB Device
Boot2002* EFI DVD/CDROM
Boot2003* EFI Network
[liveuser@eos-2021.02.03 ~]$ 


Yes just put it in the terminal.

1 Like

Now I can reboot?

1 Like

You can check it after too.

sudo efibootmgr

1 Like

I’ve rebooted and it still goes to GRUB Rescue with the same error :frowning:

Is it set to boot from EndeavourOS now?

If it’s set to boot from endeavourOS and you are getting this problem you may have to use the live iso and arch-chroot into the system to fix grub.

Edit: After arch-chroot into the system then use the procedure listed here to reinstall grub for UEFI.

1 Like

What’s wrong?

[root@archiso /]# os-prober
/dev/sda1@/efi/Microsoft/Boot/bootmgfw.efi:Windows Boot Manager:Windows:efi
grub-probe: error: cannot find a GRUB drive for /dev/sdb1.  Check your device.map.
[root@archiso /]# grub-mkconfig -o /boot/grub/grub.cfg
/usr/bin/grub-mkconfig: line 248: /boot/grub/grub.cfg.new: No such file or directory
[root@archiso /]# 

Did you arch-chroot first and mount the proper drives?

Edit: You have to boot on the live ISO and follow the instructions in the first one to arch-chroot and mount the drives on the installed system then follow the UEFI instructions to reinstall grub.

1 Like

Yes I followed those steps. Is there a way I can unmount and mount again the drives to check what’s wrong?

One thing: Wouldn’t it be better to just reinstall the system? My /home is on a separate partition.

Well that’s up to you but this will teach you how to repair your system when this happens or something else that you need to arch-chroot to be able to install something. It would be a good exercise for learning.

1 Like

Hmm that’s right. What can I do now? How can I unmount the drives?

I think the command is umount.

Edit: sudo umount /mnt

Edit2: I think you can just type exit also?

1 Like