I’m on stable-daily
, and I was not able to apply yesterday’s update this morning, because the bootfs seems full. All updates were working in the previous months. I assume it is somehow related to this change: chore(ci): support combined akmods-kernel-cache in build by bsherman · Pull Request #182 · ublue-os/aurora · GitHub
Note: I did not change the recommended partition layout when installing Aurora from scratch a few months ago. (But I selected manual partitioning, then clicked to create the default recommended layout, and just accepted that - after renaming the btrfs volume.)
Should I somehow have a larger /boot
? Or shouldn’t it have filled up?
Note2: Did not yet have time to retry it or try it with another image.
State: idle
Warning: failed to finalize previous deployment
error: Installing kernel: regfile copy: No space left on device
check `journalctl -b -1 -u ostree-finalize-staged.service`
Deployments:
● ostree-image-signed:docker://ghcr.io/ublue-os/aurora-dx:stable-daily
Digest: sha256:781d39a91bea15441f4ce7bd85359d65bd458316e03f951fad3d567631feb966
Version: 41.20250205.8 (2025-02-05T18:16:11Z)
ostree-image-signed:docker://ghcr.io/ublue-os/aurora-dx:stable-daily
Digest: sha256:ae714eb63ce850983151c89ab77ca243bd07fd7de41467c51a2a56fdfa251734
Version: 41.20250205.3 (2025-02-05T07:18:46Z)
Pinned: yes
ostree-image-signed:docker://ghcr.io/ublue-os/aurora-dx:stable-daily
Digest: sha256:d135686f77be55dfe6fad6dd277d4e32e53ca749fe144bc11efebd0bed0cb90c
Version: 41.20250113.6 (2025-01-13T07:23:23Z)
Pinned: yes
ostree-image-signed:docker://ghcr.io/ublue-os/aurora-dx:stable-daily
Digest: sha256:c31b9ddf427fdb7f14561e1d66e409749e4f29e40dd9712a53ee524bdd8e5db7
Version: 41.20250105.1 (2025-01-05T19:24:15Z)
LayeredPackages: brave-browser
Pinned: yes
ostree-image-signed:docker://ghcr.io/ublue-os/aurora-dx:stable-daily
Digest: sha256:919dc0378dbc59ade5f1a9e9af5889ce81c8ace0193429293686db97408fc709
Version: 41.20250109 (2025-01-09T06:07:09Z)
Pinned: yes
ostree-image-signed:docker://ghcr.io/ublue-os/aurora-dx:stable-daily
Digest: sha256:66e734492af55b17deb6172d7de8e63543f812ab0baa766ed3d70fa9c86a4380
Version: 41.20241220 (2024-12-20T06:10:08Z)
LayeredPackages: brave-browser
Pinned: yes
❯ journalctl -b -1 -u ostree-finalize-staged.service
Feb 06 08:46:36 hostname systemd[1]: Finished ostree-finalize-staged.service - OSTree Finalize Staged Deployment.
Feb 06 08:50:06 hostname systemd[1]: Stopping ostree-finalize-staged.service - OSTree Finalize Staged Deployment...
Feb 06 08:50:07 hostname ostree[9004]: Finalizing staged deployment
Feb 06 08:50:08 hostname ostree[9004]: Copying /etc changes: 30 modified, 6 removed, 150 added
Feb 06 08:50:08 hostname ostree[9004]: Copying /etc changes: 30 modified, 6 removed, 150 added
Feb 06 08:50:08 hostname ostree[9004]: Refreshing SELinux policy
Feb 06 08:50:11 hostname ostree[9004]: Refreshed SELinux policy in 2664 ms
Feb 06 08:50:11 hostname ostree[9004]: Finalized deployment
Feb 06 08:50:11 hostname ostree[9004]: bootfs requires additional space: 167.8 MB
Feb 06 08:50:11 hostname ostree[9004]: Size to prune from bootfs: 0 bytes
Feb 06 08:50:11 hostname ostree[9004]: Disabling auto-prune optimization; insufficient space left in bootfs
Feb 06 08:50:12 hostname ostree[9004]: error: Installing kernel: regfile copy: No space left on device
Feb 06 08:50:12 hostname systemd[1]: ostree-finalize-staged.service: Control process exited, code=exited, status=1/FAILURE
Feb 06 08:50:12 hostname systemd[1]: ostree-finalize-staged.service: Failed with result 'exit-code'.
Feb 06 08:50:12 hostname systemd[1]: Stopped ostree-finalize-staged.service - OSTree Finalize Staged Deployment.
Feb 06 08:50:12 hostname systemd[1]: ostree-finalize-staged.service: Consumed 3.982s CPU time, 112.8M memory peak.
❯ df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/dm-0 248378368 71151384 173891192 30% /sysroot
devtmpfs 4096 0 4096 0% /dev
tmpfs 3999320 84 3999236 1% /dev/shm
efivarfs 100 67 29 71% /sys/firmware/efi/efivars
tmpfs 1599732 2248 1597484 1% /run
tmpfs 1024 0 1024 0% /run/credentials/systemd-cryptsetup@luks\xyz\xyz\xyz\xyz\xyz.service
tmpfs 1024 0 1024 0% /run/credentials/systemd-journald.service
tmpfs 1024 0 1024 0% /run/credentials/systemd-udev-load-credentials.service
tmpfs 1024 0 1024 0% /run/credentials/systemd-network-generator.service
tmpfs 1024 0 1024 0% /run/credentials/systemd-tmpfiles-setup-dev-early.service
tmpfs 1024 0 1024 0% /run/credentials/systemd-sysctl.service
tmpfs 1024 0 1024 0% /run/credentials/systemd-tmpfiles-setup-dev.service
/dev/dm-0 248378368 71151384 173891192 30% /var
/dev/dm-0 248378368 71151384 173891192 30% /var/home
overlay 248378368 71151384 173891192 30% /usr/share/sddm/themes
tmpfs 3999324 4 3999320 1% /tmp
/dev/sda2 996780 976516 0 100% /boot
/dev/sda1 613160 12856 600304 3% /boot/efi
tmpfs 1024 0 1024 0% /run/credentials/systemd-vconsole-setup.service
tmpfs 1024 0 1024 0% /run/credentials/systemd-tmpfiles-setup.service
tmpfs 1024 0 1024 0% /run/credentials/systemd-resolved.service
tmpfs 799864 104376 695488 14% /run/user/1000
Do you have any suggestions how I could fix this most easily?
Thanks!