I've discovered that this behavior can also occur with the installer
(similar to bug 1900130) when the USB stick to which the installer ISO
was written is bad. (In this case, the error message is saying exactly
what it should be saying.)
--
You received this bug notification because you are a me
** Changed in: oem-priority
Status: New => Fix Released
--
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 OEM Priority Project:
** Tags removed: eoan
--
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 OEM Priority Project:
New
Status in grub2 package in Ubuntu:
@superm1 yes I have, it is now pulled into v5.14
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=2c484419efc09e7234c667aa72698cb79ba8d8ed
I will request it to be included in linux-stable series.
Note that in Impish we have now switched to zstd compression for the
ini
#134: @xnox, have you re-sent it? It looks like
https://lkml.org/lkml/2021/1/14/1091 got no feedback.
--
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 f
** Changed in: initramfs-tools (Ubuntu Focal)
Assignee: Armandoobnaiala (armando1986) => (unassigned)
--
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 unpacki
Works well, thank you for the update.
On Fri, Mar 26, 2021, 7:31 AM Armandoobnaiala <1835...@bugs.launchpad.net>
wrote:
> update-initramfs: Generating /boot/initrd.img-5.8.0-45-generic
> /usr/sbin/mkinitramfs: 177: COMPRESS: parameter not set
> update-initramfs: failed for /boot/initrd.img-5.8.0
update-initramfs: Generating /boot/initrd.img-5.8.0-45-generic
/usr/sbin/mkinitramfs: 177: COMPRESS: parameter not set
update-initramfs: failed for /boot/initrd.img-5.8.0-45-generic with 2.
** Changed in: initramfs-tools (Ubuntu Focal)
Assignee: (unassigned) => Armandoobnaiala (armando1986)
# An empty value - compcache isn't used, or added to the initramfs at all.
# An integer and K (e.g. 65536 K) - use a number of kilobytes.
# An integer and M (e.g. 256 M) - use a number of megabytes.
# An integer and G (e.g. 1 G) - use a number of gigabytes.
# An integer and % (e.g. 50 %) - use a pe
@Fred eldmannen+launchpad
This issue is only fixed in the Ubuntu patchset for the Linux Kernel.
Although I have submitted this fix upstream, it has not been picked up
yet by kernel.org vanilla kernels. See
https://lkml.org/lkml/2021/1/14/1091
The mainline builds you point to, do not contain Ubunt
I have this issue on Hirsuite.
Is this only fixed in 5.8 and 5.10 but not 5.11?
$ uname -a
Linux example 5.11.8-051108-generic #202103200636 SMP Sat Mar 20 11:17:32 UTC
2021 x86_64 x86_64 x86_64 GNU/Linux
I got the 5.11.8 kernel from
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.11.8/
becau
This bug was fixed in the package linux - 5.10.0-14.15
---
linux (5.10.0-14.15) hirsute; urgency=medium
* hirsute/linux: 5.10.0-14.15 -proposed tracker (LP: #1913724)
* Restore palm ejection on multi-input devices (LP: #1913520)
- HID: multitouch: Apply MT_QUIRK_CONFIDENCE qu
This bug was fixed in the package linux - 5.4.0-65.73
---
linux (5.4.0-65.73) focal; urgency=medium
* focal/linux: 5.4.0-65.73 -proposed tracker (LP: #1912220)
* initramfs unpacking failed (LP: #1835660)
- SAUCE: lib/decompress_unlz4.c: correctly handle zero-padding around
i
This bug was fixed in the package linux - 5.8.0-41.46
---
linux (5.8.0-41.46) groovy; urgency=medium
* groovy/linux: 5.8.0-41.46 -proposed tracker (LP: #1912219)
* Groovy update: upstream stable patchset 2020-12-17 (LP: #1908555) // nvme
drive fails after some time (LP: #1910
$ sudo qemu-system-x86_64 -kernel ./vmlinuz-5.8.0-41-generic -initrd
./initrd-pad4-5.8.0-41-generic -append 'break=top quiet console=ttyS0'
-m 2G -nographic -no-reboot
Spawning shell within the initramfs
BusyBox v1.30.1 (Ubuntu 1:1.30.1-4ubuntu6.3) built-in shell (ash)
Enter 'help' for a list of
Verifying v5.8 build
$ sudo qemu-system-x86_64 -kernel ./vmlinuz-5.8.0-41-generic -initrd
./initrd-pad4-5.8.0-41-generic -append 'break=top quiet console=ttyS0'
-m 2G -nograt
Spawning shell within the initramfs
BusyBox v1.30.1 (Ubuntu 1:1.30.1-4ubuntu6.3) built-in shell (ash)
Enter 'help' for a
1) checking that reproducer still fails
sudo qemu-system-x86_64 -kernel ./vmlinuz-5.4.0-64-generic -initrd
./initrd-pad4-5.4.0-64-generic -append 'break=top quiet console=ttyS0'
-m 2G -nograt
[3.581106] Initramfs unpacking failed: Decoding failed
Spawning shell within the initramfs
BusyBox
@vmc
this bugfix is not yet available on any .iso for any series yet. It can
only be tested from installed systems and enabling proposed.
--
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/183
This bug is still failing per current ISO dated 01/25/2021 booting from
Kubuntu 21.04:
$ sudo dmesg|grep failed
[0.538632] Initramfs unpacking failed: Decoding failed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
ht
The corrected ISO date is this:
hirsute-desktop-amd64.iso 2021-01-26 05:51
from Kubuntu daily-live current. It still fails.
--
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
Tit
This bug failure is still present as of current ISO dated 01/25/2021 using
Kubuntu:
[code]vmc@01-25-21:~$ sudo dmesg|grep failed
[0.538632] Initramfs unpacking failed: Decoding failed[/code]
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribe
@vmclarck, @xnox, or anyone who has been dealing with this bug - may you
please verify if the kernel in -proposed resolves the problem for you in
Focal and/or Groovy? Instructions are listed in comment #120
Thank you!
--
You received this bug notification because you are a member of Kernel
Packa
Fix this bug with a patch, please have a try.
** Patch added: "Fix padding parse error"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1835660/+attachment/5455378/+files/0001-initramfs-fix-Decoding-failed.patch
--
You received this bug notification because you are a member of Kernel
Pa
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
groovy' to 'verification-done-groovy'. If the problem still exists,
change the tag 'verifica
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag 'verificati
I have successfully resolved the problem. I don't know exactly what
helped because I did a few things. Namely: I switched all SATA cables
from the second controller to the first (my computer motherboard has two
SATA controllers) and disabled the Compatibility Support Module.
Unfortunately, CSM turn
The same thing happened when I try Ubuntu 20.10 live server... Let me
check the 18.04 server. I currently use Ubuntu Desktop 18.04 on my
laptop, maybe the server edition will work.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in U
Hi
I have this issue when I try to boot USB installation pendrive with Ubuntu
20.04.1 live server made from ISO available from the official webpage.
I downloaded ISO two times, I sha256 its content and compared to value stored
in the SHA256SUMS file.
I want to install Ubuntu on my PC next to Wind
** Changed in: linux (Ubuntu Groovy)
Status: Confirmed => Fix Committed
** Changed in: linux (Ubuntu Focal)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.lau
** Also affects: grub2 (Ubuntu Groovy)
Importance: Undecided
Status: New
** Also affects: initramfs-tools (Ubuntu Groovy)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Groovy)
Importance: Undecided
Status: New
** Also affects: grub2 (Ubuntu Hirsut
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
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 OEM Priority Proj
I struggled with the same issue on a fresh Kubuntu 20.04 installation
(Lenovo Thinkpad P52s).
>From the Grub / Advanced options / Recovery mode / root terminal I was
able to remount the / as rw (rather than ro)
Changing 'lz4' to 'gzip' as per
https://forums.linuxmint.com/viewtopic.php?f=46&t=323
** Description changed:
"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 dmes
so what grub is doing is correct.
It pads/aligns every initrd by 4, which is fine, and as per spec.
https://www.kernel.org/doc/html/latest/driver-api/early-userspace
/buffer-format.html
initramfs size can be filled with arbitrary amount of "\0" all the way
upto initramfs_size.
"In human terms,
** Changed in: grub2 (Ubuntu)
Status: Triaged => Invalid
** Changed in: linux (Ubuntu)
Status: Invalid => Triaged
--
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
Titl
@twetzel21 this is not related to those changes at all.
--
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 OEM Priority Project:
New
St
Dimitri, I note your comment #106 about secureboot patches upstream. If
I recall correctly, a linux security update came down through Ubuntu
Updater about the same time or just prior to the LTS 20.04.1 updates in
mid September. A number of issues with LTS 20.04.1 appeared following
two "batches" of
NAK on the linux patch.
I think this is a grub bug.
When loading multiple initrds, grub aligns_up each one of them at 4bytes
boundary, and allocates pages for that. And it declares and passes
ramdisk_image as the total allocated memory. Rather than the true size
of the initrds.
** Changed in: gr
As discussed at https://github.com/lz4/lz4/issues/956 I really think it
is grub2 secureboot patches linuxefi bug. WIP thing is here
https://github.com/rhboot/grub2/pull/77/files
** Bug watch added: github.com/lz4/lz4/issues #956
https://github.com/lz4/lz4/issues/956
** Changed in: grub2 (Ubunt
The attachment "[PATCH] unlz4: Handle 0-size chunks, discard trailing
padding/garbage" seems to be a patch. If it isn't, please remove the
"patch" flag from the attachment, remove the "patch" tag, and if you are
a member of the ~ubuntu-reviewers, unsubscribe the team.
[This is an automated messag
** Also affects: grub2 (Ubuntu)
Importance: Undecided
Status: New
--
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 OEM Priori
So lz4 compressed initrd looks like this with hexdump
568f580 0523 00ac 54bf 4152 4c49 5245 2121 0021
568f590 0001 1cff 0050
568f59a
I do wonder what ram is initialized too, and how those things look when
kernel reads initrd from memory as loaded by the bootloader / qemu.
@Siarhei
That looks very valid. And we were close to getting to that, when apw &
I timed out looking at this.
lz4 -l Use Legacy format (typically for Linux Kernel compression)
Note : -l is not compatible with -m (--multiple) nor -r
Which must always be used when creating initrd
Also i guess we (i) need to retest if
https://github.com/lz4/lz4/releases/tag/v1.9.3 fixes all the things =/
--
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 unpac
** Tags added: patch
--
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 OEM Priority Project:
New
Status in initramfs-tools package in
The patch had also been posted to LKML:
https://lkml.org/lkml/2020/11/16/1438
--
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 OEM Pri
Please take a look at the following patch as it might be relevant to the
issue at hand.
** Patch added: "[PATCH] unlz4: Handle 0-size chunks, discard trailing
padding/garbage"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1835660/+attachment/5434929/+files/0001-unlz4-Handle-0-size-chu
Dziękuję za zainteresowanie. Aktualnie mój HP 8760 nie działa, więc
jak dla mnie problem z Ubuntu 20.04 stał się nieistotny.
Jeszcze raz dziękuję i pozdrawiam ekipę Ubuntu.
Tomek P.
2020-11-06 12:18 GMT+01:00, archi02 <1835...@bugs.launchpad.net>:
> Same issue here and no workaround works : neithe
Same issue here and no workaround works : neither switching from lz4 to
gzip nor keeping lz4 and only update initramfs. I also tried to launch
with another kernel, without success.
The computer is now blocked (Xubuntu 20.04, fresh install). I really
don't want to reinstall 18.04.
What can I do ?
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");
>
The fix for 1872159 (spinning logo hang on startup) has allowed me to
turn the splash screen back on; and this error is not visible. I do,
though, encourage completion of the fix for it since it rears its head
when the splash screens have to be disabled.
--
You received this bug notification beca
I'm having this error too.
--
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 OEM Priority Project:
New
Status in initramfs-tools packa
** Tags added: fr-79
--
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 OEM Priority Project:
New
Status in initramfs-tools package in
** Tags added: oem-priority originate-from-1896145 sutton
** Changed in: oem-priority
Importance: Undecided => Low
--
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:
initr
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 f
Still happening on 2020-10-01 (since at least 2019-10-01) on multiple
computers.
Quoting what bug description says:
"Kernel should be fixed to correctly parse lz4 compressed initrds, or at
least lower the warning, to not be user visible as an error."
--
You received this bug notification becaus
Just installed a new system and the bug is still there, leading me straight
back to this bug report for the 'fix'.
I was really hoping that this bug would have been addressed in 20.04.1.
Not sure why no one from the dev team is picking this up to rectify it.
--
You received this bug notification
Applied the 'fix' from Comment #11 by vmc(vmclark) in Linux Mint 20. The
error is no longer logged. Some boots on my HP laptop with a 5400RPM
spinning Hard drive are slow but some are faster but some around the
same time with lz4. Hard disk performance on my laptop is better with
gzip than lz4. Wit
i get this right away when i try to do a fresh install :
initramfs unpacking failed: Decoding failed
--
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 fa
This error is still happening and it is critical error which does not
allow me to start Ubuntu !
Distributor ID: Ubuntu
Description:Ubuntu 20.04.1 LTS
Release:20.04
Codename: focal
--
You received this bug notification because you are a member of Kernel
Packages, which is subsc
Ubuntu put it at lz4 by default, so my gut tells me that'll give the
fastest boot time. I didn't change lz4 to anything, just ran this
command to get rid of the error:
sudo update-initramfs -c -k $(uname -r)
I believe you have to run this command everytime certain packages are
updated.
Runnn
Been seeing this since new install of Linux Mint 20 (2 weeks ago)
(Have not noticed on a LM19.3 upgrade on a different machine)
I have been finding several small bugs and wondered if this may have
something to do with any of them.
I just tried the above fix.
I no longer see the error on boot up,
This is a simplified version of the means to work around this problem:
Step 1:
sudo sed -i 's/COMPRESS=lz4/COMPRESS=gzip/g' /etc/initramfs-tools/initramfs.conf
Step 2:
sudo update-initramfs -u
Step 3:
Reboot.
Now I wonder whether someone has already tried something other than gzip?
Because ini
I'm watching this error since about 10 months hoping that this would be fixed
before the 20.04 release.
Now we're almost 4 months past the release date and it's still there.
Given that the fix is quite easy, I'm wondering why this is still an unresolved
issue.
--
You received this bug notificat
I recall that on one of my machines I had exactly the same situation as
reported in #20 and #21 up to the timings (5.3.0-26-generic in Ubuntu
19.10 with EFI Secure Boot and dual boot with Windows 10,
fastboot/hibernation disabled, LZ4 image by default, booting failed
often, booting succeeded upon r
Confirmed on Linux 5.4.0-42-generic with Linux Mint 20 (Ubuntu 20.04)
clean install.
Changing lz4 to gzip in /etc/initramfs-tools/initramfs.conf removed the
error (after doing sudo update-initramfs -u)
--
You received this bug notification because you are a member of Kernel
Packages, which is su
Is part of the issue here that some (most) initramfs-tools created
images have an uncompressed early CPU microcode firmware prefixed ?
That is stored as ASCII CPIO which is why Con see's that reported by
'file' since that tool checks the magic signatures at start of a file.
binwalk reveals more d
Ubuntu 20.04
for me the problem started after upgrading to the kernel version
5.4.0-42-generic,
I noticed it because the boot up failed once.
--
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
Hi, I had this same issue while updating ubuntu 20, however, I have
noticed that kernal hung error while the update stalled.
So I have added the following in /etc/sysctl.conf and rebooted the
server, this issue has gone(we can apply those parameter without
restarting server usings sysctl -w vm.di
I think "file" is wrong. (I have the same kind of misleading output :
"ASCII cpio archive ..." )
You can try to you use "unmkinitramfs" on your inird.img (unfortunately "cpio"
does not work to fully "unarchive" this kind of "multi-segments" archive) and
check the size.
I have "lz4" initrd.img fi
The issue appears to be that update-initramfs creates uncompressed
images.
I have the same error but have been dealing with a different issue of it
failing to boot with a custom kernel by UUID which is why I haven't
posted a bug report. However, since this issue appears to be related,
upon further
All LXD virtual machines are hitting this too.
Run:
- lxc launch images:ubuntu/focal/cloud f1 && lxc console f1
And you'll see it show that message. As mentioned above, boot then still
goes ahead and you get a login prompt, but as that may not always be the
case.
For example in linux-kvm, that
Given that the change to the compression format is one of the headline
features of Ubuntu 20, and that Ubuntu 20 is a LTS release (and thus,
for one thing, a release upon which other Linux distributions are based)
I am surprised that this problem made it into the final release.
--
You received th
Same thing here. In my case, the computer keeps booting into emergency mode,
with output like in #5, and some additional ACPI errors.
I changed COMPRESS to gzip as described in #47, but not back to lz4.
Now the computer keeps booting into emergency mode with the message "/dev/sda2
clean" (which i
Can confirm
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1835660/comments/26
What I did was I changed
`COMPRESS=lz4` to `COMPRESS=gzip` in `/etc/initramfs-tools/initramfs.conf`, then
`sudo update-initramfs -u`
After, without a reboot I've changed `COMPRESS` back to `lz4`, and then
`sudo
I was dealing with some of these issues after install new kernel version this
morning. However I was able to boot with older kernel versions. After a lot of
test, now I am able to boot in the new kernel without any problem.
Here there are some checks and tasks that I could accomplish:
-) Check i
This is the error that I get on boot up after a software update this
morning:
[ 0478394 ] Initramfs unpacking failed: Decoding failed
[1356011] atas.00: failed to set xfermode (err mask=0x40) /dev/sda3: clean,
205993/1831424 files, 2350143/7324160 blocks You are in emergency mode. After
lo
This is a blocking issue for me as well. Rolling back to 18.04 LTS.
--
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 pa
Correction for my last post: More investigation revealed that the issue
IS harmless after all - the error message just happened to be the only
message printed on an otherwise black and unresponsive screen for
multiple seconds before a timeout occurs that after further research
turned out to be caus
I did a clean install of 20.04 on my machine (which has been running
Ubuntu, most recently 19.04, without issue so far) and I am facing this
- importantly in my case it is NOT a harmless message but actually
preventing boot - I am stuck in the initramfs prompt.
I tried the suggested workaround of
Confirmed on 20.04 vmlinuz-5.4.0-31-generic
[0.691523] Trying to unpack rootfs image as initramfs...
[0.850467] Initramfs unpacking failed: Decoding failed
[0.864022] Freeing initrd memory: 83456K
--
You received this bug notification because you are a member of Kernel
Packages, whic
Confirmed also on a clean 20.04, kernel 5.4.0-31-generic
The time difference between gzip and lz4 is not noticeable by the user:
LZ4:
Startup finished in 14.815s (firmware) + 3.483s (loader) + 1.879s (kernel) +
23.176s (userspace) = 43.354s
graphical.target reached after 23.164s in userspace
GZ
Same problem here in Ubuntu (Focal) no matter the kernelversion, even with
custom compiled kernels (wich is what I use)
The problem was however easy fixed, as per earlier description, with changing
compression by editing /etc/initramfs-tools/initramfs.conf to use gzip and then
do "sudo update-in
Running 20.04 here, and I've also noticed the same message. Maybe a
useful data point: I only see this on UEFI machines, my traditional BIOS
machines seem unaffected. Could it be something related to GRUB on UEFI?
--
You received this bug notification because you are a member of Kernel
Packages,
8
--
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:
Co
@vmc, I've noticed the same with nvme, or at least not slower. It slowed
after the last update for 20.04 and updating the kernel to 5.40.0-29
however. it was almost 5 seconds faster with version -28
--
You received this bug notification because you are a member of Kernel
Packages, which is subscr
Ye, I tried X,K,U,b ubuntu, and all boot without errors. I also prefer
gzip. I had the reverse though. I find gzip is faster than lz4, and I'm
using nvme for boot.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bu
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 prefe
regarding #58 - ignore the last line. That's a copy-paste fail on my
part. Sorry.
--
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 init
I've been experiencing this for several months now (not exactly sure
when it started). For me, the error leads to a hard stop and the option
to Ctrl-D to continue or ENTER for maintenance.
I followed the process from #47 (Saroumane wrote on 2020-04-06:)
Adding COMPRESS=gzip to /etc/initramfs-tool
>From the time i upgraded from 19.10 to 20.04 on 24th April, this didn't
came at first, during the boot just after upgrade, even now this error
randomly appears not every-time, but i can confirm its there with Ubuntu
20.04 too
--
You received this bug notification because you are a member of Kern
USB 2.0 flash drive install of ubuntu-20.04-desktop-amd64.iso
UNetbootin 677-1~bionic1
AMD Athlon II X4 640
ASRock N68-S
The first time that I ran the USB install, the live version of Ubuntu
20.04 succeeded in booting without issue. Now each and every time I
attempt to boot the live USB, I get th
** Tags added: id-5e861a6d29650f3423a935c0
--
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:
Invali
As stated, this is believed to not be a bug in initramfs-tools, only in
the kernel for displaying a spurious message. Hence the 'linux' bug
task is confirmed.
** Changed in: initramfs-tools (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a memb
> I am having the same trouble, but during INSTALLATION, I already
installed Ubuntu 20.04 twice and I haven't access to it yet.
That is not this bug.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.
I’ve had the same problem during installation Ubuntu 20.04 Beta and last
daily release.
I’m not sure if it’s necessary but my PC spec is Intel i9
9900k/RTX2080Ti.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https:/
I am having the same trouble, but during INSTALLATION, I already
installed Ubuntu 20.04 twice and I haven't access to it yet. The first
time I got black screen (with safe graphics installation) then normal
installation didn't let me to install, and I try to reinstall with safe
graphics again. I got
This happened for me yesterday, when booting the main Ubuntu 20.04 beta
x86_64 iso on real hardware (not a virtual machine). It has a graphical
splash screen but in the upper left corner I get this "console" message.
Then eventually in a few seconds, after it has fully booted, that splash
screen i
In post#14, I showed how my gzip booted faster.
"We currently believe that the decoding error reported in dmesg is
actually harmless and has no impact on usability on the system."
If 'harmless', then why the error in the first place? Something is
causing it. Sticking the error in the sand is NOT
For me its happening the same, if lz4 is activated get this initramfs
unpacking failed: Decoding failed at first line of boot, if switch to
gzip the error is gone, switching back to lz4 make the initramfs
unpacking failed: Decoding failed back again at boot, staying at gzip
for the time being.
Als
1 - 100 of 147 matches
Mail list logo
