[CLOSED] os-prober detecting no OS / GRUB making mistakes in entry

the_pumpkin_man · 2019-12-03 15:27:44

So, I followed the wiki for installing an encrypted with LVM on LUKS and a separate unencrypted /boot on an USB key. So everything is working for this system. The problem is with GRUB and os-prober as the title says.

I have actually 4 systems on my computer, they are all working :
- My fresh installed Arch Linux as described above (1)
- An old Arch Linux system, my main system, unencrypted, just the basic install with GNOME (2)
- Kali Linux (3)
- Windows 10 (4)

When I used the GRUB from (2) before I had my new Arch Linux system, everything worked. os-prober was able to detect (3) and (4), and no problem with GRUB.
Now, Im trying to use the GRUB from (1), because it would be complicated to detect (1) with (2) and I want (1) to be my main system. But os-prober doesnt find anything. So I tried to make it detect the OSs by mounting them, what I did, so it detected them. But after installing GRUB and launching (2), it froze. The problem was at the initrd line of the /boot/grub/grub.cfg on the USB key (remember, my /boot is on the key). It was only

initrd /boot/intel-ucode.img

, but should be

initrd /boot/intel-ucode.img /boot/initramfs-linux-lts.img

. After manually editing grub.cfg to change this, it finally worked. But I have two questions :
- How can I make os-prober work ? Is it not working because my /boot is on an USB stick ?
- How can I make GRUB work for Arch Linux ? (I actually didnt tried to launch Windows or Kali Linux)

Thanks in advance for reading all this and for your help

Last edited by the_pumpkin_man (2019-12-14 09:57:13)

the_pumpkin_man · 2019-12-14 09:51:30

Well, finally ... os-prober is now working, I have no idea why. It probably needed some package I installed, I would like to know which one. And for GRUB misconfiguring the Arch Linux entry, I will try to find a workaround.
So, closing this thread.

WorMzy · 2019-12-14 11:56:38

Please don't use "[closed]", as this is used by the system to mark a thread which is no longer accessible for new posts. Use e.g. [solved] instead: https://wiki.archlinux.org/index.php/Co … ow_to_post

In regards to your problem, I don't use grub, but I believe there was a bug with os-prober requiring the command 'which' to be installed, but this may have been fixed upstream to use a more portable solution.

Arch Linux

#1 2019-12-03 15:27:44

[CLOSED] os-prober detecting no OS / GRUB making mistakes in entry

#2 2019-12-14 09:51:30

Re: [CLOSED] os-prober detecting no OS / GRUB making mistakes in entry

#3 2019-12-14 11:56:38

Re: [CLOSED] os-prober detecting no OS / GRUB making mistakes in entry

Board footer