Problems with chroot

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:
[email protected] ~]$ 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
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.

a thousand thanks

Check if all drives are mounted (/dev/sda2-4) in LXQt file browser.
Then again,

sudo update-grub

OK thank you.
[[email protected] ~]$ 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

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 :wink:, I think the following information might be beneficial anyway:


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:

  Kernel: 5.17.9-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 12.1.0
    parameters: BOOT_IMAGE=/vmlinuz-linux-zen
    root=UUID=85767c9d-1549-476d-ad89-f880cf55488b rw [email protected]
    quiet quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0
  Desktop: LXQt v: 1.1.0 tk: Qt v: 5.15.4 info: cairo-dock, lxqt-panel
    wm: kwin_x11 vt: 1 dm: SDDM Distro: Garuda Linux base: Arch Linux
  Type: Laptop System: Dell product: Latitude E5440 v: 00
    serial: <superuser required> Chassis: type: 9 serial: <superuser required>
  Mobo: Dell model: 0XFRKC v: A01 serial: <superuser required> UEFI: Dell
    v: A23 date: 10/08/2018
  ID-1: BAT0 charge: 33.9 Wh (100.0%) condition: 33.9/66.6 Wh (50.9%)
    volts: 12.9 min: 11.1 model: SMP DELL WGCW633 type: Li-ion serial: <filter>
    status: full
  Info: model: Intel Core i3-4030U bits: 64 type: MT MCP arch: Haswell
    family: 6 model-id: 0x45 (69) stepping: 1 microcode: 0x24
  Topology: cpus: 1x cores: 2 tpc: 2 threads: 4 smt: enabled cache:
    L1: 128 KiB desc: d-2x32 KiB; i-2x32 KiB L2: 512 KiB desc: 2x256 KiB
    L3: 3 MiB desc: 1x3 MiB
  Speed (MHz): avg: 1896 high: 1897 min/max: 800/1900 scaling:
    driver: intel_cpufreq governor: schedutil cores: 1: 1896 2: 1896 3: 1896
    4: 1897 bogomips: 15165
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Type: itlb_multihit status: KVM: VMX disabled
  Type: l1tf
    mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable
  Type: mds status: Vulnerable: Clear CPU buffers attempted, no microcode;
    SMT vulnerable
  Type: meltdown mitigation: PTI
  Type: spec_store_bypass
    mitigation: Speculative Store Bypass disabled via prctl
  Type: spectre_v1
    mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2 mitigation: Retpolines, IBPB: conditional, IBRS_FW,
    STIBP: conditional, RSB filling
  Type: srbds status: Vulnerable: No microcode
  Type: tsx_async_abort status: Not affected
  Device-1: Intel Haswell-ULT Integrated Graphics vendor: Dell driver: i915
    v: kernel ports: active: DP-2,eDP-1
    empty: DP-1, DP-3, DP-4, HDMI-A-1, HDMI-A-2 bus-ID: 00:02.0
    chip-ID: 8086:0a16 class-ID: 0300
  Device-2: Microdia Laptop_Integrated_Webcam_HD type: USB driver: uvcvideo
    bus-ID: 1-1.6:3 chip-ID: 0c45:649d class-ID: 0e02
  Display: x11 server: X.Org v: 21.1.3 with: Xwayland v: 22.1.1
    compositor: kwin_x11 driver: X: loaded: modesetting
    alternate: fbdev,intel,vesa gpu: i915 display-ID: :0 screens: 1
  Screen-1: 0 s-res: 3286x1080 s-dpi: 96 s-size: 869x285mm (34.21x11.22")
    s-diag: 915mm (36.01")
  Monitor-1: DP-2 mapped: DP-1-1 pos: primary,top-left model: Dell S2740L
    serial: <filter> built: 2013 res: 1920x1080 hz: 60 dpi: 82 gamma: 1.2
    size: 598x336mm (23.54x13.23") diag: 686mm (27") ratio: 16:9 modes:
    max: 1920x1080 min: 720x400
  Monitor-2: eDP-1 pos: bottom-r model: Samsung 0x5441 built: 2012
    res: 1366x768 hz: 60 dpi: 112 gamma: 1.2 size: 309x174mm (12.17x6.85")
    diag: 355mm (14") ratio: 16:9 modes: 1366x768
  OpenGL: renderer: Mesa Intel HD Graphics 4400 (HSW GT2)
    v: 4.6 Mesa 22.0.4 compat-v: 3.1 direct render: Yes
  Device-1: Intel Haswell-ULT HD Audio vendor: Dell driver: snd_hda_intel
    v: kernel bus-ID: 00:03.0 chip-ID: 8086:0a0c class-ID: 0403
  Device-2: Intel 8 Series HD Audio vendor: Dell driver: snd_hda_intel
    v: kernel bus-ID: 00:1b.0 chip-ID: 8086:9c20 class-ID: 0403
  Sound Server-1: ALSA v: k5.17.9-zen1-1-zen running: yes
  Sound Server-2: PulseAudio v: 15.0 running: no
  Sound Server-3: PipeWire v: 0.3.51 running: yes
  Device-1: Intel Ethernet I218-LM vendor: Dell driver: e1000e v: kernel
    port: f080 bus-ID: 00:19.0 chip-ID: 8086:155a class-ID: 0200
  IF: eno1 state: down mac: <filter>
  Device-2: Qualcomm Atheros AR9485 Wireless Network Adapter vendor: Dell
    driver: ath9k v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1
    bus-ID: 02:00.0 chip-ID: 168c:0032 class-ID: 0280
  IF: wlp2s0 state: up mac: <filter>
  Hardware-1: Intel 82801 Mobile SATA Controller [RAID mode] driver: ahci
    v: 3.0 port: f060 bus-ID: 00:1f.2 chip-ID: 8086:282a rev: N/A
    class-ID: 0104
  Local Storage: total: 447.13 GiB used: 15.16 GiB (3.4%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: Kingston model: SA400S37480G
    size: 447.13 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
    type: SSD serial: <filter> rev: B1D1 scheme: GPT
  ID-1: / raw-size: 166.97 GiB size: 166.97 GiB (100.00%)
    used: 15.16 GiB (9.1%) fs: btrfs dev: /dev/sda5 maj-min: 8:5
  ID-2: /home raw-size: 166.97 GiB size: 166.97 GiB (100.00%)
    used: 15.16 GiB (9.1%) fs: btrfs dev: /dev/sda5 maj-min: 8:5
  ID-3: /var/log raw-size: 166.97 GiB size: 166.97 GiB (100.00%)
    used: 15.16 GiB (9.1%) fs: btrfs dev: /dev/sda5 maj-min: 8:5
  ID-4: /var/tmp raw-size: 166.97 GiB size: 166.97 GiB (100.00%)
    used: 15.16 GiB (9.1%) fs: btrfs dev: /dev/sda5 maj-min: 8:5
  Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: zram size: 15.53 GiB used: 0 KiB (0.0%) priority: 100
    dev: /dev/zram0
  ID-2: swap-2 type: partition size: 549 MiB used: 0 KiB (0.0%)
    priority: -2 dev: /dev/sda7 maj-min: 8:7
  System Temperatures: cpu: 46.0 C mobo: 37.0 C sodimm: SODIMM C
  Fan Speeds (RPM): cpu: 3024
  Processes: 214 Uptime: 10m wakeups: 1 Memory: 15.53 GiB
  used: 2.86 GiB (18.4%) Init: systemd v: 251 tool: systemctl Compilers:
  gcc: 12.1.0 clang: 13.0.1 Packages: pacman: 1534 lib: 374 Shell: Bash
  v: 5.1.16 running-in: kitty inxi: 3.3.16
Garuda (2.6.3-2):
  System install date:     2022-05-14
  Last full system update: 2022-05-23
  Is partially upgraded:   No
  Relevant software:       NetworkManager
  Windows dual boot:       No/Undetected
  Snapshots:               Snapper
  Failed units:            bluetooth-autoconnect.service 
[[email protected] ~]$ efibootmgr
BootCurrent: 0000
Timeout: 0 seconds
BootOrder: 0001,0002,0003,0004,0005,0000,0006
Boot0000* garuda
Boot0001* Diskette Drive
Boot0002* Internal HDD
Boot0003* USB Storage
Boot0004* CD/DVD/CD-RW Drive
Boot0005* Onboard NIC
Boot0006* UEFI: Hard Drive 

a thousand thanks

[malik @ DELL ~] $ sudo grub-install --target = x86_64-efi --efi-directory = / boot / efi --bootloader-id = garuda-first
[sudo] malik password:
Installation for the x86_64-efi platform.
grub-install: error: / boot / efi does not appear to be an EFI partition.

i don't understand the EFI partitions there i have.

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



You need to remove all these spaces from the path.

sudo grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=garuda-first

[[email protected] ~]$ 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

does not appear to be an EFI partition.
THats the problem.

I think this is the crux of the issue. Some of your installations appear to have been done in legacy mode.

I do not think your Windows is using the EFI partition either, because it looks like you only have 2.74 MiB on /boot/efi.

Can you try to restore grub with the legacy method instead of EFI and post the output to the thread?


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.

And correct ???

Too many spaces.

[email protected] malik]# sudo garuda-chroot /mnt/@
sudo: garuda-chroot: command not found

Or use live ISO and in Welcome/Assistant the chroot icon.

I'm working on it but the problem is the command:
garuda chroot who does not find it

 ╭─[email protected] in ~ took 1m9s
[🧱] × su
[[email protected] sgs]# garuda-chroot -a
==> Detected systems:
 --> 0) Arch_Linux
 --> 1) Garuda_Linux
==> Select system to mount [0-1] : 

this is the result I get when I give the command:

     squash 4.0 0 100% / var / lib / snapd / snap / core18 / 2409
     squash 4.0 0 100% / var / lib / snapd / snap / snapd / 15534
     squash 4.0 0 100% / var / lib / snapd / snap / gnome-3-28-1804 / 161
     squash 4.0 0 100% / var / lib / snapd / snap / translatium / 141
     squash 4.0 0 100% / var / lib / snapd / snap / gtk-common-themes / 1519
     squash 4.0 0 100% / var / lib / snapd / snap / bare / 5
│ ntfs Recovery
│ B0243BA0243B690C
│ vfat FAT32 5E63-73A4
│ ntfs 06F665DCF665CC8D
│ btrfs 85767c9d-1549-476d-ad89-f880cf55488b 151G 9% / var / tmp
│ / var / log
│ / srv
│ / var / cache
│ / home
│ / root
│ /
│ btrfs 59b2d140-9617-4869-bc03-09f061ee6bce 157.4G 14% / mnt / broken
│ / mnt
     swap 1 2f465ffe-f823-4f14-bcb9-cec74faa773a [SWAP]

Please format your terminal output and post also the command too!

[root @ DELL owner] # garuda-chroot -a
bash: garuda-chroot: command not find

Use live ISO

[email protected] 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/@