Since the end of last week I have been getting the message that the boot partition is almost full. I was able to fix the whole thing by dropping of:
rpm-ostree cleanup --rollback
The next time I updated I got the message again.
My boot partition looks like this:
/dev/sda1 588M 266M 280M 49% /boot where it was almost full before I ran the command.
I’ve never had this problem before.
What can I do?
Did you happen to have older image deployments pinned? those will eat up the boot partition if you keep multiple old images pinned
No, I don’t think so. Here is my status output:
rpm-ostree status
State: idle
AutomaticUpdates: stage; rpm-ostreed-automatic.timer: last run 7min ago
Deployments:
ostree-image-signed:docker://ghcr.io/ublue-os/bluefin-nvidia:latest
Digest: sha256:5a62c105b74182ec90120e1260b6fde6909d8d31d810d5ffbe9e8eac4debd8e0
Version: 41.20241106.0 (2024-11-06T04:44:45Z)
Diff: 10 upgraded
LayeredPackages: gnome-themes-extra jre kitty mangohud sassc setserial virt-manager
LocalPackages: brscan-skey-0.3.2-0.x86_64 brscan5-1.3.5-0.x86_64 mfcl3740cdwpdrv-3.5.1-1.i386
● ostree-image-signed:docker://ghcr.io/ublue-os/bluefin-nvidia:latest
Digest: sha256:84b88d9a3b51ac750658bc585b8505df7610606fc9d4bee9fb9c8718d466e5a2
Version: 41.20241105.0 (2024-11-05T15:26:49Z)
LayeredPackages: gnome-themes-extra jre kitty mangohud sassc setserial virt-manager
LocalPackages: brscan-skey-0.3.2-0.x86_64 brscan5-1.3.5-0.x86_64 mfcl3740cdwpdrv-3.5.1-1.i386
It looks like some files are in /boot directory. Did you make custom partitioning and set “/boot” to be too small?
Also, can you please post output of commands:
lsblk
df -lh /boot
tree /boot
No, not actually. I just let the installer do it.
❯ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
sda 8:0 0 931,5G 0 disk
├─sda1 8:1 0 614,4M 0 part /boot
├─sda2 8:2 0 83,4G 0 part /var
│ /sysroot/ostree/deploy/default/var
│ /usr
│ /etc
│ /
│ /sysroot
└─sda3 8:3 0 847,5G 0 part /var/home
❯ df -lh /boot
Dateisystem Größe Benutzt Verf. Verw% Eingehängt auf
/dev/sda1 588M 266M 280M 49% /boot
❯ tree /boot
/boot
├── boot → .
├── grub2 [error opening dir]
├── loader → loader.1
├── loader.1
│ ├── entries
│ │ └── ostree-1.conf
│ └── grub.cfg
├── lost+found [error opening dir]
└── ostree
└── default-0f9cfc2995621c65a9328844b5a124d75ca60e003000be05a622238fe781c8fc
├── initramfs-6.11.5-300.fc41.x86_64.img
└── vmlinuz-6.11.5-300.fc41.x86_64
What I have now seen is that there are a lot of ‘mod’ files in grub2. And then there is also the locale folder with ‘mo’ files.
I have 1 GB size of /boot in your case is only 588 MB.
Can you also please check the biggest files in /boot directory:
sudo du -S /boot | sort -n -r | head
in my case there is the following:
159016 /boot/ostree/default-d8af1948dd0c51a45edec20b4e28a37eea21e753a865320ffa16de26beeff683
4640 /boot/grub2/locale
3376 /boot/grub2/i386-pc
2344 /boot/grub2/fonts
16 /boot/lost+found
16 /boot/loader.1
12 /boot/loader.1/entries
12 /boot/grub2
8 /boot/ostree/initramfs-overlays
4 /boot/ostree
‘mo’ files are translation files for various world languages. They are small like 5 MB in total size and should not produce the disk storage problem.
Finally …
❯ sudo du -S /boot | sort -n -r | head
[sudo] Passwort für svnskr:
261172 /boot/ostree/default-b02dbd56460269206f9b81ef2309835187f903f24e49533ce80e7d1cc0638672
261168 /boot/ostree/default-0f9cfc2995621c65a9328844b5a124d75ca60e003000be05a622238fe781c8fc
4640 /boot/grub2/locale
3380 /boot/grub2/i386-pc
2344 /boot/grub2/fonts
16 /boot/lost+found
16 /boot/loader.0
12 /boot/loader.0/entries
12 /boot/grub2
4 /boot/ostree
again I’ve only 25 megs left.
On my laptop I also got only 580MB space.
Dumb question. Are using BIOS or CSM?
You don’t seem to have a EFI system partition and boot is half the size it should be.
As I mentioned before, I just let the installer do its thing. That’s probably why it only reserved 600MB for the boot partition.
I use Bios. I have never dealt with Uefi. I also don’t know why I should change that.
Maybe it’s because I used an older ISO. I will download a newer ISO and use it to set up the system again. Let’s see if the boot partion is bigger then.
By the way, it has only been complaining about running out of space since last week. The problem didn’t exist before. 
You should put your BIOS to Uefi mode too
I had a similar issue previously and wouldn’t keep updates because I was out of space with multiple images. I grew my partition and shrunk another slightly. I like to keep a couple of pinned images so I expanded mine to a little over 1GB. You can just download gparted, put on a USB stick and boot from that to resize. Solved my issues.
u can do this do this even though i have had the same install for about 3 months now?
I did a new install, ‘cause I couldn’t increase boot partition with gparted. Thx everyone for their help.