You are not logged in.
Pages: 1
Hello, for the last couple of days I have been trying to add my windows 10 install as a menu in grub (installed on a another ssd), I have tried everything I can find here on the forums but still cant get it to work. I have try adding it manually and useing os-prober. If I use the programs called grub-customizer I can see windows as an entry but I still wont show up in my grub. I have also tried with a brand new windows install.
Last edited by ozynt (2021-10-17 20:38:17)
Offline
Walking on toes here.
I am not an expert in this.
Does the secondary ssd have its own efi boot partition? or a Master Boot record? (From where the list of partitions and boot volumes etc is stored)
Also do you mean another ssd or another partition ? ( I haven't come across a 2 ssd rig with OSes on both of them so I am just curious)
Maybe grub is not probing the other drive for potential OSes?
Can you boot windows separately?
Last edited by DireWolf (2021-10-10 08:16:47)
Offline
Have you checked the os-prober setting in grub-config?
The default setting is not to use os-prober in grub.
You need to change this.
Enter the following command with root privileges.
# sed -i 's/GRUB_DISABLE_OS_PROBER="true"/GRUB_DISABLE_OS_PROBER="false"/g' /usr/bin/grub-mkconfig
# grub-install --target=x86_64-efi --efi-directory=/boot --bootloader-id=GRUB
# grub-mkconfig -o /boot/grub/grub.cfg
Offline
Walking on toes here.
I am not an expert in this.
Does the secondary ssd have its own efi boot partition? or a Master Boot record? (From where the list of partitions and boot volumes etc is stored)
Also do you mean another ssd or another partition ? ( I haven't come across a 2 ssd rig with OSes on both of them so I am just curious)
Maybe grub is not probing the other drive for potential OSes?
Can you boot windows separately?
Yeah, I can select windows in my bios boot menu.
Offline
Have you checked the os-prober setting in grub-config?
The default setting is not to use os-prober in grub.
You need to change this.
Enter the following command with root privileges.
# sed -i 's/GRUB_DISABLE_OS_PROBER="true"/GRUB_DISABLE_OS_PROBER="false"/g' /usr/bin/grub-mkconfig
# grub-install --target=x86_64-efi --efi-directory=/boot --bootloader-id=GRUB
# grub-mkconfig -o /boot/grub/grub.cfg
When Im run grub install I get this output
[ozynt@arch ~]$ sudo grub-install --target=x86_64-efi --efi-directory=/boot --bootloader-id=GRUB
Installing for x86_64-efi platform.
grub-install: error: /boot doesn't look like an EFI partition.
Offline
Then, what about entering the command as below, excluding the second item?
Oh, and check if ntfs-3g is also installed.
# sudo pacman -S ntfs-3g
# sed -i 's/GRUB_DISABLE_OS_PROBER="true"/GRUB_DISABLE_OS_PROBER="false"/g' /usr/bin/grub-mkconfig
# grub-mkconfig -o /boot/grub/grub.cfg
Last edited by sephid86 (2021-10-10 22:20:05)
Offline
# sed -i 's/GRUB_DISABLE_OS_PROBER="true"/GRUB_DISABLE_OS_PROBER="false"/g' /usr/bin/grub-mkconfig
no dont do that, follow the wiki and enable it correctly:
https://wiki.archlinux.org/title/GRUB#D … ng_systems
Offline
You also need to make sure that the partition your Windows bootloader is on is mounted somewhere for os-prober to find a bootable entry. Assuming an EFI boot for windows you will have a distinct FAT partition on your windows drive, you need to mount that "somewhere" before running grub-mkconfig with os_prober enabled (... and I agree with the above, rather than trying to sed the installation script which will break when GRUB updates, actually adjust the relevant configuration file instead)
Offline
sephid86 wrote:# sed -i 's/GRUB_DISABLE_OS_PROBER="true"/GRUB_DISABLE_OS_PROBER="false"/g' /usr/bin/grub-mkconfig
no dont do that, follow the wiki and enable it correctly:
https://wiki.archlinux.org/title/GRUB#D … ng_systems
Why is vim allowed and not sed?
the result is the same
Can you explain why you shouldn't use sed ?
Last edited by sephid86 (2021-10-11 09:38:14)
Offline
Not sure where you get vim from, but you are manipulating the "wrong" file.
You are manipulating an "executable" (... yes I know it's a script) that's not intended to be edited manually. The minimal result will be that your change will get removed when the GRUB package updates and might lead to unexpected results on subsequent grub-mkconfig invocations. GRUB has configuration files for this purpose and that's where it's intended you make configuration changes.
Last edited by V1del (2021-10-11 09:40:25)
Offline
Not sure where you get vim from, but you are manipulating the "wrong" file.
You are manipulating an "executable" (... yes I know it's a script) that's not intended to be edited manually. The minimal result will be that your change will get removed when the GRUB package updates and might lead to unexpected results on subsequent grub-mkconfig invocations. GRUB has configuration files for this purpose and that's where it's intended you make configuration changes.
You're not good at explaining.
But I understand and I understand what you mean.
Recognize and respect your words.
You are right.
I will take care in the future
Thank you.
Offline
Update:
I reinstalled windows and Arch useing this guide: https://youtu.be/_kwNzRi-UcI
Still could not get it to work. I could still see in the grub editor that windows was there but when I boot into grub I wont show up. So after some testing I removed my Arch entry to the grub and now when I booted I saw the Windows entry and it worked. But now I could not see the arch entry for grub. So I wiped my arch drive and installed Manjaro just to test if there was an issue with useing 1 ssd per system. (One for windows and one for arch) In Manjaro it worked perfect. So now I want to wipe my Manjaro install and try again…
Does anyone here know what Manjaro is useing as bootloader? Is there any alternatives to grub?
Thanks in advance
Im gonna try to follow this guide later today and see how it goes. https://youtu.be/LGhifbn6088
Last edited by ozynt (2021-10-17 13:03:55)
Offline
Offline
2nd update: after following this video I got it working
https://youtu.be/LGhifbn6088
Offline
Pages: 1