Post /etc/fstab file from the installed garuda.
Also post
lsblk -f -o +PARTUUID
1 Like
Go ahead and reinstall the kernel and let’s check the output of that. Then exit out of the chroot and try booting to Garuda again.
╭─garuda@garuda in ~ as 🧙 took 114ms
╰─λ sudo garuda-chroot /mnt/broken/@
sh-5.2# cat /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=20E2-A57F /boot/efi vfat defaults,noatime 0 2
UUID=d2cdbdd3-8fc6-4d34-aca1-3d4511cf1264 / btrfs subvol=/@,defaults,noatime,compress=zstd 0 0
UUID=d2cdbdd3-8fc6-4d34-aca1-3d4511cf1264 /home btrfs subvol=/@home,defaults,noatime,compress=zstd 0 0
UUID=d2cdbdd3-8fc6-4d34-aca1-3d4511cf1264 /root btrfs subvol=/@root,defaults,noatime,compress=zstd 0 0
UUID=d2cdbdd3-8fc6-4d34-aca1-3d4511cf1264 /srv btrfs subvol=/@srv,defaults,noatime,compress=zstd 00
UUID=d2cdbdd3-8fc6-4d34-aca1-3d4511cf1264 /var/cache btrfs subvol=/@cache,defaults,noatime,compress=zstd0 0
UUID=d2cdbdd3-8fc6-4d34-aca1-3d4511cf1264 /var/log btrfs subvol=/@log,defaults,noatime,compress=zstd 00
UUID=d2cdbdd3-8fc6-4d34-aca1-3d4511cf1264 /var/tmp btrfs subvol=/@tmp,defaults,noatime,compress=zstd 00
tmpfs /tmp tmpfs defaults,noatime,mode=1777 0 0
sh-5.2# lsblk -f -o +PARTUUID
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS PARTUUID
loop0
loop1
loop2
loop3
sda
|-sda1
`-sda2 808.5G 13% /
sdb
|-sdb1
`-sdb2
zram0 [SWAP]
nvme0n1
|-nvme0n1p1
|-nvme0n1p2
|-nvme0n1p3
|-nvme0n1p4
|-nvme0n1p5
`-nvme0n1p6
sh-5.2#
This has no output. Try it outside of chroot. We need to compare UUIDs and PartUUIDs to confirm the proper ESP .
lsblk -f -o +PARTUUID /dev/sda1
lsblk -f -o +PARTUUID /dev/sdb1
lsblk -f -o +PARTUUID /dev/nvme0n1p1
1 Like
You are missing a lot of mount points. It looks like you did not run garuda-chroot -a.
Here
╭─garuda@garuda in ~ as 🧙 took 5s
╰─λ lsblk -f -o +PARTUUID /dev/sda1
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS PARTUUID
sda1 vfat FAT32 4E38-566A 65429e5f-6f53-304e-b10b-a68cf8025aa4
╭─garuda@garuda in ~ as 🧙 took 34ms
╰─λ lsblk -f -o +PARTUUID /dev/sdb1
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS PARTUUID
sdb1 iso966 Jolie GARUDA_DR460NIZED_RAPTOR 2023-10-29-09-55-02-00 0 100% /run/miso/bootmnt
╭─garuda@garuda in ~ as 🧙 took 5ms
╰─λ lsblk -f -o +PARTUUID /dev/nvme0n1p1
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS PARTUUID
nvme0n1p1
vfat FAT32 ESP 20E2-A57F 23fb5d92-9662-4a5d-b730-c10ef99ab09a
Sorry, i hit my max number of replies for the day.
Sorry about that, that did not occur to me. I have set you to TL1 so we don’t run into that issue again.
This is the device we should be mounting. I’m not sure how /dev/sda got wrapped up in it last time, but as far as I can tell that is something else and should be left out of it altogether.
Try again to set the garuda-chroot.
garuda-chroot -a
This should give you options of what system you want to mount, and if you choose the Garuda install it will set up all the mount points from fstab that it can.
Post any errors you get into the thread if garuda-chroot doesn’t work for some reason.
1 Like
This is what I get if I try and run garuda-chroot -a
╭─garuda@garuda in ~ as 🧙 took 125ms
╰─λ garuda-chroot -a
==> ERROR: No Linux partitions detected!
╭─garuda@garuda in ~ as 🧙 took 7s
[⚡] × sudo mkdir -p /mnt/broken
╭─garuda@garuda in ~ as 🧙 took 20ms
╰─λ sudo mount /dev/sda2 /mnt/broken/
╭─garuda@garuda in ~ as 🧙 took 82ms
╰─λ garuda-chroot -a
==> ERROR: No Linux partitions detected!```Okay, that’s kind of bad but not necessarily the end of the world because we can do it manually.
This should not be part of it, remember? We are going to leave /dev/sda out of it. Let’s unmount this device before we begin:
sudo umount /dev/sda2
Next, let’s try mounting the root subvolume.
sudo mount -o subvol=@ /dev/nvme0n1p2 /mnt
1 Like
No, I think that’s Windows stuff
It should be sda2
3 Likes
This is the error I got.
>╭─garuda@garuda in ~ as 🧙 took 88ms
[🔴] × sudo mount -o subvol=@ /dev/nvme0n1p2 /mnt
mount: /mnt: wrong fs type, bad option, bad superblock on /dev/nvme0n1p2, missing codepage or helper program, or other error.
dmesg(1) may have more information after failed mount system call.
It worked with sda 2
I guess Garuda ESP is not on the same drive as Garuda root (@).
1 Like
My mistake, I was confused because it appears the EFI partition in fstab is on nvme0n1p1:
But then the boot variable points to /dev/sda:
I think this was caused by reinstalling Grub when the correct EFI partition was not mounted, but I am not sure.
It’s kind of a mess! 
2 Likes
Different disks.
1 Like
Probably the Garuda installation is piggy-backing on the EFI partition from Windows.
So:
sudo mount -o subvol=@ /dev/sda2 /mnt
sudo mount -o subvol=@home /dev/sda2 /mnt/home
sudo mount -o subvol=@root /dev/sda2 /mnt/root
sudo mount -o subvol=@srv /dev/sda2 /mnt/srv
sudo mount -o subvol=@cache /dev/sda2 /mnt/var/cache
sudo mount -o subvol=@log /dev/sda2 /mnt/var/log
sudo mount -o subvol=@tmp /dev/sda2 /mnt/var/tmp
sudo mount /dev/nvme0n1p1 /mnt/boot/efi
arch-chroot /mnt
4 Likes
Done
Install grub with the above and recreate grub config
update-grub
1 Like
This is the output.
[root@garuda-dr460nized /]# grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=garuda --recheck
Installing for x86_64-efi platform.
Installation finished. No error reported.
[root@garuda-dr460nized /]# 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
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.
grub-probe: error: cannot find a GRUB drive for /dev/sdb1. Check your device.map.
grub-probe: error: cannot find a GRUB drive for /dev/sdb1. Check your device.map.
Adding boot menu entry for UEFI Firmware Settings ...
Detecting snapshots ...
Found snapshot: 2024-06-06 21:11:32 | @/.snapshots/251/snapshot | post | linux-zen |
Found snapshot: 2024-06-06 10:04:17 | @/.snapshots/247/snapshot | pre | pacman -Su |
Found snapshot: 2024-04-22 09:38:16 | @/.snapshots/246/snapshot | post | aalib accountsservice alsa-card-profiles attica baloo beautyline bind bi |
Found snapshot: 2024-04-22 09:31:02 | @/.snapshots/245/snapshot | pre | pacman -Su |
Found snapshot: 2024-04-13 11:31:02 | @/.snapshots/244/snapshot | post | alsa-card-profiles ark aspnet-runtime-6.0 aspnet-runtime-7.0 baloo-widge |
Found snapshot: 2024-04-13 11:27:00 | @/.snapshots/243/snapshot | pre | pacman -Su --config /tmp/tmp.EQ9gQtAm4g |
Found snapshot: 2024-04-11 21:42:30 | @/.snapshots/242/snapshot | pre | pacman -Su |
Found snapshot: 2024-04-03 11:49:57 | @/.snapshots/241/snapshot | pre | pacman -S scanner-support printer-support --needed |
Found snapshot: 2024-04-01 20:28:23 | @/.snapshots/238/snapshot | post | nmap |
Found snapshot: 2024-04-01 20:28:21 | @/.snapshots/237/snapshot | pre | pacman -S --config /etc/pacman.conf -- extra/nmap |
Found snapshot: 2024-03-30 21:18:47 | @/.snapshots/236/snapshot | post | postman-bin |
Found snapshot: 2024-03-30 21:18:38 | @/.snapshots/235/snapshot | pre | pacman -S --config /etc/pacman.conf -- chaotic-aur/postman-bin |
Found 12 snapshot(s)
Unmount /tmp/grub-btrfs.oY3wq8YCDa .. Success
Found memtest86+ image: /boot/memtest86+/memtest.bin
done
[root@garuda-dr460nized /]#
It looks fine.
Now update your system packages.
garuda-update
3 Likes