I’m doing this off my phone so excuse typos, formatting, photo size whatever.
Powered on PC just fine, unlocked disk encryption, logged in, got to to desktop, opened ghostty and started a garuda-update and it started chugging along. Was going fine until a few gave a 500 error, no biggie. Ran garuda-update again, thing ran just fine until I hit the last pack, google fonts (I should’ve gotten rid of it tbh it always takes forever) and it gets to 99% and then the bg goes black (as in, no toolbar etc, but the ghostty window stayed and I could type and move my mouse around). In hindsight I should’ve taken pictures at that time and ask around before powering down through terminal. On reboot I’m met with this after unlocking encryption
Okay so I have realised I have another problem. I don’t have a live usb ready to go and I don’t exactly have another computer. I’ll have to ask my brother to do one for me. It might have to wait for tomorrow depending on his schedule. Edit: I’ll have a live stick tomorrow, I’ll reply here how it goes.
alright I have a live-usb and booted into it, but when I try to chroot it says ==> ERROR: No Linux partitions detected!. I then did a garuda-update regardless, but no difference. Here’s my lsblk
lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 16.8M 1 loop /run/miso/sfs/livefs
loop1 7:1 0 357.7M 1 loop /run/miso/sfs/mhwdfs
loop2 7:2 0 3.4G 1 loop /run/miso/sfs/desktopfs
loop3 7:3 0 725.8M 1 loop /run/miso/sfs/rootfs
sda 8:0 0 1.8T 0 disk
└─sda1 8:1 0 1.8T 0 part
sdb 8:16 1 14.9G 0 disk
├─sdb1 8:17 1 4.6G 0 part /run/miso/bootmnt
└─sdb2 8:18 1 4M 0 part
zram0 253:0 0 30.5G 0 disk [SWAP]
nvme0n1 259:0 0 1.8T 0 disk
└─nvme0n1p1 259:1 0 1.8T 0 part /run/media/garuda/9753a0ab-acd4-4ce3-a143-70337a937818
nvme1n1 259:2 0 931.5G 0 disk
├─nvme1n1p1 259:3 0 300M 0 part
└─nvme1n1p2 259:4 0 931.2G 0 part
and sudo parted -l
sudo parted -l
Model: ATA WDC WD2003FZEX-0 (scsi)
Disk /dev/sda: 2000GB
Sector size (logical/physical): 512B/4096B
Partition Table: msdos
Disk Flags:
Number Start End Size Type File system Flags
1 1049kB 2000GB 2000GB primary ntfs
Model: Verbatim STORE N GO (scsi)
Disk /dev/sdb: 16.0GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:
Number Start End Size Type File system Flags
2 4906MB 4910MB 4194kB primary esp
Model: Samsung SSD 980 PRO 2TB (nvme)
Disk /dev/nvme0n1: 2000GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
1 1049kB 2000GB 2000GB btrfs
Model: Samsung SSD 970 EVO Plus 1TB (nvme)
Disk /dev/nvme1n1: 1000GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
1 2097kB 317MB 315MB fat32 boot, esp
2 317MB 1000GB 1000GB root
Model: Unknown (unknown)
Disk /dev/zram0: 32.7GB
Sector size (logical/physical): 4096B/4096B
Partition Table: loop
Disk Flags:
Number Start End Size File system Flags
1 0.00B 32.7GB 32.7GB linux-swap(v1)
nvme1n1p2 is where my garuda installation is/was(?) and nvme0n1 is my new storage drive, and sda is my old storage drive.
edit: i went and decrypted the drive but no difference for chroot, new lsblk
sudo lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 16.8M 1 loop /run/miso/sfs/livefs
loop1 7:1 0 357.7M 1 loop /run/miso/sfs/mhwdfs
loop2 7:2 0 3.4G 1 loop /run/miso/sfs/desktopfs
loop3 7:3 0 725.8M 1 loop /run/miso/sfs/rootfs
sda 8:0 0 1.8T 0 disk
└─sda1 8:1 0 1.8T 0 part /run/media/garuda/Storage
sdb 8:16 1 14.9G 0 disk
├─sdb1 8:17 1 4.6G 0 part /run/miso/bootmnt
└─sdb2 8:18 1 4M 0 part
zram0 253:0 0 30.5G 0 disk [SWAP]
nvme0n1 259:0 0 1.8T 0 disk
└─nvme0n1p1 259:1 0 1.8T 0 part /run/media/garuda/9753a0ab-acd4-4ce3-a143-70337a937818
nvme1n1 259:2 0 931.5G 0 disk
├─nvme1n1p1 259:5 0 300M 0 part
└─nvme1n1p2 259:6 0 931.2G 0 part
└─nvme1n1p2_crypt 254:0 0 931.2G 0 crypt /run/media/garuda/4f5db719-10c0-41bd-91b7-f6a68cb5a06d
Edit4: So my current theory on what happened was I hadn’t checked my storage capacity in a while and it capped during the garuda-update and it broke some stuff.
Maybe you could try with the menual chroot procedure, as opposed to the button. https://forum.garudalinux.org/t/how-to-chroot-garuda-linux/4004
Probably you’ll have to first decrypt the drive and use /dev/nvme1n1p2_crypt insead of /dev/nvme0n1p2 (or try sudo mount /dev/mapper/crypto_LUKS /mnt/broken) , while the EFI system partition should be /dev/nvme1n1p1 insead of /dev/nvme0n1p4.
Okay so I tried it and after doing sudo mount /dev/nvme0n1p2 /mnt/broken
I get mount: /mnt/broken: unknown filesystem type 'crypto_LUKS'. dmesg(1) may have more information after failed mount system call.
I tried mapper and it said it didn’t exist so I might’ve put the wrong names. As for unlocking I had unlocked it to delete the cache, idk if I need to do a separate luks command or something. I’ll get back home in a few hours.
