[Bug 1835660] Re: initramfs unpacking failed

[Tim Wetzel]

Continues to occur even once the bug 1871268 install crash has been
dealt with (installing from latest daily-live current image). So affects
even a fresh install. Seemed to appear in mid-September updates along
with recurrence of bug 1872159, the dreaded spinning Ubuntu logo hang on
startup. So a fresh install does not resolve it; and the workarounds of
recreating the ram drive image no longer seem to work either.

This issue 1835660, the spinning logo hang 1872159, a problem with the
login password immediately triggering suspend 1897185, and then the
reinstallation crashes 1871268 (which happen when reinstalling to try to
get rid of all this) appeared with the last two Ubuntu updater packages,
since mid-September. The last of these also included an nVidia driver
update, which is believed to affect at least one of these issues.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, 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:
  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