Root Partition Changed

[Mic_Ifhonce]

I just update my system and reboot the system. I'm dual boot my machine with windows that stored in different SSD which I don't open for a couple of months now if it might help.
The issue it stuck in the initrd from grub. The path of file which Grub used for boot like vmlinuz-linux-zen and initramfs-linux-zen accessed with @/ as the root too. When I enter the Grub command line, I run command below:

grub > ls
(hd0) (hd0,gpt3) (hd0,gpt2) (hd0,gpt1) (hd1) (hd1,gpt2) (hd1,gpt1)
grub > ls (hd0,gpt2)/
@cache @/ @root/ @tmp/ @home/ @log/ @srv/
grub > ls (hd0,gpt2)/@/
dev/ run/ boot/ lib sbin srv/ usr/ opt/ lib64/ bin home/ etc/ var/ tmp/ sys/ mnt/ proc/ root/
grub > ls (hd0,gpt2)/@/boot/
initramfs-linux-zen-fallback.img initramfs-linux-zen.img intel-unicode.img grub/ amd-ucode.img vmlinuz-linux-zen efi/ memtest/

after that I try to boot using:

grub > set root=(hd0,gpt2)
grub > linux /@/boot/vmlinuz-linux-zen.img root=/dev/sda2
grub > initrd /@/boot/initramfs-linux-zen.img
grub > boot

But it didn't fix the issue, it's just stuck in the grub command line display. When I try to chroot with live-usb it can't detect my partition.

Edit:
I already find the problem why I can't detect the partition. It's regarding the hardware company of the SSD can't be detected other than using zen-kernel, so I use live-usb with garuda ISO. The problem right now are the changes in the partition of my linux file as shown below when I try to use my program it's work fine:

