This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
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 2129888 - initramfs unpacking failed: uncompression error for certain initrd sizes
Summary: initramfs unpacking failed: uncompression error for certain initrd sizes
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: grub2
Version: 8.0
Hardware: Unspecified
OS: Linux
unspecified
high
Target Milestone: rc
: ---
Assignee: Bootloader engineering team
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks: 2122326
TreeView+ depends on / blocked
 
Reported: 2022-09-26 14:23 UTC by Pavel Cahyna
Modified: 2023-09-16 17:12 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-09-16 17:12:12 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   RHEL-4351 0 None Migrated None 2023-09-16 17:12:06 UTC
Red Hat Issue Tracker RHELPLAN-134910 0 None None None 2022-09-26 14:43:21 UTC

Description Pavel Cahyna 2022-09-26 14:23:12 UTC 
Description of problem:

With a certain size of initrd, the kernel will print 

Initramfs unpacking failed: uncompression error
or
Initramfs unpacking failed: junk in compressed archive

(and then panic as it won't be able to mount the initrd).

I have tried to identify the problematic initrd sizes.
Initrd of 429055538 bytes (and smaller) worked, 429061102 bytes and larger are broken, up to 463840156 bytes. 463841919 bytes and larger work properly again. This was with kernel vmlinuz-4.18.0-424.el8.x86_64. With kernels vmlinuz-5.14.0-162.el9.x86_64 and vmlinuz-5.14.0-70.13.1.el9_0.x86_64 (from RHEL 9) the problem persists, but the boundary between working and non-working initrd sizes shifts a bit.

I am convinced that it is a problem with GRUB and not with the kernel or with the initrd generating tools (gzip, cpio), because installing GRUB from RHEL 7.9 avoids the problem (with the same kernel and initrd that have the problem on RHEL 8).

I can reproduce the problem in RHEL 8.0 and the newest RHEL 8.7, also in RHEL 9.0 and 9.1.

Version-Release number of selected component (if applicable):

1:2.02-66.el8

How reproducible:

Well reproducible with a right initrd size, can be obtained by adding a large file with random data to the initrd.

Steps to Reproduce:
1. dd if=/dev/urandom of=/root/fill bs=1024 count=350000
2. dracut -N --force --include /root/fill /usr/lib/fill /boot/initramfs-4.18.0-425.1.1.el8.x86_64.big.img
3. in GRUB menu, change the boot entry to boot from /boot/initramfs-4.18.0-425.1.1.el8.x86_64.big.img instead of the default /boot/initramfs-4.18.0-425.1.1.el8.x86_64.img

Actual results:
Kernel panic, preceded by the message above

Expected results:
kernel+initrd should boot normally

Additional info:

The problem does not happen when booting with SYSLINUX. I was not able to reproduce it on UEFI machines, only on BIOS machines. I got a panic with sufficiently large initrd on popc64le (PowerVM with OpenFirmware) as well, but the boundary between working and non-working initrd size is different (initrd of size 393955235 was broken, 188900948 worked).
Comment 1 RHEL Program Management 2023-09-16 17:09:41 UTC 
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 2 RHEL Program Management 2023-09-16 17:12:12 UTC 
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.
Note You need to log in before you can comment on or make changes to this bug.