RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1844423 - /boot size 200Mib is not enough
Summary: /boot size 200Mib is not enough
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: anaconda
Version: ---
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: 8.0
Assignee: Vendula Poncova
QA Contact: Release Test Team
Depends On:
TreeView+ depends on / blocked
Reported: 2020-06-05 11:35 UTC by fujiwara
Modified: 2022-11-08 09:36 UTC (History)
7 users (show)

Fixed In Version: anaconda-
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2022-11-08 09:17:10 UTC
Type: Bug
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RTT-4521 0 None None None 2022-05-16 16:44:23 UTC
Red Hat Issue Tracker RTT-4522 0 None None None 2022-05-16 16:44:29 UTC
Red Hat Product Errata RHBA-2022:7462 0 None None None 2022-11-08 09:17:39 UTC

Description fujiwara 2020-06-05 11:35:52 UTC
Since RHEL 8.2, I always get an installation error of:

DNF error: Error in POSTTRANS scriptlet in rpm package kmod-kvdo

Finally I found anaconda recommends the size of /boot partition is 200 Mib or higher but 200 MB is not enough for the partition and the partition usage is 100% and causes above error.

Probably I think the minimum /boot size would be 300MB and the recommendation is 400MB in RHEL 8.y if I think the kernel update later.

Comment 1 Jan Stodola 2020-06-05 19:03:13 UTC
Just some data from a freshly installed RHEL-8.2 x86_64 system and after installing kernel updates:

The content of /boot after installation of the default package set:

[root@localhost ~]# df -h /boot/
Filesystem      Size  Used Avail Use% Mounted on
/dev/vda1      1014M  229M  786M  23% /boot
[root@localhost ~]# ls -l /boot/
total 188216
-rw-------. 1 root root  3909996 Mar 27 15:47 System.map-4.18.0-193.el8.x86_64
-rw-r--r--. 1 root root   187648 Mar 27 15:47 config-4.18.0-193.el8.x86_64
drwxr-xr-x. 3 root root       17 Jun  5 14:36 efi
drwx------. 4 root root       83 Jun  5 14:52 grub2
-rw-------. 1 root root 98311174 Jun  5 14:41 initramfs-0-rescue-bea028befae442a48899ed35436b5a02.img
-rw-------. 1 root root 52726476 Jun  5 14:43 initramfs-4.18.0-193.el8.x86_64.img
-rw-------. 1 root root 19756532 Jun  5 14:49 initramfs-4.18.0-193.el8.x86_64kdump.img
drwxr-xr-x. 3 root root       21 Jun  5 14:39 loader
-rwxr-xr-x. 1 root root  8913760 Jun  5 14:40 vmlinuz-0-rescue-bea028befae442a48899ed35436b5a02
-rwxr-xr-x. 1 root root  8913760 Mar 27 15:48 vmlinuz-4.18.0-193.el8.x86_64
[root@localhost ~]#

After installing 3 kernel updates (3 kernels are kept on the system by default, older kernel versions are removed when installing another kernel update):

