Hi everyone
Sorry in advance but this is the first time I create a topic and I don’t know if I’m doing it right.
I will try to best describe my problem.
Or a problem on my grub, meaning I don’t see my distributions anymore.
or rather I only see one of garuda lxqte.
but or also garuda kde and win10
and the latter I no longer see.
I do the grub update:
sudo update-grub, and it gives me this result:
malik@DELL ~]$ sudo update-grub
Generating grub configuration file …
Found theme: /usr/share/grub/themes/garuda/theme.txt
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 …
Detecting snapshots …
Kernels not found.
If you think an error has occurred , please file a bug report at " GitHub - Antynea/grub-btrfs: Include btrfs snapshots at boot options. (Grub menu) "
Unmount /tmp/grub-btrfs.c5iNN7XDEZ … Success
done
but it does not see the other partitions.
I made the efi part as a procedure.
and when it starts there is only garuda boot but no os.
in gparted you can see very well my partitions, including the efi partition.
but it is not resolved.
thank you very much and I hope you understand what I wrote you.
OK thank you.
[malik@DELL ~]$ sudo update-grub
[sudo] password di malik:
Generating grub configuration file ...
Found theme: /usr/share/grub/themes/garuda/theme.txt
Found linux image: /boot/vmlinuz-linux-zen
Found initrd image: /boot/intel-ucode.img /boot/initramfs-linux-zen.img
Found fallback initrd image(s) in /boot: intel-ucode.img initramfs-linux-zen-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 ...
Detecting snapshots ...
Found snapshot: 2022-05-23 16:20:06 | @/.snapshots/108/snapshot | post | snapd |
Found snapshot: 2022-05-23 16:20:02 | @/.snapshots/107/snapshot | pre | /usr/bin/pamac-daemon |
Found snapshot: 2022-05-23 16:17:43 | @/.snapshots/106/snapshot | post | appstream appstream-qt beautyline blackarch-mirrorlist device-mapper f2f |
Found snapshot: 2022-05-23 16:17:33 | @/.snapshots/105/snapshot | pre | /usr/bin/pamac-daemon |
Found snapshot: 2022-05-22 20:46:18 | @/.snapshots/104/snapshot | post | firedragon |
Found snapshot: 2022-05-22 20:46:14 | @/.snapshots/103/snapshot | pre | pacman -Syyu |
Found snapshot: 2022-05-22 19:01:06 | @/.snapshots/102/snapshot | post | arch-repro-status gmp |
Found snapshot: 2022-05-22 19:01:04 | @/.snapshots/101/snapshot | pre | /usr/bin/pamac-daemon |
Found snapshot: 2022-05-22 18:22:33 | @/.snapshots/100/snapshot | post | network-manager-sstp |
Found snapshot: 2022-05-22 18:22:31 | @/.snapshots/99/snapshot | pre | pacman --sync -y -u -- |
Found snapshot: 2022-05-22 18:19:27 | @/.snapshots/98/snapshot | post | paru paru-bin |
Found snapshot: 2022-05-22 18:19:24 | @/.snapshots/97/snapshot | pre | /usr/bin/pacman -U /home/malik/paru-bin/paru-bin-1.10.0-1-x86_64.pkg.tar |
Found snapshot: 2022-05-22 16:56:13 | @/.snapshots/96/snapshot | post | autoconf automake binutils bison fakeroot file findutils flex gawk gcc g |
Found snapshot: 2022-05-22 16:56:05 | @/.snapshots/95/snapshot | pre | pacman -S base-devel wget sudo |
Found 14 snapshot(s)
Unmount /tmp/grub-btrfs.f3jG3DPmoo .. Success
Found memtest86+ image: /boot/memtest86+/memtest.bin
done
nothing always stays the same as before it does not find the other distributions
Provided that this use-case is a bit peculiar for me, so I hope some else will have better ideas , I think the following information might be beneficial anyway:
garuda-inxi
efibootmgr
When this issue started (did the triple boot work until a certain point)?
This is also useful to understand how the dual boot of the two garuda systems was handled.
If you do not take specific steps, you risk the second installation to overwrite the grub of the first one. See e.g. here:
The strange thing here is that /boot/efi is missing.
Maybe you installed LXQt in Legacy mode and the grub went somewhere else?
You could try mounting /boot/efi manually (
sudo mount /dev/sda3 /boot/efi
) or better via /etc/fstab and try again.
Careful, in your post above there were unnecessary spaces, / boot / efi instead of /boot/efi
[malik@DELL ~]$ sudo grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=garuda-first
Installazione per la piattaforma x86_64-efi.
grub-install: errore: /boot/efi non sembra essere una partizione EFI.
the spaces are right there are not but it gives me the error
ok let's see if I understand.
Yes, you may have messed with lagacy and EFI.
At this point, if I have to redo the grub, do I have to install it on the sda6 partition?
If I think I understand?
sudo mkdir / mnt
sudo mount / dev / sda6 / mnt
sudo garuda-chroot / mnt / @
%%%%%%%%%%%%%%%
sudo grub-install / dev / sda6.
╭─sgs@i3 in ~ took 1m9s
[🧱] × su
Passwort:
[root@i3 sgs]# garuda-chroot -a
==> Detected systems:
--> 0) Arch_Linux
--> 1) Garuda_Linux
==> Select system to mount [0-1] :
root@garuda-lxqt garuda]# sudo garuda-chroot /mnt/@
mount: /mnt/@/proc: mount point does not exist.
dmesg(1) may have more information after failed mount system call.
==> ERROR: failed to setup API filesystems in chroot /mnt/@
, I think the following information might be beneficial anyway:
