Jump to content
9 minutes ago, Bharath1910 said:

I have 2 physical HDD 1 has Garuda Linux (Arch based) another one has Windows 10 when I boot into grub menu.. I can't see windows

What happens if you change the boot order in bios to boot to the HDD containing windows?

Attention is what makes life meaningful.

Also, please quote me for a reply. 🙂

Link to comment
https://linustechtips.com/topic/1302308-grub-menu-problem/#findComment-14455218
Share on other sites

Link to post
Share on other sites

2 hours ago, mahyar said:

well its not much of surprise because they don't share a bootloader partition

This has nothing to do with the problem, grub can load an OS from any disk and partition (if it is a sensible one; it might not do something like booting a DOS-based OS from an extended partition etc.).

3 hours ago, Bharath1910 said:

It is very overwhelming for me... but thanks I will try to understand it

Post  the output of "sudo lsblk" and "sudo blkid" here, that way we can help.

 

The page can be daunting as it has loads of information out of which not all is relevant to you. To summarize the process is roughly:

  1. install os-prober (it is not installed per default in Arch),
  2. mount your windows partition and then
  3. run grub-mkconfig (as outlined earlier on that page).

With the help of above commands, people can probably give you the exact command needed to enable grub detecting Windows.

 

(in case you ever re-run grub-mkconfig, you need to remount the Windows partition less grub-mkconfig will overwrite the configuration without Windows entries)

Link to comment
https://linustechtips.com/topic/1302308-grub-menu-problem/#findComment-14456123
Share on other sites

Link to post
Share on other sites

8 hours ago, Bharath1910 said:

It is very overwhelming for me... but thanks I will try to understand it

 

All you have to do is install os-prober:

 

sudo pacman -S os-prober

Then mount the Windows partitions, and run: 

 

sudo grub-mkconfig -o /boot/grub/grub.cfg

 

Link to comment
https://linustechtips.com/topic/1302308-grub-menu-problem/#findComment-14456930
Share on other sites

Link to post
Share on other sites

3 hours ago, gardotd426 said:

All you have to do is install os-prober:

 


sudo pacman -S os-prober

Then mount the Windows partitions, and run: 

 


sudo grub-mkconfig -o /boot/grub/grub.cfg

 

I can't mount those drives.. bcz it is NTFS
and it says unmounted and no option to mount it

Screenshot__2.png

Link to comment
https://linustechtips.com/topic/1302308-grub-menu-problem/#findComment-14457326
Share on other sites

Link to post
Share on other sites

3 hours ago, gardotd426 said:

All you have to do is install os-prober:

 


sudo pacman -S os-prober

Then mount the Windows partitions, and run: 

 


sudo grub-mkconfig -o /boot/grub/grub.cfg

 

Generating grub configuration file ...
Found theme: /usr/share/grub/themes/garuda/theme.txt
Found linux image: /boot/vmlinuz-linux-tkg-bmq
Found initrd image: /boot/intel-ucode.img /boot/initramfs-linux-tkg-bmq.img
Found fallback initrd image(s) in /boot: initramfs-linux-tkg-bmq-fallback.img
Detecting snapshots ...
Info: Separate boot partition not detected 
Found snapshot: 2021-02-05 09:06:19 | timeshift-btrfs/snapshots/2021-02-05_09-06-19/@
Found snapshot: 2021-02-04 19:55:54 | timeshift-btrfs/snapshots/2021-02-04_19-55-54/@
Found snapshot: 2021-02-04 18:50:58 | timeshift-btrfs/snapshots/2021-02-04_18-50-58/@
Found snapshot: 2021-02-04 18:42:36 | timeshift-btrfs/snapshots/2021-02-04_18-42-36/@
Found snapshot: 2021-02-04 18:31:03 | timeshift-btrfs/snapshots/2021-02-04_18-31-03/@
Found snapshot: 2021-02-04 15:37:06 | timeshift-btrfs/snapshots/2021-02-04_15-37-06/@
Found 6 snapshot(s)
Found memtest86+ image: /boot/memtest86+/memtest.bin
done

I got this after running commands given by you 

Link to comment
https://linustechtips.com/topic/1302308-grub-menu-problem/#findComment-14457327
Share on other sites

Link to post
Share on other sites

3 hours ago, gardotd426 said:

All you have to do is install os-prober:

 


