I might be misuerstanding, but do you want me to boot off a snapshot and try garuda-update from it?
No. I was suggesting to first try the chroot, garuda-update and kernel reinstallation.
If this should not help, I was reminding the possibility to restore a snapshot.
Thanks for the response, had a chuckle.
But essentially I updated the system through Garuda Helper as usual and I got the same issue as the other chap in the other post. I can’t boot in to the OS. I can however boot in to a Snapshot. But… The issue is nothing on the snapshot besides photos, videos etc work. Firedragon says there is no profile, other software just won’t load and so forth.
As for fixing this, what steps are needed? As I said, I’m a bit of a caveman.
Here is my attempt at updating it from the live environment. It says there is no space even though I know there is.
╭─garuda@garuda in ~ as 🧙
╰─λ 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
├─sda1 ntfs 307CC93C7CC8FE1A
├─sda2 vfat FAT32 48E2-7C54
├─sda3
├─sda4
└─sda5 ntfs 4E28335A28333FEF
sdb iso966 Jolie GARUDA_GNOME_RAPTOR
2023-03-19-16-49-22-00
├─sdb1 iso966 Jolie GARUDA_GNOME_RAPTOR
│ 2023-03-19-16-49-22-00 0 100% /run/miso/bootmnt
└─sdb2 vfat FAT12 MISO_EFI B49B-B214
zram0 [SWAP]
nvme1n1
├─nvme1n1p1
│ vfat FAT32 497C-2B30
└─nvme1n1p2
crypto 1 f2314da2-7bb3-4bfa-83ba-9a58d102e216
nvme0n1
├─nvme0n1p1
│ vfat FAT32 1228-F410
├─nvme0n1p2
│
└─nvme0n1p3
╭─garuda@garuda in ~ as 🧙 took 14ms
╰─λ sudo mkdir -p /mnt/broken
╭─garuda@garuda in ~ as 🧙 took 7ms
╰─λ sudo cryptsetup open /dev/nvme1n1p2 crypto_LUKS
Enter passphrase for /dev/nvme1n1p2:
╭─garuda@garuda in ~ as 🧙 took 4s
╰─λ
╭─garuda@garuda in ~ as 🧙 took 4s
╰─λ sudo mkdir -p /mnt/broken
╭─garuda@garuda in ~ as 🧙 took 7ms
╰─λ sudo mount /dev/mapper/crypto_LUKS /mnt/broken
╭─garuda@garuda in ~ as 🧙 took 80ms
╰─λ sudo garuda-chroot /mnt/broken/@
sh-5.2# garuda-update
:: Synchronizing package databases...
error: failed to synchronize all databases (unable to lock database)
:: Synchronizing package databases...
error: failed to synchronize all databases (unable to lock database)
mkdir: cannot create directory '/var/log/garuda/': No space left on device
sh-5.2# pacman -S linux-zen linux-zen-headers
error: failed to init transaction (unable to lock database)
error: could not lock database: No space left on device
sh-5.2#
Try this one instead (after opening and mounting crypto)
sudo garuda-chroot /mnt/broken
1 Like
Is this right?
╭─garuda@garuda in ~ as 🧙 took 95ms
╰─λ sudo garuda-chroot /mnt/broken
mount: /mnt/broken/proc: mount point does not exist.
dmesg(1) may have more information after failed mount system call.
==> ERROR: failed to setup API filesystems in chroot /mnt/broken
umount: bad usage
Try 'umount --help' for more information.
╭─garuda@garuda in ~ as 🧙 took 57ms
[⚡] ×
Try with -a, like this:
garuda-chroot -a
It should ask you to identify the Linux partition, and then automatically mount the subvolumes and set the chroot for you.
Now what?
╭─garuda@garuda in ~ as 🧙 took 57ms
[⚡] × garuda-chroot -a
==> Mounting (Garuda_Linux) [/dev/mapper/crypto_LUKS]
--> mount: [/mnt]
--> mount: [/mnt/boot/efi]
[root@garuda-gnome /]#
Now you attempt the update.
garuda-update
Mission failed, sad times.
╭─garuda@garuda in ~ as 🧙 took 57ms
[⚡] × garuda-chroot -a
==> Mounting (Garuda_Linux) [/dev/mapper/crypto_LUKS]
--> mount: [/mnt]
--> mount: [/mnt/boot/efi]
[root@garuda-gnome /]# garuda-update
:: Synchronizing package databases...
error: failed to synchronize all databases (unable to lock database)
:: Synchronizing package databases...
error: failed to synchronize all databases (unable to lock database)
mkdir: cannot create directory '/var/log/garuda/': No space left on device
[root@garuda-gnome /]#
rm /var/lib/pacman/db.lck
[root@garuda-gnome /]# rm /var/lib/pacman/db.lck
rm: cannot remove '/var/lib/pacman/db.lck': No such file or directory
[root@garuda-gnome /]#
Encrypted or decrypted database?
Seems it is not my …
Year 
Yes, the device is full. I think we already knew that. You need to create some space to continue.
Clear the package cache:
paccache -rk0
Also delete some snapshots with Btrfs Assistant.
1 Like
It can’t be full, it has 41gb free.
I think the issue is because I used rufus to flash the usb drive I’m using, it’s saying that is full.
Anyway here is what I get.
[root@garuda-gnome /]# paccache -rk0
==> ERROR: cachedir '/var/cache/pacman/pkg/' does not exist or is not a directory
[root@garuda-gnome /]#
Perhaps you have chrooted the wrong device.
1 Like
I’m still new to this, can you identify from this?
╭─garuda@garuda in ~ as 🧙
╰─λ 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
├─sda1 ntfs 307CC93C7CC8FE1A
├─sda2 vfat FAT32 48E2-7C54
├─sda3
├─sda4
└─sda5 ntfs 4E28335A28333FEF
sdb iso966 Jolie GARUDA_GNOME_BIRDOFPREY 2024-04-28-13-31-10-00
├─sdb1 iso966 Jolie GARUDA_GNOME_BIRDOFPREY 2024-04-28-13-31-10-00 0 100% /run/miso/bootmnt
└─sdb2 vfat FAT12 MISO_EFI EFF1-3B17
zram0 [SWAP]
nvme1n1
├─nvme1n1p1
│ vfat FAT32 497C-2B30 298.7M 0% /mnt/boot/efi
└─nvme1n1p2
│ crypto 1 f2314da2-7bb3-4bfa-83ba-9a58d102e216
└─crypto_LUKS
btrfs d06acea6-ea8c-4f8f-941c-00a29881dbad /mnt
/mnt/broken
nvme0n1
├─nvme0n1p1
│ vfat FAT32 1228-F410
├─nvme0n1p2
│
└─nvme0n1p3
Oh hmm…you already have the disk mounted here and there from some of the other efforts in the thread. It is likely that is the issue.
Let’s try to start fresh by rebooting. Then come back into the live environment, unlock the LUKS device, and run garuda-chroot -a again.
Alright, I’m freshly rebooted, I’ve gone in the file manager, clicked the drive, unlocked and I’m here in terminal.
╭─garuda@garuda in ~ as 🧙
╰─λ garuda-chroot -a
==> Mounting (Garuda_Linux) [/dev/mapper/luks-f2314da2-7bb3-4bfa-83ba-9a58d102e216]
--> mount: [/mnt]
--> mount: [/mnt/boot/efi]
[root@garuda-gnome /]#
Hmm, still looks funny. What does this command output?
findmnt --real