hi, I have several operating systems on my PC, Grub Garuda does not recognize Arch Linux
Thank you for your answer
Hi there, welcome to the forum.
Please provide your garuda-inxi, as instructed by the new topic template, as well as any possibly related information. E g.
cat /etc/fstab
sudo fdisk -l
lsblk -f
My best guess would be to make sure that your Arch Linux partition is mounted before running again
sudo update-grub
from Garuda
2 Likes
Can you please provide your
garuda-inxi
as per the forum template
2 Likes
Sorry, I didn't understand what you meant
╰─λ garuda-inxi
System:
Kernel: 6.4.10-zen2-1-zen arch: x86_64 bits: 64 compiler: gcc v: 13.2.1
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=3a5fc761-9574-4cb6-869d-493ef636a42e rw rootflags=subvol=@
quiet quiet rd.udev.log_priority=3 vt.global_cursor_default=0 loglevel=3
ibt=off
Desktop: KDE Plasma v: 5.27.7 tk: Qt v: 5.15.10 wm: kwin_x11 vt: 2
dm: SDDM Distro: Garuda Linux base: Arch Linux
Machine:
Type: Desktop System: ASUS product: N/A v: N/A serial: <superuser required>
Mobo: ASUSTeK model: PRIME H510M-K v: Rev 1.xx
serial: <superuser required> UEFI: American Megatrends v: 2001
date: 02/01/2023
Battery:
Device-1: hidpp_battery_0 model: Logitech Wireless Mouse serial: <filter>
charge: 55% (should be ignored) rechargeable: yes status: discharging
Device-2: hidpp_battery_1 model: Logitech Wireless Keyboard
serial: <filter> charge: 55% (should be ignored) rechargeable: yes
status: discharging
CPU:
Info: model: 11th Gen Intel Core i5-11400 bits: 64 type: MT MCP
arch: Rocket Lake gen: core 11 level: v4 note: check built: 2021+
process: Intel 14nm family: 6 model-id: 0xA7 (167) stepping: 1
microcode: 0x59
Topology: cpus: 1x cores: 6 tpc: 2 threads: 12 smt: enabled cache:
L1: 480 KiB desc: d-6x48 KiB; i-6x32 KiB L2: 3 MiB desc: 6x512 KiB
L3: 12 MiB desc: 1x12 MiB
Speed (MHz): avg: 2150 high: 2600 min/max: 800/4400 scaling:
driver: intel_pstate governor: powersave cores: 1: 800 2: 2600 3: 801
4: 2600 5: 2600 6: 2600 7: 800 8: 2600 9: 2600 10: 2600 11: 2600 12: 2600
bogomips: 62208
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities: <filter>
Graphics:
Device-1: Intel RocketLake-S GT1 [UHD Graphics 730] vendor: ASUSTeK
driver: i915 v: kernel arch: Gen-12.1 process: Intel 10nm built: 2020-21
ports: active: HDMI-A-1 empty: DP-1 bus-ID: 00:02.0 chip-ID: 8086:4c8b
class-ID: 0300
Display: x11 server: X.Org v: 21.1.8 with: Xwayland v: 23.1.2
compositor: kwin_x11 driver: X: loaded: modesetting
alternate: fbdev,intel,vesa dri: iris gpu: i915 display-ID: :0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22")
s-diag: 582mm (22.93")
Monitor-1: HDMI-A-1 mapped: HDMI-1 model: Samsung LF24T35 serial: <filter>
built: 2020 res: 1920x1080 dpi: 92 gamma: 1.2 size: 528x297mm (20.79x11.69")
diag: 606mm (23.9") ratio: 16:9 modes: max: 1920x1080 min: 720x400
API: OpenGL v: 4.6 Mesa 23.1.5 renderer: Mesa Intel Graphics (RKL GT1)
direct-render: Yes
Audio:
Device-1: Intel Tiger Lake-H HD Audio vendor: ASUSTeK driver: snd_hda_intel
v: kernel alternate: snd_sof_pci_intel_tgl bus-ID: 00:1f.3
chip-ID: 8086:43c8 class-ID: 0403
API: ALSA v: k6.4.10-zen2-1-zen status: kernel-api tools: N/A
Server-1: PipeWire v: 0.3.77 status: active with: 1: pipewire-pulse
status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
4: pw-jack type: plugin tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: Intel Ethernet I219-V vendor: ASUSTeK driver: e1000e v: kernel
port: N/A bus-ID: 00:1f.6 chip-ID: 8086:15fa class-ID: 0200
IF: eno1 state: down mac: <filter>
Device-2: Realtek RTL8192EU 802.11b/g/n WLAN Adapter driver: rtl8192eu
type: USB rev: 2.1 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-6:3
chip-ID: 0bda:818b class-ID: 0000 serial: <filter>
IF: wlp0s20f0u6 state: up mac: <filter>
Bluetooth:
Device-1: Cambridge Silicon Radio Bluetooth Dongle (HCI mode) driver: btusb
v: 0.8 type: USB rev: 2.0 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-7:4
chip-ID: 0a12:0001 class-ID: e001
Report: bt-adapter ID: hci0 rfk-id: 1 state: up address: <filter>
Drives:
Local Storage: total: 2.65 TiB used: 45 GiB (1.7%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Lexar model: 256GB SSD
size: 238.47 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s
lanes: 4 tech: SSD serial: <filter> fw-rev: V1.19.B3 temp: 38.9 C
scheme: GPT
ID-2: /dev/nvme1n1 maj-min: 259:1 vendor: Lexar model: SSD NM620 512GB
size: 476.94 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s
lanes: 4 tech: SSD serial: <filter> fw-rev: V1.27 temp: 34.9 C scheme: GPT
ID-3: /dev/sda maj-min: 8:0 vendor: Samsung model: ST1000LM024 HN-M101MBB
size: 931.51 GiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
tech: HDD rpm: 5400 serial: <filter> fw-rev: 0001 scheme: GPT
ID-4: /dev/sdb maj-min: 8:16 vendor: Maxtor model: STM3320820AS
size: 298.09 GiB block-size: physical: 512 B logical: 512 B speed: 3.0 Gb/s
tech: N/A serial: <filter> fw-rev: E scheme: GPT
ID-5: /dev/sdc maj-min: 8:32 vendor: Seagate model: ST500LT012-1DG142
size: 465.76 GiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
tech: HDD rpm: 5400 serial: <filter> fw-rev: SDM1 scheme: GPT
ID-6: /dev/sdd maj-min: 8:48 vendor: Maxtor model: STM3320820AS
size: 298.09 GiB block-size: physical: 512 B logical: 512 B speed: 3.0 Gb/s
tech: N/A serial: <filter> fw-rev: E scheme: GPT
Partition:
ID-1: / raw-size: 457.46 GiB size: 457.46 GiB (100.00%)
used: 44.99 GiB (9.8%) fs: btrfs dev: /dev/sdc2 maj-min: 8:34
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 296 KiB (0.1%) fs: vfat dev: /dev/sdc1 maj-min: 8:33
ID-3: /home raw-size: 457.46 GiB size: 457.46 GiB (100.00%)
used: 44.99 GiB (9.8%) fs: btrfs dev: /dev/sdc2 maj-min: 8:34
ID-4: /var/log raw-size: 457.46 GiB size: 457.46 GiB (100.00%)
used: 44.99 GiB (9.8%) fs: btrfs dev: /dev/sdc2 maj-min: 8:34
ID-5: /var/tmp raw-size: 457.46 GiB size: 457.46 GiB (100.00%)
used: 44.99 GiB (9.8%) fs: btrfs dev: /dev/sdc2 maj-min: 8:34
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: zram size: 31.12 GiB used: 0 KiB (0.0%) priority: 100
dev: /dev/zram0
ID-2: swap-2 type: partition size: 8 GiB used: 0 KiB (0.0%) priority: -2
dev: /dev/sdc3 maj-min: 8:35
Sensors:
System Temperatures: cpu: 40.0 C mobo: N/A
Fan Speeds (RPM): N/A
Info:
Processes: 294 Uptime: 5m wakeups: 17 Memory: total: 32 GiB note: est.
available: 31.12 GiB used: 4.16 GiB (13.4%) Init: systemd v: 254
default: graphical tool: systemctl Compilers: gcc: 13.2.1 clang: 15.0.7
Packages: pm: pacman pkgs: 1301 libs: 342 tools: octopi,paru Shell: fish
v: 3.6.1 default: Bash v: 5.1.16 running-in: konsole inxi: 3.3.28
Garuda (2.6.16-1):
System install date: 2023-08-12
Last full system update: 2023-08-13
Is partially upgraded: No
Relevant software: snapper NetworkManager dracut
Windows dual boot: Probably (Run as root to verify)
Was this done?
I believed that Arch was installed, but it needs to be mounted in Garuda before update-grub.
1 Like
Yes, I updated Grub several times after installing Arch Linux
File: /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a device; this may
# be used with UUID= as a more robust way to name devices that works even if
# disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
UUID=DBC7-F1C9 /boot/efi vfat defaults,noatime 0 2
UUID=3a5fc761-9574-4cb6-869d-493ef636a42e / btrfs subvol=/@,defaults,noatime,compress=zstd 0 0
UUID=3a5fc761-9574-4cb6-869d-493ef636a42e /home btrfs subvol=/@home,defaults,noatime,compress=zstd
0 0
UUID=3a5fc761-9574-4cb6-869d-493ef636a42e /root btrfs subvol=/@root,defaults,noatime,compress=zstd
0 0
UUID=3a5fc761-9574-4cb6-869d-493ef636a42e /srv btrfs subvol=/@srv,defaults,noatime,compress=zstd 0
0
UUID=3a5fc761-9574-4cb6-869d-493ef636a42e /var/cache btrfs subvol=/@cache,defaults,noatime,compress=zstd
0 0
UUID=3a5fc761-9574-4cb6-869d-493ef636a42e /var/log btrfs subvol=/@log,defaults,noatime,compress=zstd 0
0
UUID=3a5fc761-9574-4cb6-869d-493ef636a42e /var/tmp btrfs subvol=/@tmp,defaults,noatime,compress=zstd 0
0
╰─λ sudo fdisk -l
Disk /dev/sda: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: ST1000LM024 HN-M
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: D67F8949-6747-144D-B2F5-A63E2C4BF564
Device Start End Sectors Size Type
/dev/sda1 4096 618495 614400 300M EFI System
/dev/sda2 618496 904943615 904325120 431.2G Linux filesystem
/dev/sda3 904943616 905822207 878592 429M EFI System
/dev/sda4 905822208 1953523711 1047701504 499.6G Linux filesystem
Disk /dev/sdb: 298.09 GiB, 320071851520 bytes, 625140335 sectors
Disk model: MAXTOR STM332082
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 36B7D694-1BEB-4447-BB4E-E2D173160EB7
Device Start End Sectors Size Type
/dev/sdb1 2048 625139711 625137664 298.1G Microsoft basic data
Disk /dev/sdc: 465.76 GiB, 500107862016 bytes, 976773168 sectors
Disk model: ST500LT012-1DG14
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: EB4B4C54-EE8B-B94B-8A3D-9B056519C19A
Device Start End Sectors Size Type
/dev/sdc1 6144 620543 614400 300M BIOS boot
/dev/sdc2 620544 959993855 959373312 457.5G Linux filesystem
/dev/sdc3 959993856 976771071 16777216 8G Linux swap
Disk /dev/sdd: 298.09 GiB, 320071851520 bytes, 625140335 sectors
Disk model: MAXTOR STM332082
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: B05299B4-6D3C-4E40-9078-3AD6E7EA9F22
Device Start End Sectors Size Type
/dev/sdd1 2048 625139711 625137664 298.1G Microsoft basic data
Disk /dev/nvme0n1: 238.47 GiB, 256060514304 bytes, 500118192 sectors
Disk model: Lexar 256GB SSD
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: D5868C12-C232-4338-9D68-03F76526DFC8
Device Start End Sectors Size Type
/dev/nvme0n1p1 2048 206847 204800 100M EFI System
/dev/nvme0n1p2 206848 239615 32768 16M Microsoft reserved
/dev/nvme0n1p3 239616 498749439 498509824 237.7G Microsoft basic data
/dev/nvme0n1p4 498749440 500115455 1366016 667M Windows recovery environment
Disk /dev/nvme1n1: 476.94 GiB, 512110190592 bytes, 1000215216 sectors
Disk model: Lexar SSD NM620 512GB
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: CF5ACDE2-51C9-40BC-911D-78717BAD6B48
Device Start End Sectors Size Type
/dev/nvme1n1p1 2048 1050623 1048576 512M EFI System
/dev/nvme1n1p2 1050624 1000214527 999163904 476.4G Linux filesystem
Disk /dev/zram0: 31.12 GiB, 33410777088 bytes, 8156928 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
╰─λ lsblk -f
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
sda
├─sda1 vfat FAT32 NO_LABEL 5136-968F
├─sda2 btrfs 092bd525-d2a7-4cc5-a19d-a41b90862492
├─sda3 vfat FAT32 CD47-4D62
└─sda4 btrfs 9aba5fd1-8dba-486d-aca2-a73525b8a71c
sdb
└─sdb1 ntfs Program 7DC2DAB15C434DB7
sdc
├─sdc1 vfat FAT32 DBC7-F1C9 299.1M 0% /boot/efi
├─sdc2 btrfs 3a5fc761-9574-4cb6-869d-493ef636a42e 412.2G 10% /var/log
│ /var/tmp
│ /var/cache
│ /srv
│ /root
│ /home
│ /
└─sdc3 swap 1 701e9457-35bd-4d7a-a0c9-e0ccde631855 [SWAP]
sdd
└─sdd1 ntfs Data1 2793FC7B17A174FF
zram0 [SWAP]
nvme0n1
├─nvme0n1p1 vfat FAT32 3E80-676A
├─nvme0n1p2
├─nvme0n1p3 ntfs Windows11 58A89817A897F1AC
└─nvme0n1p4 ntfs 5E70FCCB70FCAAC3
nvme1n1
├─nvme1n1p1 vfat FAT32 7D0E-10A7
└─nvme1n1p2 btrfs 4a21c8c9-591a-43d9-baf5-860a62eef203
╰─λ sudo update-grub
Generating grub configuration file ...
Found theme: /usr/share/grub/themes/garuda-dr460nized/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
Found linux image: /boot/vmlinuz-linux-nitrous
Found initrd image: /boot/intel-ucode.img /boot/initramfs-linux-nitrous.img
Found fallback initrd image(s) in /boot: intel-ucode.img initramfs-linux-nitrous-fallback.img
Found linux image: /boot/vmlinuz-linux
Found initrd image: /boot/intel-ucode.img /boot/initramfs-linux.img
Found fallback initrd image(s) in /boot: intel-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.
Found Windows Boot Manager on /dev/nvme0n1p1@/efi/Microsoft/Boot/bootmgfw.efi
Found Kali GNU/Linux Rolling on /dev/nvme1n1p2
Found Parrot OS 5.3 (Electro Ara) on /dev/sda2
Adding boot menu entry for UEFI Firmware Settings ...
Detecting snapshots ...
There is nothing in the efi folder in Arch Linux
I have installed it several times and every time I restart it, it gets deleted
# mount /dev/sda3 /boot/efi
# sudo grub-install /dev/sda3
This could be the problem?
You don't have to mount Arch's /boot/efi but its root partition.
And then
sudo update-grub
No need to reinstall grub and no need to chroot or similar (I see the #). Just use a normal Garuda terminal.
1 Like
It cannot be done with a normal user, it must be the root user
╭─lion@garuda in ~ took 33ms
╰─λ mount /dev/sda3 /boot/efi
mount: /boot/efi: must be superuser to use mount.
dmesg(1) may have more information after failed mount system call.
Assuming that /dev/sda4 is your Arch root partition, try:
sudo mount /dev/sda4 /mnt
sudo update-grub
1 Like
It didn't work
╭─lion@garuda in ~
╰─λ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
sda 8:0 0 931.5G 0 disk
├─sda1 8:1 0 300M 0 part
├─sda2 8:2 0 431.2G 0 part
├─sda3 8:3 0 429M 0 part
└─sda4 8:4 0 499.6G 0 part
sdb 8:16 0 298.1G 0 disk
└─sdb1 8:17 0 298.1G 0 part
sdc 8:32 0 465.8G 0 disk
├─sdc1 8:33 0 300M 0 part /boot/efi
├─sdc2 8:34 0 457.5G 0 part /var/log
└─sdc3 8:35 0 8G 0 part [SWAP]
sdd 8:48 0 298.1G 0 disk
└─sdd1 8:49 0 298.1G 0 part
zram0 254:0 0 31.1G 0 disk [SWAP]
nvme1n1 259:0 0 238.5G 0 disk
├─nvme1n1p1 259:1 0 100M 0 part
├─nvme1n1p2 259:2 0 16M 0 part
├─nvme1n1p3 259:3 0 237.7G 0 part
└─nvme1n1p4 259:4 0 667M 0 part
nvme0n1 259:5 0 476.9G 0 disk
├─nvme0n1p1 259:6 0 512M 0 part
└─nvme0n1p2 259:7 0 476.4G 0 part
Arch linux root partition /dev/sda4
╭─lion@garuda in ~ took 30ms
╰─λ sudo mount /dev/sda4 /mnt
╰─λ sudo update-grub
Generating grub configuration file ...
Found theme: /usr/share/grub/themes/garuda-dr460nized/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
Found linux image: /boot/vmlinuz-linux-nitrous
Found initrd image: /boot/intel-ucode.img /boot/initramfs-linux-nitrous.img
Found fallback initrd image(s) in /boot: intel-ucode.img initramfs-linux-nitrous-fallback.img
Found linux image: /boot/vmlinuz-linux
Found initrd image: /boot/intel-ucode.img /boot/initramfs-linux.img
Found fallback initrd image(s) in /boot: intel-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.
Found Kali GNU/Linux Rolling on /dev/nvme0n1p2
Found Windows Boot Manager on /dev/nvme1n1p1@/efi/Microsoft/Boot/bootmgfw.efi
Found Parrot OS 5.3 (Electro Ara) on /dev/sda2
Adding boot menu entry for UEFI Firmware Settings ...
Detecting snapshots ...
I install it and it is installed
# mount /dev/sda3 /boot/efi
# sudo grub-install /dev/sda3
Installing for x86_64-efi platform.
Installation finished. No error reported.
# ls /boot/efi/EFI
arch arch_grub garuda
It will be deleted after restarting
# ls /boot/efi/EFI
boot Garuda
In the first box you reinstalled grub in the Arch ESP partition, but you will be using the Garuda GRUB not the Arch one. The os-prober doesn't care of the other grubs, it just looks for bootable entries.
The difference after reboot could be due to the fact that in the second box you might be searching in the Garuda ESP, not the Arch one as before.
Anyway I'm sorry, I dual boot Garuda and Arch on a laptop with no problems since years, but I don't have it with me in this period to check the details.
I don't recall I did anything special.
Maybe try installing in Arch lsb-release but I doubt it will help:
https://wiki.archlinux.org/title/GRUB#Arch_not_found_from_other_OS
1 Like
While os-prober is designed to detect other operating systems on different partitions, typically there will only be one EFI partition on a single disk. I’m not sure os-prober is designed to handle multiple EFI partitions on the same disk–from what I understand, it expects to find bootloader information in a common EFI partition.
Having two EFI partitions on the same disk can cause other issues related to bootloaders and OS installation, so it would not surprise me to learn it causes issues with os-prober as well. Actually, having two EFI partitions on the same disk can cause major issues with Windows–for example, Windows will refuse to install on a disk that already has an EFI partition. You may be fine to keep using it since the installation is complete, but I would be nervous to update that bootloader.
My advice is to boot to your Arch installation, unmount /dev/sda3, mount /dev/sda1 at /boot/efi (assuming that is where you have mounted the EFI partition in Arch), reinstall the Grub bootloader, regenerate the Grub configuration file, amend /etc/fstab with 5136-968F as the UUID for the EFI partition, reboot to confirm that the updated configuration works as expected, and then delete the /dev/sda3 partition and delete the old EFI boot variable with efibootmgr or from the UEFI setup utility.
Then, re-scan with os-prober from Garuda.
4 Likes
Thank you for your answer
You should know that, you l33t h4x0r!
1 Like
The problem was solved؛
I had installed Arch Linux and Parrot in one disk, with two partitions efi
I deleted one of the efi partitions, And I installed two grubs on one efi partition
╰─λ sudo update-grub
Generating grub configuration file ...
Found theme: /usr/share/grub/themes/garuda-dr460nized/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
Found linux image: /boot/vmlinuz-linux-nitrous
Found initrd image: /boot/intel-ucode.img /boot/initramfs-linux-nitrous.img
Found fallback initrd image(s) in /boot: intel-ucode.img initramfs-linux-nitrous-fallback.img
Found linux image: /boot/vmlinuz-linux
Found initrd image: /boot/intel-ucode.img /boot/initramfs-linux.img
Found fallback initrd image(s) in /boot: intel-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.
Found Windows Boot Manager on /dev/nvme0n1p1@/efi/Microsoft/Boot/bootmgfw.efi
Found Kali GNU/Linux Rolling on /dev/nvme1n1p2
Found Parrot OS 5.3 (Electro Ara) on /dev/sda2
Found Arch Linux on /dev/sda3
Adding boot menu entry for UEFI Firmware Settings ...
Detecting snapshots ...
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.