[root@localhost ~]# df -h /boot/
Filesystem      Size  Used Avail Use% Mounted on
/dev/vda1      1014M  406M  609M  40% /boot
[root@localhost ~]# ls -l /boot/
total 368900
-rw-------. 1 root root  3963107 May 28 16:29 System.map-4.18.0-208.el8.x86_64
-rw-------. 1 root root  3963107 Jun  2 09:16 System.map-4.18.0-209.el8.x86_64
-rw-------. 1 root root  3965684 Jun  3 14:13 System.map-4.18.0-210.el8.x86_64
-rw-r--r--. 1 root root   188331 May 28 16:29 config-4.18.0-208.el8.x86_64
-rw-r--r--. 1 root root   188402 Jun  2 09:16 config-4.18.0-209.el8.x86_64
-rw-r--r--. 1 root root   188778 Jun  3 14:13 config-4.18.0-210.el8.x86_64
drwxr-xr-x. 3 root root       17 Jun  5 14:36 efi
drwx------. 4 root root       83 Jun  5 14:52 grub2
-rw-------. 1 root root 98311174 Jun  5 14:41 initramfs-0-rescue-bea028befae442a48899ed35436b5a02.img
-rw-------. 1 root root 19756532 Jun  5 14:49 initramfs-4.18.0-193.el8.x86_64kdump.img
-rw-------. 1 root root 50605799 Jun  5 15:29 initramfs-4.18.0-208.el8.x86_64.img
-rw-------. 1 root root 19765921 Jun  5 15:30 initramfs-4.18.0-208.el8.x86_64kdump.img
-rw-------. 1 root root 50604371 Jun  5 15:32 initramfs-4.18.0-209.el8.x86_64.img
-rw-------. 1 root root 19764550 Jun  5 15:32 initramfs-4.18.0-209.el8.x86_64kdump.img
-rw-------. 1 root root 50605813 Jun  5 15:35 initramfs-4.18.0-210.el8.x86_64.img
-rw-------. 1 root root 19765391 Jun  5 15:35 initramfs-4.18.0-210.el8.x86_64kdump.img
drwxr-xr-x. 3 root root       21 Jun  5 14:39 loader
-rwxr-xr-x. 1 root root  8913760 Jun  5 14:40 vmlinuz-0-rescue-bea028befae442a48899ed35436b5a02
-rwxr-xr-x. 1 root root  9052816 May 28 16:29 vmlinuz-4.18.0-208.el8.x86_64
-rwxr-xr-x. 1 root root  9052816 Jun  2 09:17 vmlinuz-4.18.0-209.el8.x86_64
-rwxr-xr-x. 1 root root  9061008 Jun  3 14:14 vmlinuz-4.18.0-210.el8.x86_64
[root@localhost ~]#

Comment 2 Jiri Konecny 2020-06-24 14:51:35 UTC
Javier could you please bring some insights here for why we have 200MB recommendation now and how we should proceed?

Comment 3 Javier Martinez Canillas 2020-07-07 13:18:57 UTC
I'm confused since I see in the Anaconda source code that 200 MiB is for /boot/efi and for /boot is 1GiB. So not sure from where the 200 MiB for /boot is coming from.

Comment 4 Jan Stodola 2020-07-07 13:33:57 UTC
Here is the recommended minimal size defined:

And it's probably from times when 200 MiB was enough...

Comment 5 Jiri Konecny 2020-07-07 16:42:18 UTC
So it should be enough to just adjust the minimal value to avoid having the 200MB size of /boot? If yes, should we use 1G as minimal?

Could you please confirm the above?

Comment 6 fujiwara 2020-07-08 06:03:58 UTC
From my user perspective, I guess /boot 1GiB is too much for virtual hosts? I assign 30GB to a virtual host size and two kernels are enough for me in every update.

Comment 8 Vladimír Slávik 2021-04-21 14:55:40 UTC
The default size of the partition is 1 GiB. The 200 MiB value is for warning the user in GUI. The warning can be dismissed, so the reason why it matters is that people read it and think it's correct. So bumping it to some reasonable value is probably ok. What would the value be?

In the upstream bug, the size is calculated to be a bit more than 300 MiB, so I suggested 512...


Comment 9 Vladimír Slávik 2021-04-23 14:56:16 UTC
Upstream change merged. Let's give it a week and see if anything breaks, backporting this should be 5 minutes, just like upstream.

Comment 11 RHEL Program Management 2021-12-05 07:26:59 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.

Comment 16 Vendula Poncova 2022-05-10 14:01:05 UTC
Fixed in a pull request: https://github.com/rhinstaller/anaconda/pull/4095

Comment 21 Jan Stodola 2022-08-09 12:04:24 UTC
Checked that anaconda- is in nightly compose RHEL-8.7.0-20220809.0

Moving to VERIFIED

Comment 23 errata-xmlrpc 2022-11-08 09:17:10 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (anaconda bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.