Appears after upgrade from 18.04 to 20.04. Doesn't seem to affect the system but I preferred to use gzip instead of lz4 as for me it doesn't slow the boot (perhaps related to the fact I have nvme) - I've made several tests with both compression methods. But even if it slows a couple seconds I prefer this then priority 0 error. I agree that it either has to be fixed for the LTS versions kernels at least, as if you do not plan to change to the next LTS you will stuck with the current Kernel version, and it make sense in some case as for me some drivers didn't work with other kernel versions. Or the priority has to be lowered that it won't appear as emergency.
-- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1835660 Title: initramfs unpacking failed Status in initramfs-tools package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Bug description: "initramfs unpacking failed: Decoding failed", message appears on boot up. If I "update-initramfs" using gzip instead of lz, then boot up passes without decoding failed message. --- However, we currently believe that the decoding error reported in dmesg is actually harmless and has no impact on usability on the system. Switching from lz4 to gzip compression, simply papers over the warning, without any benefits, and slows down boot. Kernel should be fixed to correctly parse lz4 compressed initrds, or at least lower the warning, to not be user visible as an error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1835660/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
