[ 0.000000] Initramfs unpacking failed: Decoding failed

Bug #1886769 reported by Norbert
This bug report is a duplicate of:  Bug #1835660: initramfs unpacking failed. Edit Remove
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Steps to reproduce:
1. Download MATE Groovy daily (sha256sum = 7d2fdad36b8fcf0409aa0a484755e5fc5ef3798fd256eeebbde905a71ad474b7 )
2. Insert ISO into VirtualBox with EFI enabled
3. Boot VM

Expected results:
* VM boots normally

Actual results:
* VM hangs during early boot with message

      [ 0.000000] Initramfs unpacking failed: Decoding failed

Norbert (nrbrtx)
description: updated
Norbert (nrbrtx)
summary: - [ 0.000000] Initramfs unpacking failed: Deconding failed
+ [ 0.000000] Initramfs unpacking failed: Decoding failed
description: updated
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1886769

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Norbert (nrbrtx) wrote :

@Ubuntu Kernel Bot (ubuntu-kernel-bot)
It is impossible, system hung on boot.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
sudodus (nio-wiklund) wrote :

Do you think this bug is somehow related to the following bug?

https://bugs.launchpad.net/bugs/1886148

For example, are there problems to boot into a live system from a USB drive in a real system, or booted from a virtual hard disk drive with the image in a virtual machine? (I know that it boots in VirtualBox from the iso file when seen as an optical (CD/DVD) drive.)

Revision history for this message
Sai Vinoba (saivinob) wrote :

Tested 20200808 build in Virt-manager. No issues. Does it have to be VirtualBox?

Revision history for this message
Sai Vinoba (saivinob) wrote :

Tested in VirtualBox with 20200810 build. Could see the fault _once_. But when repeated (reboot/shutdown) unable to reproduce.

Revision history for this message
Julian Andres Klode (juliank) wrote :

Removing bootloader tasks, as the kernel has loaded successfully.

no longer affects: grub2 (Ubuntu)
no longer affects: syslinux (Ubuntu)
Norbert (nrbrtx)
tags: added: focal
Revision history for this message
Norbert (nrbrtx) wrote :

Still happens on Ubuntu MATE 20200930 beta iso. Using virtualbox 6.0.24 with EFI.

Revision history for this message
Steve Paynter (ghastlyman) wrote :

Got this bug too.

Steps to reproduce:

1. Download ubuntu-20.04.1-desktop-amd64.iso and verify.
2. Install onto USB stick using Startup Disk Creator.
3. Boot machine from USB stick.

Expected results:
- Machine boots into live Ubuntu.

Actual results:
1. BIOS stuff, as per usual.
2. Grub 2.04 screen, boots "Ubuntu" option by default after a few seconds.
3. Machine hangs with message "[0.XXXXXX] Initramfs unpacking failed: Decoding failed" (where XXXXXX is a different number each time).
   This message is always followed by 5 lines of really tiny text, completely unreadable on my 4k screen.
   Machine now appears to be dead, except that:
   - On one occasion, hitting Enter caused screen to fill with more unreadable tiny text.
   - On another occasion, after a minute of me doing nothing, machine played a short chip tune!

Machine config:
- Lenovo Thinkpad X1 Extreme, Gen 2, one year old.
- UEFI BIOS Version: N2oet47w (1.34), 2020-08-06.
- Firmware is current (as per Lenovo Vantage check, done several days ago).
- My BIOS security settings are maxxed out.

Notes:
- I tried with Secure Boot enabled and disabled; made no difference.
- Machine boots fine into a very recent Ubuntu 20.10 beta, using same laptop and USB stick. (Unfortunately, the ROS software won't work on 20.10 yet.)
- Just repeating: all was fine with Ubuntu 20.10 beta. But fails with 20.04.1.

Revision history for this message
Steve Paynter (ghastlyman) wrote :

Update: Nope, the machine isn't dead at that point:

* Das blinken licht (well hidden) on the USB stick, blinkens for 35 secs.
* The laptop fan starts up.
* A four-note tune plays.

And then nothing.

Revision history for this message
Steve Paynter (ghastlyman) wrote :

Same bug as #1835660?

Revision history for this message
Steve Paynter (ghastlyman) wrote :

Setting BIOS to more-or-less default settings fixed the problem for me. I don't know which one(s) caused the problem.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

It looks like bug 1835660 is close to releasing a fix for this. Maybe use bug 1835660 for now.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.