I see that init/initramfs.c in the kernel tries to unpack our initrd as
rootfs image, which is well, not going to happen, as it is not rootfs
image but early,early2,main(lz4 compat) initramfs.
I wonder if kernel is tripping up on such mixed compression initrd.
However, it still boots fine. So this error is a bit bogus.
Not sure if we should improve how we generate our initrds, or fix kernel
to cope with our initrds which have two early uncompressed ones,
followed by lz4 compatible one.
** Also affects: initramfs-tools (Ubuntu)
Importance: Undecided
Status: New
** Changed in: initramfs-tools (Ubuntu)
Status: New => Confirmed
** Changed in: initramfs-tools (Ubuntu)
Importance: Undecided => High
** Changed in: linux (Ubuntu)
Importance: Undecided => High
--
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 initramfs-tools package in Ubuntu:
Confirmed
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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+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
