I don’t know what else to say or what other logs to give other that what I have below. Thank you for the help.
~ 11:38:29
❮ sudo limine-snapper-sync
Stop creating a snapshot boot entry because the boot partition usage limit 85.0% is exceeded.
Saved: /boot/8e894020c9ab48be8cae43e3b9a5598f/limine_history/snapshots.json
Updated: /boot/limine.conf
~ 11:38:42
❮ sudo limine-snapper-info
Version : 1.20.0
Manifest version : 1.3.0
UUID : 619cf237-3877-416c-a318-6b2aab55db2a
Last snapshot : ID: 498, date: 2025-09-26 23:28:22
Snapshots : 0 (max 8)
ESP usage : 45.4% of 2.00 GiB (max 85.0%)
Unused files : 0
Missed files : 0
Corrupted files : 0
~ 11:38:54
❮ df -h /boot
Filesystem Size Used Avail Use% Mounted on
/dev/nvme1n1p1 2.0G 928M 1.1G 46% /boot
~ 11:39:01
❮ sudo limine-snapper-list
ID │ Date │ Description
────┼───────────┼─────────────
~ 11:41:51
❮ lsblk -f
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
# I also have a windows drive nvme0n1 and sda is a HDD for media.
zram0 swap 1 zram0 e3b51290-5582-4a70-90bd-e5ab248bf116 [SWAP]
nvme1n1
├─nvme1n1p1 vfat FAT32 6439-85CB 1.1G 45% /boot
└─nvme1n1p2 btrfs 619cf237-3877-416c-a318-6b2aab55db2a 309G 66% /home
/root
/var/cache
/var/log
/srv
/var/tmp
/
I don’t have even the slightest idea of what is take up all the space. My main problem isn’t that the snapshot feature isn’t work but the fact that I don’t know why its saying 85% of the boot partition has been usage up is my main concern. Just like you said I could just increase the size of the partition but that might just delay my issue until later and then I would have the same issue but twice the size.
du -hsc /boot/* ~ ❮ sudo du -hsc /boot 928M /boot 928M total ~ ❮ sudo snapper list-configs Config │ Subvolume ───────┼────────── root │ / ~ ❮ sudo du -hsc /.snapshots/ 237G /.snapshots/ 237G total ~ ❮ df -h Filesystem Size Used Avail Use% Mounted on dev 16G 0 16G 0% /dev run 16G 2.6M 16G 1% /run efivarfs 128K 69K 55K 57% /sys/firmware/efi/efivars /dev/nvme1n1p2 930G 599G 327G 65% / tmpfs 16G 0 16G 0% /dev/shm none 1.0M 0 1.0M 0% /run/credentials/systemd-journald.service none 1.0M 0 1.0M 0% /run/credentials/systemd-resolved.service /dev/nvme1n1p2 930G 599G 327G 65% /srv tmpfs 16G 140K 16G 1% /tmp /dev/nvme1n1p2 930G 599G 327G 65% /var/tmp /dev/nvme1n1p2 930G 599G 327G 65% /root /dev/nvme1n1p2 930G 599G 327G 65% /home /dev/nvme1n1p2 930G 599G 327G 65% /var/cache /dev/nvme1n1p2 930G 599G 327G 65% /var/log /dev/nvme1n1p1 2.0G 928M 1.1G 46% /boot tmpfs 3.1G 1.2G 2.0G 38% /run/user/1000 ❮ sudo btrfs fi usage /.snapshots/ Overall: Device size: 929.51GiB Device allocated: 765.50GiB Device unallocated: 164.01GiB Device missing: 0.00B Device slack: 3.00KiB Used: 597.92GiB Free (estimated): 326.24GiB (min: 244.23GiB) Free (statfs, df): 326.23GiB Data ratio: 1.00 Metadata ratio: 2.00 Global reserve: 512.00MiB (used: 0.00B) Multiple profiles: no Data,single: Size:754.01GiB, Used:591.78GiB (78.49%) /dev/nvme1n1p2 754.01GiB Metadata,DUP: Size:5.74GiB, Used:3.07GiB (53.47%) /dev/nvme1n1p2 11.47GiB System,DUP: Size:8.00MiB, Used:112.00KiB (1.37%) /dev/nvme1n1p2 16.00MiB Unallocated: /dev/nvme1n1p2 164.01GiBHere, you dropped this:
/*BTW
ncdu -x /bootOh, I didn’t notice.
$ du -hsc /boot/* 927M /boot/8e894020c9ab48be8cae43e3b9a5598f 300K /boot/amd-ucode.img 820K /boot/EFI 4.0K /boot/limine.conf 4.0K /boot/limine.conf.old 180K /boot/limine-splash.png 4.0K /boot/System Volume Information 928M total $ du -hsc /boot/8e894020c9ab48be8cae43e3b9a5598f/* 12K /boot/8e894020c9ab48be8cae43e3b9a5598f/limine_history 333M /boot/8e894020c9ab48be8cae43e3b9a5598f/linux-cachyos 262M /boot/8e894020c9ab48be8cae43e3b9a5598f/linux-cachyos-lts 333M /boot/8e894020c9ab48be8cae43e3b9a5598f/linux-cachyos-rt-bore 927M totalMy guess is some firmware or modules that just makes it that big and if you want room for snapshots you need to resize (or uninstall some variant if not needed). OS installer might have too small default size for a setup like this.
300MBish for a kernel is totally normal and you have 3 variants installed.