[Touch-packages] [Bug 1835660] Re: initramfs unpacking failed

2020-12-02 Thread Dimitri John Ledkov
** 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

[Touch-packages] [Bug 1835660] Re: initramfs unpacking failed

2020-11-30 Thread Dimitri John Ledkov
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,

[Touch-packages] [Bug 1835660] Re: initramfs unpacking failed

2020-11-30 Thread Dimitri John Ledkov
** 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 Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.

[Touch-packages] [Bug 1835660] Re: initramfs unpacking failed

2020-11-30 Thread Dimitri John Ledkov
@twetzel21 this is not related to those changes at all. -- 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

[Touch-packages] [Bug 1835660] Re: initramfs unpacking failed

2020-11-30 Thread Tim Wetzel
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"

[Touch-packages] [Bug 1835660] Re: initramfs unpacking failed

2020-11-26 Thread Dimitri John Ledkov
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

[Touch-packages] [Bug 1835660] Re: initramfs unpacking failed

2020-11-26 Thread Dimitri John Ledkov
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:

[Touch-packages] [Bug 1835660] Re: initramfs unpacking failed

2020-11-26 Thread Ubuntu Foundations Team Bug Bot
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

[Touch-packages] [Bug 1835660] Re: initramfs unpacking failed

2020-11-26 Thread Dimitri John Ledkov
** Also affects: grub2 (Ubuntu) Importance: Undecided Status: New -- 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

[Touch-packages] [Bug 1835660] Re: initramfs unpacking failed

2020-11-25 Thread Dimitri John Ledkov
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 /

[Touch-packages] [Bug 1835660] Re: initramfs unpacking failed

2020-11-17 Thread Dimitri John Ledkov
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 Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1835660

[Touch-packages] [Bug 1835660] Re: initramfs unpacking failed

2020-11-17 Thread Dimitri John Ledkov
@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

[Touch-packages] [Bug 1835660] Re: initramfs unpacking failed

2020-11-16 Thread Ubuntu Foundations Team Bug Bot
** Tags added: patch -- 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

[Touch-packages] [Bug 1835660] Re: initramfs unpacking failed

2020-11-16 Thread Siarhei Liakh
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 Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1835660 Title: initramfs unpacking

[Touch-packages] [Bug 1835660] Re: initramfs unpacking failed

2020-11-16 Thread Siarhei Liakh
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"

Re: [Touch-packages] [Bug 1835660] Re: initramfs unpacking failed

2020-11-06 Thread Tomek
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 :

[Touch-packages] [Bug 1835660] Re: initramfs unpacking failed

2020-11-06 Thread archi02
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 ?

[Touch-packages] [Bug 1835660] Re: initramfs unpacking failed

2020-10-24 Thread Gon Solo
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"); >

[Touch-packages] [Bug 1835660] Re: initramfs unpacking failed

2020-10-21 Thread Tim Wetzel
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

[Touch-packages] [Bug 1835660] Re: initramfs unpacking failed

2020-10-21 Thread ed20900
I'm having this error too. -- 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

[Touch-packages] [Bug 1835660] Re: initramfs unpacking failed

2020-10-14 Thread Matthieu Clemenceau
** Tags added: fr-79 -- 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

[Touch-packages] [Bug 1835660] Re: initramfs unpacking failed

2020-10-12 Thread Rex Tsai
** 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 Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.

[Touch-packages] [Bug 1835660] Re: initramfs unpacking failed

2020-10-02 Thread 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

[Touch-packages] [Bug 1835660] Re: initramfs unpacking failed

2020-09-30 Thread Diego González
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

[Touch-packages] [Bug 1835660] Re: initramfs unpacking failed

2020-09-25 Thread gruberm
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

[Touch-packages] [Bug 1835660] Re: initramfs unpacking failed

2020-09-13 Thread Tony Thuitai
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.

[Touch-packages] [Bug 1835660] Re: initramfs unpacking failed

2020-09-10 Thread ipv
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 Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1835660 Title:

[Touch-packages] [Bug 1835660] Re: initramfs unpacking failed

2020-09-08 Thread martin suc
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 Ubuntu Touch seeded packages,

[Touch-packages] [Bug 1835660] Re: initramfs unpacking failed

