You are not logged in.
Before installing Arch, I had a dual-boot with w10 and ubuntu, during Arch installation I kept the w10 EFI partition and the ubuntu one (just mounted on the latter as the wiki told so). Now w10 just boot if I choose its partition in the BIOS and I still have left the ubuntu partition (that just boots the rescue console) and the GRUB partition that just recognizes Arch.
I already tried installing os-prober, mounting the w10 partition and re-ran the grub-mkconfig, edited the /etc/default/grub file to add the
GRUB_DISABLE_OS_PROBER=falsestatement and this the output:
Using os-prober
lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
sda 8:0 0 223.6G 0 disk
├─sda1 8:1 0 100M 0 part /boot
├─sda2 8:2 0 16M 0 part
├─sda3 8:3 0 173G 0 part
├─sda4 8:4 0 498M 0 part
├─sda5 8:5 0 524M 0 part /efi
├─sda6 8:6 0 4G 0 part [SWAP]
└─sda7 8:7 0 45.5G 0 part /
sdb 8:16 0 931.5G 0 disk
├─sdb1 8:17 0 16M 0 part
├─sdb2 8:18 0 631.5G 0 part
└─sdb3 8:19 0 300G 0 part /home
sudo os-prober
/dev/sda1@/EFI/Microsoft/Boot/bootmgfw.efi:Windows Boot Manager:Windows:efiRe-running grub-mkconfig (it giver an error if I run it with w10 partition mounted)
sudo grub-mkconfig -o /boot/grub/grub.cfg
/usr/bin/grub-mkconfig: line 261: /boot/grub/grub.cfg.new: No such file or directoryWithout w10 mounted:
lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
sda 8:0 0 223.6G 0 disk
├─sda1 8:1 0 100M 0 part
├─sda2 8:2 0 16M 0 part
├─sda3 8:3 0 173G 0 part
├─sda4 8:4 0 498M 0 part
├─sda5 8:5 0 524M 0 part /efi
├─sda6 8:6 0 4G 0 part [SWAP]
└─sda7 8:7 0 45.5G 0 part /
sdb 8:16 0 931.5G 0 disk
├─sdb1 8:17 0 16M 0 part
├─sdb2 8:18 0 631.5G 0 part
└─sdb3 8:19 0 300G 0 part /home
sudo grub-mkconfig -o /boot/grub/grub.cfg
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-linux
Found initrd image: /boot/amd-ucode.img /boot/initramfs-linux.img
Found fallback initrd image(s) in /boot: amd-ucode.img initramfs-linux-fallback.img
Warning: os-prober will be executed to detect other bootable partitions.
Its output will be used to detect bootable binaries on them and create new boot entries.
Adding boot menu entry for UEFI Firmware Settings ...
doneAlthough the warning message says that, I still have the problem.
Last edited by Kurokishin (2022-02-19 16:54:23)
Offline
during Arch installation I kept the w10 EFI partition and the ubuntu one (just mounted on the latter as the wiki told so).
Why do you have multiple EFI partitions?
You should only have one that's shared between all OS's.
Offline
I just have two, the one that comes with w10 and the one that I had for ubuntu. Should I delete the w10 one?
Last edited by Kurokishin (2022-02-15 15:27:47)
Offline
Why is /dev/sda1 mounted under /boot? Does the grub directory actually exist on that partition?
Try mounting /dev/sda1 under /mnt instead so that grub-mkconfig is able to output the configuration file to /boot on /dev/sda7, where it can be found by GRUB.
You should only have one that's shared between all OS's.
Multiple ESPs are fine with GRUB. It would only be a problem for systemd-boot, which needs bootmgfw.efi to be on the same ESP for it to be added to the menu.
Jin, Jîyan, Azadî
Offline
Multiple ESPs are fine with GRUB. It would only be a problem for systemd-boot, which needs bootmgfw.efi to be on the same ESP for it to be added to the menu.
Multiple ESPs aren't covered by the UEFI specification, it's completely dependent on the motherboard manufacturers implementation whether or not such a setup will work without issues.
Offline
Well the OP's motherboard can certainly handle multiple ESPs:
Before installing Arch, I had a dual-boot with w10 and ubuntu, during Arch installation I kept the w10 EFI partition and the ubuntu one
Jin, Jîyan, Azadî
Offline
Why is /dev/sda1 mounted under /boot? Does the grub directory actually exist on that partition?
Try mounting /dev/sda1 under /mnt instead so that grub-mkconfig is able to output the configuration file to /boot on /dev/sda7, where it can be found by GRUB.
Slithery wrote:You should only have one that's shared between all OS's.
Multiple ESPs are fine with GRUB. It would only be a problem for systemd-boot, which needs bootmgfw.efi to be on the same ESP for it to be added to the menu.
That worked, thanks. But do you have any idea about how do I remove the "rescue console" that I talked about? It's like the GRUB that I installed in my ubuntu is still on my pc, and it only appears in the BIOS
Last edited by Kurokishin (2022-02-15 17:25:53)
Offline
You can use efibootmgr(8) to delete the vestigial Ubuntu NVRAM boot entry.
Jin, Jîyan, Azadî
Offline
Thank you for the solutions, it worked flawlessly.
Offline