well , it did change to red color ‘manjaro /’ , so i guessed its already in manjaro-chroot , and continued…
I will try again this time and record everyting.
manjaro-chroot -a
grub-probe: error: cannot find a GRUB drive for /dev/sdb1. Check your device.map.
grub-probe: error: cannot find a GRUB drive for /dev/sdb1. Check your device.map.
==> Detected systems:
--> 0) ManjaroLinux
==> Select system to mount [0-0] :
what should i do now , i tried typing 0 ,ManjaroLinux and it always says You can’t mount 0! or ManjaroLinux!
And whenever i mount root and boot/efi and manjaro-chroot /mnt /bin/bash , i cant use manjaro-chroot -a and i get the error ‘bash: manjaro-chroot: command not found’.
What should i do?
(PS - i am still in live environment.)
Sorry will need someone else with more patience and knowledge with your dozen partitions and weird setup. I can’t help more if you can’t chroot with the manjaro tool.
The error you mentioned refers to a drive you apparently don’t have, I don’t know what’s going on.
I am ready to reinstall manjaro(dual boot) , is there a proper documentation for this? ([HowTo] Dual-boot Manjaro - Windows 10 - Step by Step - Tutorials - Manjaro Linux Forum and [root tip] Dual boot Manjaro and Windows). I have installed manjaro a lot of times and i always get this error.
try typing 1
It is confusing - and I cant replicate because I don’t have this many partitions and drives
it was a bug in an earlier version of that tool
and maybe it is still this way
it tells you to type 0 for the first system
but it only succeeds when you type 1
I chrooted like a few weeks ago, and typed 0, it worked.
Maybe there is still a bug with his system but that’s odd (maybe OLD live environment?)
we just don’t know - I just suggested it since the intuitively correct response didn’t work
[manjaro manjaro]# manjaro-chroot -a
==> Detected systems:
--> 0) ManjaroLinux
==> Select system to mount [0-0] :
1
==> Mounting (ManjaroLinux) [/dev/sda3]
--> mount: [/mnt]
--> mount: [/mnt/boot/efi]
--> mount: [/mnt/home]
[manjaro /]# pacman -Syu grub
:: Synchronizing package databases...
core is up to date
extra is up to date
community is up to date
multilib is up to date
warning: grub-2.04-15 is up to date -- reinstalling
:: Starting full system upgrade...
resolving dependencies...
looking for conflicting packages...
Packages (1) grub-2.04-15
Total Installed Size: 49.06 MiB
Net Upgrade Size: 0.00 MiB
:: Proceed with installation? [Y/n] y
(1/1) checking keys in keyring [######################] 100%
(1/1) checking package integrity [######################] 100%
(1/1) loading package files [######################] 100%
(1/1) checking for file conflicts [######################] 100%
(1/1) checking available disk space [######################] 100%
:: Processing package changes...
(1/1) reinstalling grub [######################] 100%
:: Running post-transaction hooks...
(1/2) Arming ConditionNeedsUpdate...
(2/2) Updating the info directory file...
[manjaro /]# grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=manjaro --recheck
Installing for x86_64-efi platform.
Installation finished. No error reported.
[manjaro /]# grub-mkconfig -o /boot/grub/grub.cfg
Generating grub configuration file ...
Found theme: /usr/share/grub/themes/manjaro/theme.txt
Found linux image: /boot/vmlinuz-5.9-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-5.9-x86_64.img
Found initrd fallback image: /boot/initramfs-5.9-x86_64-fallback.img
grub-probe: error: cannot find a GRUB drive for /dev/sdb1. Check your device.map.
grub-probe: error: cannot find a GRUB drive for /dev/sdb1. Check your device.map.
Adding boot menu entry for UEFI Firmware Settings ...
Found memtest86+ image: /boot/memtest86+/memtest.bin
done
This is exactly what happened everytime except i had to mount chroot manually.
but this error occured all the time and i had to go to grub rescue.
grub-probe: error: cannot find a GRUB drive for /dev/sdb1. Check your device.map.
grub-probe: error: cannot find a GRUB drive for /dev/sdb1. Check your device.map
this time also it goes into grub rescue…
Now that I think about it, isn’t that ‘normal’ because of the USB drive and to be ignored?
yepp, thats normal and not the source of his trouble
Are you sure you have an EFI installation of Manjaro? Aren’t you supposed to have an error with the memtest script (that I removed a while back to stop having the error while running update-grub) on a EFI install? Something’s odd here to me.
To me it looks like
the Windows EFI partition is on the second drive
Now he has got two
and needs to go through Grub on the first partition to boot either System
He probably needs to use the Windows EFI
Not sure - I never had a dual boot system with two drives and Windows partitions on both.
It seems to work ok - just not the way he want’s it to work.
By second drive , You mean nvme0n1 right? , Thats my ssd(128gb) where windows is installed. And i created 200gb partition in my hdd(1tb) where i installed manjaro(root,home,swap). and for boot/efi , when installing i clicked edit on nvme0n1’s efi system and set the mount point as boot/efi. I even tried creating a separate boot partition before in my previous installations , and all of them resulted the same(grub rescue).
when installing i clicked edit on nvme0n1’s efi system and set the mount point as boot/efi.
That didn’t seem to have worked, then.
To be sure, check how the chroot is assembled.
… where which partition actually gets mounted when you enter chroot
two terminals:
- one you will do the chroot in
- and one you use to watch what happens
use, for instance:
mount
before you enter chroot
and then again after you did
from that second terminal
it will show you what got mounted where
It should show
/dev/sda3 on /mnt
I don’t know what /dev/sda5 represents - probably /home
if that is so, it should end up at /mnt/home - but if it’s /home it is not important here
It should also show /dev/nvme0n1p1 mounted to /mnt/boot/EFI (I believe …)
I think this is what should happen but I think that this is not what actually does happen.
Compare that hypothesis to reality 
It mounted properly , i checked while chrooting manually , /mnt was in sda3 , /mnt/boot/efi was in nvme0n1p1.
Then I can’t help you to sort this out.
I’d rather not add confusion and unfounded and untested opinion.
I never had a system with two drives and it is a very long time since I had Windows.
Someone else who has actually done this and knows what he/she is talking about will hopefully help.
I can’t.
Sorry!
So , I disabled fast boot in BIOS , and its fixed. 
This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.