just installed manjaro using this guide: root-tip-dual-boot-manjaro-and-windows/1164 from the manjaro forums.
Now I get grub rescue unknown filesystem and I have no idea how to fix it. I reinstalled manjaro and that didnt fix it either.
Hello @johnsmith1234 
That means that the filesystem of the boot partition is not known. Probably it point to the wrong partition?
Please boot a live session, open a terminal and post these outputs:
manjaro-chroot -a
and then:
sudo parted -l
lsblk -f
cat /etc/fstab
grub-probe: error: cannot find a GRUB drive for /dev/sda1. Check your device.map.
grub-probe: error: cannot find a GRUB drive for /dev/sda1. Check your device.map.
==> Mounting (ManjaroLinux) [/dev/nvme2n1p4]
--> mount: [/mnt]
--> mount: [/mnt/boot/efi]
--> mount: [/mnt/home]~~~
~~~[manjaro /]# sudo parted -l
Model: SanDisk Cruzer Glide (scsi)
Disk /dev/sda: 15.7GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:
Number Start End Size Type File system Flags
2 2597MB 2601MB 4194kB primary esp
Model: Sabrent Rocket 4.0 Plus (nvme)
Disk /dev/nvme0n1: 2000GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
1 17.4kB 134MB 134MB msftres
2 134MB 2000GB 2000GB ntfs msftdata
Model: WDS500G3X0C-00SJG0 (nvme)
Disk /dev/nvme2n1: 500GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
1 17.4kB 134MB 134MB msftres
2 134MB 672MB 538MB fat32 msftdata
3 672MB 2820MB 2147MB linux-swap(v1) swap
4 2820MB 24.3GB 21.5GB ext4 legacy_boot
5 24.3GB 45.8GB 21.5GB ext4
Model: Samsung SSD 980 PRO 250GB (nvme)
Disk /dev/nvme1n1: 250GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
1 17.4kB 134MB 134MB msftres
2 135MB 240MB 105MB fat32 boot, esp
3 764MB 198GB 197GB ntfs msftdata
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
loop0
loop1
loop2
loop3
sda
|-sda1
`-sda2
nvme0n1
|-nvme0n1p1
`-nvme0n1p2
nvme2n1
|-nvme2n1p1
|-nvme2n1p2 511.7M 0% /boot/efi
|-nvme2n1p3
|-nvme2n1p4 11.7G 35% /
`-nvme2n1p5 18.5G 0% /home
nvme1n1
|-nvme1n1p1
|-nvme1n1p2
`-nvme1n1p3
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a device; this may
# be used with UUID= as a more robust way to name devices that works even if
# disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
UUID=10B0-20FD /boot/efi vfat umask=0077 0 2
UUID=164bcd62-9fcc-49fb-ab3c-0fd4d7061f5c swap swap defaults,noatime 0 0
UUID=f9e34148-b186-4d22-9e15-26be906169a6 / ext4 defaults,noatime 0 1
UUID=7ce57531-781d-44b6-9c07-5fd4f20f1c33 /home ext4 defaults,noatime 0 2~~~please edit your post and put ~~~ at the beginning and at the end of each output. It will avoid using markdown formatting and display it as plain code. thanks.
Like this
code
more code
Replace the flag here with boot, esp, or just boot, if it is a efi partition.
Since i guess that this is the root partition, remove the flag here.
Flags can be changed in gparted for example instantly.
Btw could you explain, why here are 2 partitions? Are these 2 EFI Partitions? If grub points to the first partition, then no wonder that it says unknown filesystem, because there is none.
AND
sorry, lsblk should also show the UUIDs. This way you can’t check the UUIDs in fstab.
so you want me to reinstall?
theres 2 partitions because i was looking up how to fix the grub issue and i saw a post that said i can move it and itll work so i move that to my 3rd drive
If it is easier for you? However… my guess is: the issue is that the wrong efi partition has been mounted. Please run again lsblk -f, but this time please the whole output with UUIDs. So one could check for sure that the UUIDs at fstab match.
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
loop0
loop1
loop2
loop3
sda
|-sda1
`-sda2
nvme0n1
|-nvme0n1p1
`-nvme0n1p2
nvme2n1
|-nvme2n1p1
|-nvme2n1p2 511.7M 0% /boot/efi
|-nvme2n1p3
|-nvme2n1p4 11.7G 35% /
`-nvme2n1p5 18.5G 0% /home
nvme1n1
|-nvme1n1p1
|-nvme1n1p2
`-nvme1n1p3
it should look like this:
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
sda
├─sda1 vfat FAT32 4CB8-19FE
├─sda2 btrfs 4f61283a-72c4-4a6f-990e-b64bd021f34e
├─sda3 vfat FAT32 5B26-F5F2 298,7M 0% /boot/efi
└─sda4 btrfs manjaro c2477149-41ea-47fb-897e-40c856451c4e 27,6G 71% /run/timeshift/backup
/home
/swap
/
Try this:
lsblk -o PATH,UUID,FSTYPE,MOUNTPOINT
PATH UUID FSTYPE MOUNTPOINT
/dev/loop0
/dev/loop1
/dev/loop2
/dev/loop3
/dev/sda
/dev/sda1
/dev/sda2
/dev/nvme0n1
/dev/nvme2n1
/dev/nvme2n1p1
/dev/nvme2n1p2 /boot/efi
/dev/nvme2n1p3
/dev/nvme2n1p4 /
/dev/nvme2n1p5 /home
/dev/nvme1n1
/dev/nvme0n1p1
/dev/nvme0n1p2
/dev/nvme1n1p1
/dev/nvme1n1p2
/dev/nvme1n1p3
[manjaro /]#
you have to check lsblk -fs
Before chroot
ok like @stephane mentioned. Open a new terminal and type it in there. Not in the chrooted terminal.
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
loop0
squash 4.0 0 100% /run/miso/sfs/livefs
loop1
squash 4.0 0 100% /run/miso/sfs/mhwdfs
loop2
squash 4.0 0 100% /run/miso/sfs/desktopfs
loop3
squash 4.0 0 100% /run/miso/sfs/rootfs
sda1 iso966 Jolie MANJARO_XFCE_2107
│ 2021-06-14-15-23-05-00
└─sda
iso966 Jolie MANJARO_XFCE_2107
2021-06-14-15-23-05-00 0 100% /run/miso/bootmnt
sda2 vfat FAT12 MISO_EFI
│ 0545-B0D1
└─sda
iso966 Jolie MANJARO_XFCE_2107
2021-06-14-15-23-05-00 0 100% /run/miso/bootmnt
nvme2n1p1
│
└─nvme2n1
nvme2n1p2
│ vfat FAT32 NO_LABEL
│ 10B0-20FD
└─nvme2n1
nvme2n1p3
│ swap 1 164bcd62-9fcc-49fb-ab3c-0fd4d7061f5c
└─nvme2n1
nvme2n1p4
│ ext4 1.0 f9e34148-b186-4d22-9e15-26be906169a6
└─nvme2n1
nvme2n1p5
│ ext4 1.0 7ce57531-781d-44b6-9c07-5fd4f20f1c33
└─nvme2n1
nvme0n1p1
│
└─nvme0n1
nvme0n1p2
│ ntfs Games 1FC4C4CEF619B833
└─nvme0n1
nvme1n1p1
│
└─nvme1n1
nvme1n1p2
│ vfat FAT32 SYSTEM
│ C0EE-86B9
└─nvme1n1
nvme1n1p3
Ok that is correct. Thanks.
Could you also post your efi entries?
efibootmgr -v
thanks
BootCurrent: 0011
Timeout: 1 seconds
BootOrder: 0011,0000,0009,0001,000F,0012,0005,0010
Boot0000* Windows Boot Manager HD(2,GPT,a35f7c39-3d4b-46aa-a0fa-db528bf26333,0x40800,0x32000)/File(\EFI\MANJARO\GRUBX64.EFI)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}....................
Boot0001* Manjaro HD(2,GPT,f312eec3-ce40-2340-a511-41775e7958f2,0x40022,0x1007de)/File(\EFI\MANJARO\GRUBX64.EFI)
Boot0005 Hard Drive BBS(HD,,0x0)/VenHw(5ce8128b-2cec-40f0-8372-80640e3dc858,0200)..GO..NO..........S.a.b.r.e.n.t. .R.o.c.k.e.t. .4...0. .P.l.u.s...................\.,.@.r.d.=.X..........A..........................dy.C` .......>..Gd-.;.A..MQ..L.0.3.F.1.0.7.0.C.0.E.4.4.1.9.3.2.1.6.7.9........BO..NO..........S.a.m.s.u.n.g. .S.S.D. .9.8.0. .P.R.O. .2.5.0.G.B...................\.,.@.r.d.=.X..........A.......................................%8..Q^v.....4..Gd-.;.A..MQ..L.S.5.P.1.N.G.0.N.9.1.0.7.0.5.Y........BO..NO..........W.D.S.5.0.0.G.3.X.0.C.-.0.0.S.J.G.0...................\.,.@.r.d.=.X..........A........................................DJF...........Gd-.;.A..MQ..L.2.0.3.8.8.M.4.4.7.3.1.1........BO
Boot0009* Windows Boot Manager HD(2,GPT,a35f7c39-3d4b-46aa-a0fa-db528bf26333,0x40800,0x32000)/File(\EFI\MICROSOFT\BOOT\BOOTMGFW.EFI)..BO
Boot000F* UEFI OS HD(2,GPT,f312eec3-ce40-2340-a511-41775e7958f2,0x40022,0x1007de)/File(\EFI\BOOT\BOOTX64.EFI)..BO
Boot0010 USB KEY BBS(HD,,0x0)/VenHw(5ce8128b-2cec-40f0-8372-80640e3dc858,0b00)..GO..NO..........S.a.n.D.i.s.k...................\.,.@.r.d.=.X..........A.............................>..Gd-.;.A..MQ..L.4.C.5.3.0.0.0.1.0.3.0.5.0.6.1.0.5.3.9.2........BO
Boot0011* UEFI: SanDisk PciRoot(0x0)/Pci(0x1,0x2)/Pci(0x0,0x0)/USB(6,0)/CDROM(1,0x4d62c0,0x8000)..BO
Boot0012* UEFI: SanDisk, Partition 2 PciRoot(0x0)/Pci(0x1,0x2)/Pci(0x0,0x0)/USB(6,0)/HD(2,MBR,0x0,0x4d62c0,0x2000)..BO
Interesting the entries Boot0000 and Boot0001 point to:
\EFI\MANJARO\GRUBX64.EFI
But Boot0000 has additional parameter for windows.
Change the Bootorder:
sudo efibootmgr --bootorder 0001,000F,0011,0012,0005,0009,0010,0000
Boot0001 should be the correct entry.
These one should be the windows one.
1 Like
do i restart?
yes restart after changing the bootorder. If this take not effect, try to change that at your UEFI at boottime.
1 Like
you are a genius. dual boot is working now and i can get into windows and manjaro. can you tell me what was happening?