2020-08-31 Thread Sujit Kumar
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.

[Touch-packages] [Bug 1835660] Re: initramfs unpacking failed

2020-08-11 Thread danindenver
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

[Touch-packages] [Bug 1835660] Re: initramfs unpacking failed

2020-08-06 Thread Pjotr12345
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

[Touch-packages] [Bug 1835660] Re: initramfs unpacking failed

2020-08-06 Thread gruberm
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

[Touch-packages] [Bug 1835660] Re: initramfs unpacking failed

2020-08-03 Thread Md Ayquassar
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

[Touch-packages] [Bug 1835660] Re: initramfs unpacking failed

2020-07-31 Thread Redsandro
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 Ubuntu Touch seeded

[Touch-packages] [Bug 1835660] Re: initramfs unpacking failed

2020-07-25 Thread TJ
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

[Touch-packages] [Bug 1835660] Re: initramfs unpacking failed

2020-07-24 Thread Davide
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 Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.

[Touch-packages] [Bug 1835660] Re: initramfs unpacking failed

2020-07-16 Thread Edmand Thipursian
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

[Touch-packages] [Bug 1835660] Re: initramfs unpacking failed

2020-07-04 Thread Saroumane
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

[Touch-packages] [Bug 1835660] Re: initramfs unpacking failed

2020-07-03 Thread Con Kolivas
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

[Touch-packages] [Bug 1835660] Re: initramfs unpacking failed

2020-06-18 Thread Stéphane Graber
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

[Touch-packages] [Bug 1835660] Re: initramfs unpacking failed

2020-06-18 Thread ALinuxUser
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

[Touch-packages] [Bug 1835660] Re: initramfs unpacking failed

2020-06-16 Thread Arnold
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

[Touch-packages] [Bug 1835660] Re: initramfs unpacking failed

2020-06-13 Thread Denis
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

[Touch-packages] [Bug 1835660] Re: initramfs unpacking failed

2020-06-10 Thread Rhonal Velasco
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

[Touch-packages] [Bug 1835660] Re: initramfs unpacking failed

2020-05-26 Thread Smittie
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

[Touch-packages] [Bug 1835660] Re: initramfs unpacking failed

2020-05-26 Thread Smittie
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 Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1835660 Title: initramfs unpacking failed

[Touch-packages] [Bug 1835660] Re: initramfs unpacking failed

2020-05-26 Thread Simon Repp
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

[Touch-packages] [Bug 1835660] Re: initramfs unpacking failed

2020-05-25 Thread Simon Repp
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

[Touch-packages] [Bug 1835660] Re: initramfs unpacking failed

2020-05-24 Thread Vitaly Larchenkov
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 Ubuntu Touch seeded

[Touch-packages] [Bug 1835660] Re: initramfs unpacking failed

2020-05-21 Thread Zakhar
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

[Touch-packages] [Bug 1835660] Re: initramfs unpacking failed

2020-05-11 Thread mrazster
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

[Touch-packages] [Bug 1835660] Re: initramfs unpacking failed

2020-05-11 Thread Rui Salvaterra
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 Ubuntu Touch

[Touch-packages] [Bug 1835660] Re: initramfs unpacking failed

2020-05-09 Thread VINAY KUMAR
8 -- 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: Invalid Status in linux

[Touch-packages] [Bug 1835660] Re: initramfs unpacking failed

2020-05-06 Thread Ivan Prokopov
@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 Ubuntu Touch seeded packages,

[Touch-packages] [Bug 1835660] Re: initramfs unpacking failed

2020-05-05 Thread vmc
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 Ubuntu Touch seeded packages, which is subscribed to

[Touch-packages] [Bug 1835660] Re: initramfs unpacking failed

2020-05-05 Thread Ivan Prokopov
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

[Touch-packages] [Bug 1835660] Re: initramfs unpacking failed

2020-04-29 Thread Leon Adato
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 Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1835660 Title: initramfs

[Touch-packages] [Bug 1835660] Re: initramfs unpacking failed

2020-04-29 Thread Leon Adato
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

[Touch-packages] [Bug 1835660] Re: initramfs unpacking failed

2020-04-29 Thread Jatin Sarda
>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

[Touch-packages] [Bug 1835660] Re: initramfs unpacking failed

