By the way, if you didn't install Grub (the actual package) in Arch when you did your pacstrap you will need to install it from the chroot.
pacman -S grub
1 Like
╭─garuda@garuda in ~ as 🧙 took 32ms
╰─λ sudo mount /dev/nvme0n1p2 /mnt
╭─garuda@garuda in ~ as 🧙 took 48ms
╰─λ sudo garuda-chroot /mnt/@
==> ERROR: Can't create chroot on non-directory /mnt/@
╭─garuda@garuda in ~ as 🧙 took 137ms
[⚡] × lsblk -f
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
loop0 squash 4.0 0 100% /run/miso/sfs/livefs
loop1 squash 4.0 0 100% /run/miso/sfs/mhwdfs
loop2 squash 4.0 0 100% /run/miso/sfs/desktopfs
loop3 squash 4.0 0 100% /run/miso/sfs/rootfs
sda iso966 Jolie GARUDA_DR460NIZED_RAPTOR
2023-05-01-21-27-23-00
├─sda1 iso966 Jolie GARUDA_DR460NIZED_RAPTOR
│ 2023-05-01-21-27-23-00 0 100% /run/miso/bootmnt
└─sda2 vfat FAT12 MISO_EFI CC34-06DF
sdb
sr0 iso966 Jolie U3 System 2008-05-06-12-26-42-
zram0 [SWAP]
nvme0n1
├─nvme0n1p1
│ vfat FAT32 17FA-0561
├─nvme0n1p2
│ ext4 1.0 9063bac4-c6de-409f-a18f-2747c727d875 25.4G 42% /mnt
└─nvme0n1p3
btrfs 7712be21-0b37-41fb-a77a-c53eb6067366
You cannot apply the Garuda procedure and chroot tool to Arch, because it is ext4 base not btrfs.
You should use and Arch live USB and the arch-chroot.
https://wiki.archlinux.org/title/Chroot
Then apply the GRUB installation procedure described above.
2 Likes
You probably just need to leave off the @ because you don’t have subvolumes set up in Arch.
2 Likes
It was the first thread read o' the day.
And the right side of the bed was occupied by my wife. a fearsome creature whose rest I dare not disturb.
3 Likes
Good! One less problem child.
I went by this in the Post #4 you made, since my eyes were glazed from the verbiage that followed. 
I’ll take a look at all that followed, since I’ve multi booted between Arch + Garuda and Arch + Manjaro and Arch + Fedora with no ill effects prior to figuring out that plain ol’ Arch is good enough for me, considering my conservative computing practices, i.e. I try to limit stuff history has shown me is a useless waste of time, such as installing and configuring operating systems when I could be watching porn. And writing run-on sentences. 
Nice!
╭─garuda@garuda in ~ as 🧙 took 35s
[🧱] × sudo garuda-chroot /mnt
sh-5.1# mount /dev/nvme0n1p1 /boot/efi
sh-5.1# lsblk -f
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
loop0
loop1
loop2
loop3
sda
|-sda1
`-sda2
sdb
sr0
zram0 [SWAP]
nvme0n1
|-nvme0n1p1 434.3M 15% /boot/efi
|-nvme0n1p2 25.4G 42% /
`-nvme0n1p3
sh-5.1# pacman -S grub
warning: grub-2:2.12rc1-1 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...
Packages (1) grub-2:2.12rc1-1
Total Installed Size: 32.91 MiB
Net Upgrade Size: 0.00 MiB
:: Proceed with installation? [Y/n] y
(1/1) checking keys in keyring [###############################] 100%
(1/1) checking package integrity [###############################] 100%
(1/1) loading package files [###############################] 100%
(1/1) checking for file conflicts [###############################] 100%
(1/1) checking available disk space [###############################] 100%
:: Processing package changes...
(1/1) reinstalling grub [###############################] 100%
:: To use the new features provided in this GRUB update, it is recommended
to install it to the MBR or UEFI. Due to potential configuration
incompatibilities, it is advised to run both, installation and generation
of configuration:
$ grub-install ...
$ grub-mkconfig -o /boot/grub/grub.cfg
:: Running post-transaction hooks...
(1/2) Arming ConditionNeedsUpdate...
(2/2) Updating the info directory file...
sh-5.1# grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=GRUB
Installing for x86_64-efi platform.
Installation finished. No error reported.
sh-5.1# grub-mkconfig -o /boot/grub/grub.cfg
Generating grub configuration file ...
Adding boot menu entry for UEFI Firmware Settings ...
done
sh-5.1#
The grub menu still hasn’t any entries tho…
That looks good! Now you should be able to boot Arch (via Arch’s Grub) from that UEFI boot variable.
Next, boot up Garuda and run sudo update-grub one more time and hopefully it will add Arch into Garuda’s boot menu. 
You would have to configure Arch’s Grub to use OS prober, plus some other configuration to get it to detect other distros. It will be easier to get Garuda’s Grub to detect Arch, and just use that Grub for booting everything.
3 Likes
https://i.imgur.com/AFVN6jf.png 
The output of update-grub was excactly as the other times and there’s still no arch entry
What is the init system you are using on Arch? Are the kernels and initramfs images in /boot, or somewhere else? I’m afraid you may need to get back in the chroot and take a look.
1 Like
╭─stk@stk in /boot🔒 took 1ms
╰─λ ls
drwxr-xr-x - root 1 Jan 1970 efi
drwxr-xr-x - root 7 Sep 21:41 grub
drwxr-xr-x - root 7 Sep 06:33 memtest86+
.rw------- 89M root 7 Sep 06:34 initramfs-linux-zen-fallback.img
.rw------- 33M root 7 Sep 06:33 initramfs-linux-zen.img
.rw-r--r-- 7,4M root 8 Aug 20:19 intel-ucode.img
.rw-r--r-- 14M root 7 Sep 06:33 vmlinuz-linux-zen
systemd I suppose, as there are multiple files with ‘systemd’ in them in /bin
That's your Garuda /boot. I meant in your Arch installation, you will have to look in /boot and make sure you see a kernel and an initramfs. It seems like Grub is not finding anything to boot with.
If /boot is empty, from the chroot you will need to install a kernel, then build the initramfs.
pacman -S linux
mkinitcpio -P
After you confirm you have a kernel and initramfs image in /boot, you will have to update the Grub configuration file again.
grub-mkconfig -o /boot/grub/grub.cfg
5 Likes
Grub now shows arch again! I’ll update grub in garuda again now, as you wrote above.
AHHH I'm dreaming 
Thank you so much!!! You're so kind and patient with me it's amazing.
Of course also a big thanks to the other helpers 
3 Likes
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.