[root@garuda-kde-lite garuda]# lsblk
nvme0n1     259:0    0 476.9G  0 disk 
├─nvme0n1p1 259:1    0   300M  0 part 
├─nvme0n1p2 259:2    0 467.8G  0 part 
└─nvme0n1p3 259:3    0   8.8G  0 part
[root@garuda-kde-lite garuda]# mount /dev/nv
nvme0      nvme0n1    nvme0n1p1  nvme0n1p2  nvme0n1p3  nvram      
[root@garuda-kde-lite garuda]# mount /dev/nvme0n1p2 /mnt
[root@garuda-kde-lite garuda]# ls /mnt
@  boot  @cache  @home  @log  @root  @srv  @tmp
[root@garuda-kde-lite garuda]# ls /mnt/@
bin  boot  dev  etc  home  lib  lib64  mnt  opt  proc  root  run  sbin  srv  sys  tmp  usr  var
[root@garuda-kde-lite garuda]# arch-chroot /mnt/@
==> WARNING: /mnt/@ is not a mountpoint. This may have undesirable side effects.
[root@garuda-kde-lite /]# pfetch
    ___       garuda@garuda-kde-lite
   (.. |      os     Garuda Linux
   (<> |      host   Aspire A514-52G V1.12
  / __  \     kernel 6.2.13-zen-1-zen
 ( /  \ /|    uptime 2h 28m
_/\ __)/_)    pkgs   1241
\/-____\/     memory 3160M / 11667M

Below when I try to update using pacman :

:: Proceed with installation? [Y/n] 
error: could not determine cachedir mount point /var/cache/pacman/pkg
error: failed to commit transaction (not enough free disk space)
Errors occurred, no packages were upgraded.

The output of efiboomgr from the live ISO:

BootCurrent: 0000
Timeout: 0 seconds
BootOrder: 0001,0002,2001,2002,2003
Boot0000* USB HDD: USB  PciRoot(0x0)/Pci(0x14,0x0)/USB(14,0)/HD(2,MBR,0xc5a43d17,0x7289000,0x10000)RC
Boot0001* Garuda        HD(1,GPT,546eef13-7329-7349-bc1d-5845ec2cf516,0x1000,0x96000)/File(\EFI\Garuda\grubx64.efi)
Boot0002* Windows Boot Manager  HD(1,GPT,546eef13-7329-7349-bc1d-5845ec2cf516,0x1000,0x96000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)57494e444f5753000100000088000000780000004200430044004f0042004a004500430054003d007b00390064006500610038003600320063002d0035006300640064002d0034006500370030002d0061006300630031002d006600330032006200330034003400640034003700390035007d00000000000100000010000000040000007fff0400
Boot2001* EFI USB Device        RC
Boot2002* EFI DVD/CDROM RC
Boot2003* EFI Network   RC

and lsblk -f command:

NAME        FSTYPE   FSVER            LABEL                 UUID                                 FSAVAIL FSUSE% MOUNTPOINTS
loop0       squashfs 4.0                                                                               0   100% /run/miso/sfs/livefs
loop1       squashfs 4.0                                                                               0   100% /run/miso/sfs/mhwdfs
loop2       squashfs 4.0                                                                               0   100% /run/miso/sfs/desktopfs
loop3       squashfs 4.0                                                                               0   100% /run/miso/sfs/rootfs
sda                                                                                                             
├─sda1      ntfs                                            6606225D06222F0D                       40.5G    59% /run/media/garuda/6606225D06222F0D
└─sda2                                                                                                          
sdb                                                                                                             
├─sdb1      exfat    1.0              Ventoy                7B93-BAB5                                           
│ └─ventoy  iso9660  Joliet Extension GARUDA_KDELITE_RAPTOR 2023-05-01-22-43-28-00                     0   100% /run/miso/bootmnt
└─sdb2                                                                                                          
zram0                                                                                                           [SWAP]
nvme0n1                                                                                                         
├─nvme0n1p1 vfat     FAT32                                  EF59-4196                                           
├─nvme0n1p2 btrfs                                           b94c9465-09d9-48a9-973e-7ad9526ce84f  201.5G    57% /mnt
└─nvme0n1p3 swap     1                swap                  0d5ef773-b5c0-4755-b443-30f3c0b42115

[gaustin]

seems like it detected on GRUB but cannot be detected on live-USB ?
is it because of the kernel because garuda use linux-zen as you mentioned in your /boot dir

[SGS]

How did you try to chroot?

Please post as requested in the template your garuda-inxi, also goes from the live ISO.
Post also as text output from

efibootmgr
lsblk -f

Read

Computer doesn’t boot, boots to a black screen, or stops at a message

While there are many potential reasons why your installation doesn’t boot to a desktop, the primary reason is that the graphics drivers haven’t loaded correctly so your login/display manager (DM) doesn’t start. This is why you get a “black screen” or stuck at an [ OK ] Started some service message. The normal reason for this is that you have the incorrect driver version for the kernel. This can happens when the mirror you are updating from is not fully synchronised, or times out, and so y…

How to chroot Garuda Linux

From Grub fails after update - #3 by librewish Some unlucky times that your system is not bootable and the only advised option is to use chroot from a Live ISO to repair the installed system (for example, to (re)install the bootloader), here is the suggested method: steps required to chroot to your installed Garuda installation (btrfs) Boot to a Garuda usb Live ISO Start a terminal and Find your installed system (btrfs) partition, you need the /dev/<something> part. lsblk -f Warning: Remem…

[Mic_Ifhonce]

The problem of chroot from live-usb already solved with the ISO from Garuda Linux that use zen-kernel because it's a problem in the past my Kingston SSD cannot be detected from other kernel except zen-kernel.

I've updated the issue regarding the changes of the partition. Thanks for your response before.

[Mic_Ifhonce]

Yes, that's right. The manufacture company that produces the SSD already said that the type of my SSD didn't compatible enough with the kernel based on what I read and can't be detected with other kernel other than zen-kernel as I've experience so far.

I've updated the issue regarding the changes of the partition. Thanks for your response before.

[SGS]

@Mic_Ifhonce

garuda-kde-lite

That is your Garuda DE on metal also?
Your problem is solved?
If not

@SGS

Please post as requested in the template your garuda-inxi, also goes from the live ISO.
Post also as text output from

efibootmgr
lsblk -f

[Mic_Ifhonce]

The garuda-kde-lite is the live ISO that I'm trying to chroot from. My DE on metal is Plasma.

Regarding my problem right now are the partition that changes will affect the file system of my partition as I shown when I try to mount /mnt that throw error, instead I use the /mnt/@ as the root folder.

The output of efiboomgr from the live ISO:

BootCurrent: 0000
Timeout: 0 seconds
BootOrder: 0001,0002,2001,2002,2003
Boot0000* USB HDD: USB  PciRoot(0x0)/Pci(0x14,0x0)/USB(14,0)/HD(2,MBR,0xc5a43d17,0x7289000,0x10000)RC
Boot0001* Garuda        HD(1,GPT,546eef13-7329-7349-bc1d-5845ec2cf516,0x1000,0x96000)/File(\EFI\Garuda\grubx64.efi)
Boot0002* Windows Boot Manager  HD(1,GPT,546eef13-7329-7349-bc1d-5845ec2cf516,0x1000,0x96000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)57494e444f5753000100000088000000780000004200430044004f0042004a004500430054003d007b00390064006500610038003600320063002d0035006300640064002d0034006500370030002d0061006300630031002d006600330032006200330034003400640034003700390035007d00000000000100000010000000040000007fff0400
Boot2001* EFI USB Device        RC
Boot2002* EFI DVD/CDROM RC
Boot2003* EFI Network   RC

and lsblk -f command:

NAME        FSTYPE   FSVER            LABEL                 UUID                                 FSAVAIL FSUSE% MOUNTPOINTS
loop0       squashfs 4.0                                                                               0   100% /run/miso/sfs/livefs
loop1       squashfs 4.0                                                                               0   100% /run/miso/sfs/mhwdfs
loop2       squashfs 4.0                                                                               0   100% /run/miso/sfs/desktopfs
loop3       squashfs 4.0                                                                               0   100% /run/miso/sfs/rootfs
sda                                                                                                             
├─sda1      ntfs                                            6606225D06222F0D                       40.5G    59% /run/media/garuda/6606225D06222F0D
└─sda2                                                                                                          
sdb                                                                                                             
├─sdb1      exfat    1.0              Ventoy                7B93-BAB5                                           
│ └─ventoy  iso9660  Joliet Extension GARUDA_KDELITE_RAPTOR 2023-05-01-22-43-28-00                     0   100% /run/miso/bootmnt
└─sdb2                                                                                                          
zram0                                                                                                           [SWAP]
nvme0n1                                                                                                         
├─nvme0n1p1 vfat     FAT32                                  EF59-4196                                           
├─nvme0n1p2 btrfs                                           b94c9465-09d9-48a9-973e-7ad9526ce84f  201.5G    57% /mnt
└─nvme0n1p3 swap     1                swap                  0d5ef773-b5c0-4755-b443-30f3c0b42115

[SGS]

Just follow How to chroot Garuda Linux

Maybe I do not understand the problem. You mount

@Mic_Ifhonce

nvme0n1p2

?
You want to boot windows on sda2?
Repair garuda grub on nvme first, later use garuda-boot-option to change boot order or use efibootmgr for that.

Also, did you try to boot with last working snapshot?

Restoring snapshots to get the system back to working state

[Mic_Ifhonce]

The problem is that I chroot into the /mnt/@ that mounted from the partition /dev/nvme0n1p1 because I can't chroot only with the /mnt which are the common part when we chroot into the root directory.

Which is why I can't update the system and I encounter:

could not determine cachedir mount point /var/cache/pacman/pkg

When I try to fix the grub, first I mount my efi partition which is /dev/nvme0n1p1 and run grub-install:

> mount /dev/nvme0n1p1 /boot/efi
> grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=grub

the grub install returns error:

grub-install: error: cannot find a device for /boot/grub (is /dev mounted?).

Then I try to mount and arch-chroot again but it returns other issue :

mount -o bind /dev /mnt/dev
mount -t proc /proc /mnt/proc
mount -o bind /sys /mnt/sys

error

==> WARNING: /mnt/@ is not a mountpoint. This may have undesirable side effects.

Sorry if I can't explain it well because I'm new to this. Thanks for your response anyway.

[Mic_Ifhonce]

The last option for me is to reinstall Garuda after I backup my /@home from the live-ISO because it's urgent for me.

I try twice to install Garuda on the same SSD and after I reboot second time it came with the same issue in the grub with the root partition changed into /@ and the linux and initrd take the file from /@/boot/.

The last resort I do is to use another SSD that could detected even if it's not zen-kernel, and I'm already using the snapshot because the last time I didn't.

Thanks for all the response and help.