Skip to content

fix(205-builder): limit boot generations to 10 to prevent /boot filling up - #48

Draft
phonkd wants to merge 1 commit into
mainfrom
autofix/diskwillfill-205-builder
Draft

fix(205-builder): limit boot generations to 10 to prevent /boot filling up#48
phonkd wants to merge 1 commit into
mainfrom
autofix/diskwillfill-205-builder

Conversation

@phonkd

@phonkd phonkd commented Jul 23, 2026

Copy link
Copy Markdown
Owner

What

A monitoring alert (DiskWillFillIn24h) reported that /boot on 205-builder will fill within 24 hours based on the last 6h of growth.

Root cause

NixOS keeps one kernel+initrd in /boot per generation, and with no configurationLimit set, /boot (a small vfat partition) accumulates unlimited generations.

Fix

Set boot.loader.grub.configurationLimit = 10 so only the 10 most recent generations are kept in /boot. Older kernels are cleaned up automatically during nixos-rebuild.

Verification

  • After deployment, check /boot usage drops as old generations are GC'd
  • nixos-rebuild boot should succeed and ls /boot show at most 10 kernels

…ng up

A monitoring alert (DiskWillFillIn24h) reported that /boot on
205-builder will fill within 24 hours. NixOS keeps one kernel+initrd
per generation in /boot; with no configurationLimit set, the small
vfat partition accumulates unlimited generations.

Set boot.loader.grub.configurationLimit = 10 so only the 10 most
recent generations are kept in /boot.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant