You are not logged in.
Pages: 1
Hello,
Today I installed arch dualboot beside debian. After installation I went to debian and ran `sudo grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=GRUB` to add arch to GRUB's list. The output was:
Installing for x86_64-efi platform.
Installation finished. No error reported.
And after it, I ran `sudo update-grub` and got:
Generating grub configuration file ...
Found background image: /usr/share/images/desktop-base/desktop-grub.png
Found linux image: /boot/vmlinuz-6.4.0-4-amd64
Found initrd image: /boot/initrd.img-6.4.0-4-amd64
Found linux image: /boot/vmlinuz-6.4.0-3-amd64
Found initrd image: /boot/initrd.img-6.4.0-3-amd64
Warning: os-prober will not be executed to detect other bootable partitions.
Systems on them will not be added to the GRUB boot configuration.
Check GRUB_DISABLE_OS_PROBER documentation entry.
Adding boot menu entry for UEFI Firmware Settings ...
done
But when I rebooted the system arch wasn't in GRUB's list. I returned to debian and ran `sudo os-prober` and got:
/dev/sda3:Arch Linux:Arch:linux
So arch is installed rightly.
Also in /esp/EFI/ there is a `arch/` dir and it contains `grubx64.efi` file. Why the GRUB does not list arch?
Offline
Hello, Mr./Mrs. RezaHoss.
Welcome to Arch Forums!
There are a lot of reasons for your problem.
Go to your arch linux system:
Could you post output of:
fdisk -l
Output of:
cat /etc/fstab
Output of:
sudo cat /boot/grub/grub.cfg
Output of:
mount | grep boot
Output of:
ls /boot
Output of:
cat /etc/default/grub | grep OS
Have a nice time!
Offline
Thanks!
I can't enter to arch because of the aforementioned problem. So I chrooted to arch from my debian and ran these:
[root@reza-debian ~]# fdisk -l
fdisk: cannot open /proc/partitions: No such file or directory
[root@reza-debian ~]# cat /etc/fstab
# /dev/sda3
UUID=bd7dc506-d89d-41e6-ada6-0d3659861f56 / ext4 rw,relatime 0 1
# /dev/sda2
UUID=2de85d45-e273-4244-8c34-893ac83f6261 /home ext4 rw,relatime 0 2
# /dev/sda1
UUID=7e1e7ce6-35c6-4968-9203-20f58c8308dc /boot ext4 rw,relatime 0 2
# /dev/sda4 LABEL=NO_LABEL
UUID=32EB-03CE /boot/efi vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro0 2
[root@reza-debian /]# sudo cat /boot/grub/grub.cfg
cat: /boot/grub/grub.cfg: No such file or directory
[root@reza-debian /]# mount | grep boot
mount: failed to read mtab: No such file or directory
[root@reza-debian /]# ls /boot
efi grub initramfs-linux-fallback.img initramfs-linux.img lost+found vmlinuz-linux
[root@reza-debian /]# cat /etc/default/grub | grep OS
# documentation on GRUB_DISABLE_OS_PROBER, if still want to enable this
#GRUB_DISABLE_OS_PROBER=false
Offline
Also `ls /boot/efi/EFI/arch`:
[root@reza-debian EFI]# ls arch
grubx64.efi
Offline
So, let's check.
[root@reza-debian /]# cat /etc/default/grub | grep OS
# documentation on GRUB_DISABLE_OS_PROBER, if still want to enable this
#GRUB_DISABLE_OS_PROBER=false
It looks like your os-prober is enabled. Sometimes it makes warnings for you.
I recommend to don't disable it, but if you don't like do that, you don't have to do.
You can edit it (With 'vim', 'nvim', 'nano' or whatever you like! I use 'vim'.):
sudo vim /etc/default/grub
Find that line, which is about os-prober.
Remove '#' for make it readable for grub.
Before:
#GRUB_DISABLE_OS_PROBER=false
After:
GRUB_DISABLE_OS_PROBER=false
Okay, it's fine now.
[root@reza-debian /]# sudo cat /boot/grub/grub.cfg
cat: /boot/grub/grub.cfg: No such file or directory
You didn't make any config for your system.
I think this is your problem!
You can make it, easily:
sudo grub-mkconfig -o /boot/grub/grub.cfg
It will update your grub configuration and add it in that. You can use it instead 'update-grub'.
And at the end, ensure you installed your grub after mounting your boot partition. (/dev/sda4)
It's a usual problem. Sometimes users install whatever they want, then mount their partition in that directory!
If there are any other problem, tell us.
Last edited by Paradoxer32 (2023-09-15 13:00:03)
Offline
That's it. Now arch's GRUB is shown in boot, but debian is not there in the GRUB's list!
Offline
D*mn it!
Any way, dual boot isn't a good idea, at all.
Because it isn't as isolate as what we want. If you solve this problem, after that, you'll find a lot of other problems!
Why don't you use Arch Linux in a virtual machine manager or as main distro ?
Offline
I want to use arch as my main distro, but I to have my old debian until I config arch as I want and also install all programs which I need.
Offline
Okay, nice choice.
After choose 'Arch linux' in boot menu, what will happen?
Offline
Pages: 1