Before moving production services onto a new FCOS install, I wanted to expand the /boot partition based on my upgrade from F42 FCOS being too small (90% usage). I saw the new ‘default’ or recommended size is 2Gb.
I tested a new install and still the default is 350Mb. Trying to define a boot size in ignition has caused so many mount failures, and I still cannot find a working ignition.
Does anyone have a good example for defining a 2Gb boot partition in ignition they know works?
Anyone know why the default is still so small on the F43 FCOS installer?
Hi, As of now, there is no running system. I am trying to go back to my original ignition and still it fails to create a working system.
I thought the requirement would be simple, boot to 2Gb, root to 850 Gb, remainder as a container disk. The only thing I changed was adding info for boot storage, and it all went wrong
I start with a clean disk. After running coreos-installer, before a reboot, it sets boot partition to 384Mb (and a root of only 2.3Gb).
I tried with no storage instruction ..testing in virtual so /dev/vda, but butane is only
As far as I am aware you cannot extend the size of the /boot partition via Ignition, and as I mentioned, it is generally not necessary.
From your latest post I can assume that you were able to successfully provision a running Fedora CoreOS instance with 42% /boot usage. So, could you please try to explain in more detail what exactly you want to achieve so we can try to assist you.
It is possible to increase the /boot partition via Ignition. It is also possible to expand the file system after initial boot. The issue is that the system no longer boots after these operations, at least in my tests in a VM. I will try the workaround described in the latest comment in the issue as it looks promising.
FWIW, shrinking the /boot partition and filesystem works.