2020-04-26 Thread Eromatic
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

[Touch-packages] [Bug 1835660] Re: initramfs unpacking failed

2020-04-22 Thread Francis Ginther
** Tags added: id-5e861a6d29650f3423a935c0 -- 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

[Touch-packages] [Bug 1835660] Re: initramfs unpacking failed

2020-04-20 Thread Steve Langasek
> 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 Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.

[Touch-packages] [Bug 1835660] Re: initramfs unpacking failed

2020-04-20 Thread Steve Langasek
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

[Touch-packages] [Bug 1835660] Re: initramfs unpacking failed

2020-04-19 Thread Kred1t
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 Ubuntu Touch seeded packages, which is subscribed to

[Touch-packages] [Bug 1835660] Re: initramfs unpacking failed

2020-04-17 Thread Daniel Silva Capera
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

[Touch-packages] [Bug 1835660] Re: initramfs unpacking failed

2020-04-17 Thread John Gilmore
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

[Touch-packages] [Bug 1835660] Re: initramfs unpacking failed

2020-04-10 Thread vmc
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

[Touch-packages] [Bug 1835660] Re: initramfs unpacking failed

2020-04-10 Thread Daniel Monteiro
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.

[Touch-packages] [Bug 1835660] Re: initramfs unpacking failed

2020-04-06 Thread Dimitri John Ledkov
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

[Touch-packages] [Bug 1835660] Re: initramfs unpacking failed

2020-04-06 Thread Saroumane
I had also the same message in dmesg. (I don't remember when it started) Here : Ubuntu 19.10 booting a manually installed kernel (5.5.2-050502-generic) I followed previous advices : Adding COMPRESS=gzip to /etc/initramfs-tools/initramfs.conf (instead of lz4) then : $ sudo update-grub;sudo

[Touch-packages] [Bug 1835660] Re: initramfs unpacking failed

2020-04-05 Thread Md Ayquassar
After "update-grub; update-initramfs -c -k all; update-grub" and a reboot, the message disappeared on the boot after the reboot. We'll see what happens next. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in

[Touch-packages] [Bug 1835660] Re: initramfs unpacking failed

2020-04-05 Thread Md Ayquassar
Same message for me. The grub menu waits for at least 6 seconds, I think, instead of 0. I won't try anything crazy out before new package version(s) appears, as it is a production system, and I can't repair it in case booting fails. Attachment: the initial part of the dmesg log. ** Attachment

[Touch-packages] [Bug 1835660] Re: initramfs unpacking failed

2020-04-03 Thread Ayyappan
Follow-up on my previous post - Unpacking failed, Decoding failed is back on second boot. Please do not waste your time trying the above. Sorry. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.

[Touch-packages] [Bug 1835660] Re: initramfs unpacking failed

2020-04-03 Thread Ayyappan
Edit initramfs.conf as su. Rem out COMPRESS-lz4 line Run update-initramfs -u - System will return with "COMPRESS parameter not set". Now edit initramfs.conf again. Remove the # on COMPRESS=lz4, run again update-initramfs -u. It will close without any error. Reboot. I just did and no more

[Touch-packages] [Bug 1835660] Re: initramfs unpacking failed

2020-04-02 Thread Brian Murray
** Tags removed: rls-ee-incoming ** Tags added: rls-ff-incoming -- 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

[Touch-packages] [Bug 1835660] Re: initramfs unpacking failed

2020-04-02 Thread Dimitri John Ledkov
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

[Touch-packages] [Bug 1835660] Re: initramfs unpacking failed

2019-07-11 Thread Steve Langasek
Just to confirm, you mean that this message is shown on the otherwise- blank console when booting with 'quiet'? ** Package changed: initramfs-tools (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to

[Touch-packages] [Bug 1835660] Re: initramfs unpacking failed

2019-07-08 Thread Brian Murray
** Tags added: rls-ee-incoming -- 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

[Touch-packages] [Bug 1835660] Re: initramfs unpacking failed

2019-07-08 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: initramfs-tools (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.

[Touch-packages] [Bug 1835660] Re: initramfs unpacking failed

2019-07-07 Thread vmc
** Package changed: ubuntu => initramfs-tools (Ubuntu) -- 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