Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Not enough space allocated to the default boot partition #580

Open
trafotin opened this issue Jul 6, 2024 · 1 comment
Open

Not enough space allocated to the default boot partition #580

trafotin opened this issue Jul 6, 2024 · 1 comment
Labels
bug Something isn't working f40 Related to Fedora 40

Comments

@trafotin
Copy link

trafotin commented Jul 6, 2024

Describe the bug
After enough images are pinned, Silverblue users are presented with a warning that their boot partition is either running low or running out of memory. The boot partition is given 629 MB, both in the case of a 500 GB of SSD and a 1 TB NVMe.

There was speculation if it was because 1024 MB was hinted for the boot partition in the documentation's screenshots for manual partitioning.

The only way to fix the boot partition is to either delete images or resize the boot partition using something like GParted. In my case, I deleted my pinned images. What I did in detail.

To Reproduce
Please describe the steps needed to reproduce the bug:

  1. Pin at least 2 images using ostree
  2. GNOME Disk Usage Analyzer (Baobab) delivers notification that the boot partition is running out of or is out of space.

Expected behavior
At least 1024 MB needs to be allocated to the boot partition. If this is true, does the default behavior of Anaconda need to change?

There might need to tooling to make managing images easier. In the case of uBlue, this could be done through ujust or a GUI tool.

Screenshots
Screenshot from 2024-07-05 23-35-56
Screenshot from 2024-07-03 23-07-12

OS version: Universal Blue Bluefin (Fedora 40 GNOME)

State: idle
AutomaticUpdates: stage; rpm-ostreed-automatic.timer: last run 8h ago
BootedDeployment:
● ostree-image-signed:docker://ghcr.io/ublue-os/bluefin-dx-nvidia:stable
                   Digest: sha256:1ab513c88dea2aacb07c9405bf9e1a0b7400d2788352218e70413063fbb3c66b
                  Version: 40.20240702.0 (2024-07-02T20:02:06Z)
          LayeredPackages: adobe-source-sans-pro-fonts adobe-source-serif-pro-fonts
                           mullvad-vpn pipx
            LocalPackages: veracrypt-1.26.7-1.x86_64

Additional context
Extended discussion from the uBlue forums.

@trafotin trafotin added the bug Something isn't working label Jul 6, 2024
@travier
Copy link
Member

travier commented Jul 8, 2024

As we use a distinct /boot partition, you will be limited in the amount of deployments that you can keep pinned.

If you want to keep more deployments pinned then you need to setup a bigger /boot partition on installation.

There were also discussions around increasing the size of the ESP partition: https://fedoraproject.org/wiki/Changes/BiggerESP

@travier travier added the f40 Related to Fedora 40 label Jul 8, 2024
@travier travier changed the title Not enough memory allocated to the default boot partition Not enough space allocated to the default boot partition Jul 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working f40 Related to Fedora 40
Projects
None yet
Development

No branches or pull requests

2 participants