sudo pacman -S os-prober

Then mount the Windows partitions, and run: 

 


sudo grub-mkconfig -o /boot/grub/grub.cfg

 

 

8 hours ago, Wild Penquin said:

This has nothing to do with the problem, grub can load an OS from any disk and partition (if it is a sensible one; it might not do something like booting a DOS-based OS from an extended partition etc.).

Post  the output of "sudo lsblk" and "sudo blkid" here, that way we can help.

 

The page can be daunting as it has loads of information out of which not all is relevant to you. To summarize the process is roughly:

  1. install os-prober (it is not installed per default in Arch),
  2. mount your windows partition and then
  3. run grub-mkconfig (as outlined earlier on that page).

With the help of above commands, people can probably give you the exact command needed to enable grub detecting Windows.

 

(in case you ever re-run grub-mkconfig, you need to remount the Windows partition less grub-mkconfig will overwrite the configuration without Windows entries)

I managed to mount those drives..
after running the command I got

Screenshot__3.png

Screenshot_fish _home_bharath_1.png

Link to comment
https://linustechtips.com/topic/1302308-grub-menu-problem/#findComment-14457336
Share on other sites

Link to post
Share on other sites

14 hours ago, gardotd426 said:

All you have to do is install os-prober:

 




sudo pacman -S os-prober

Then mount the Windows partitions, and run: 

 




sudo grub-mkconfig -o /boot/grub/grub.cfg

 

 

4 hours ago, gardotd426 said:

You need to install ntfs-3g with




sudo pacman -S ntfs-3g

And are you sure you had them all successfully mounted when you ran grub-mkconfig? Because what you should get is something like this, note "Found Windows Boot Manager" on there:

 

 

Screenshot_20210205_052452.png

 

33 minutes ago, TorC said:

ntfs-3g  is the first thing to make sure is installed. 

Garuda is Arch-based?  Devs were negligent, IMHO.

 

19 hours ago, Wild Penquin said:

This has nothing to do with the problem, grub can load an OS from any disk and partition (if it is a sensible one; it might not do something like booting a DOS-based OS from an extended partition etc.).

Post  the output of "sudo lsblk" and "sudo blkid" here, that way we can help.

 

The page can be daunting as it has loads of information out of which not all is relevant to you. To summarize the process is roughly:

  1. install os-prober (it is not installed per default in Arch),
  2. mount your windows partition and then
  3. run grub-mkconfig (as outlined earlier on that page).

With the help of above commands, people can probably give you the exact command needed to enable grub detecting Windows.

 

(in case you ever re-run grub-mkconfig, you need to remount the Windows partition less grub-mkconfig will overwrite the configuration without Windows entries)

2021-02-05 20-34-44.mkv

 

Update: I uninstalled the KDE version of Garuda and installed GNOME version of Garuda

now when I ran 
 

sudo pacman -S os-prober

 

I got this error

 

 

 


 

image.png

Link to comment
https://linustechtips.com/topic/1302308-grub-menu-problem/#findComment-14458283
Share on other sites

Link to post
Share on other sites

9 minutes ago, gardotd426 said:

You already have os-prober, then. Garuda apparently uses a forked grub with a forked os-prober. 

 

Just out of curiosity, what's the output of


efibootmgr

?

Literally didn't understood the first line
but is there any fix for this?
or crying is the only last option?

Link to comment
https://linustechtips.com/topic/1302308-grub-menu-problem/#findComment-14458586
Share on other sites

Link to post
Share on other sites

1 minute ago, gardotd426 said:

I mean you only need one entry, mine has two for a different reason, but yeah efibootmgr should show all EFI bootloaders on the system (and doesn't use os-prober), and yours isn't showing Windows. 

So If I install this OS without UEFI
it will work right?

Link to comment
https://linustechtips.com/topic/1302308-grub-menu-problem/#findComment-14458598
Share on other sites

Link to post
Share on other sites

No, you need to be using UEFI. Windows isn't using UEFI, and it needs to be. You would need to reinstall Windows and use UEFI. 

 

Or, you could install refind and use refind instead of grub as your bootloader, and see if that detects Windows. If it doesn't then you're definitely not using UEFI for Windows. 

Link to comment
https://linustechtips.com/topic/1302308-grub-menu-problem/#findComment-14458601
Share on other sites

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×