Has this to do with BLK_DEV_RAM being compiled as a module? From
init/initramfs.c:
> if (IS_ENABLED(CONFIG_BLK_DEV_RAM))
> printk(KERN_INFO "Trying to unpack rootfs image as
> initramfs...\n");
> else
> printk(KERN_INFO "Unpacking initramfs...\n");
> err = unpack_to_rootfs((char *)initrd_start, initrd_end -
> initrd_start);
> if (err) {
>#ifdef CONFIG_BLK_DEV_RAM
> populate_initrd_image(err);
>#else
> printk(KERN_EMERG "Initramfs unpacking failed: %s\n", err);
>#endif
So the IS_ENABLED line is true while the ifdef CONFIG_BLK_DEV_RAM line
seems to evaluate to false.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1835660
Title:
initramfs unpacking failed
Status in OEM Priority Project:
New
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/oem-priority/+bug/1835660/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
