New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

initrd.img not in gzip format #93

Closed
codygarver opened this Issue Jun 11, 2018 · 6 comments

Comments

Projects
None yet
2 participants
@codygarver
Copy link
Contributor

codygarver commented Jun 11, 2018

Looks like Ubuntu changed something?

P: Begin installing disk information...

gzip: ../../binary/casper/initrd.img-4.15.0-23-generic: not in gzip format
cpio: premature end of archive

@codygarver codygarver added this to the juno-beta1 milestone Jun 11, 2018

@codygarver codygarver self-assigned this Jun 11, 2018

@codygarver

This comment has been minimized.

Copy link
Contributor

codygarver commented Jun 15, 2018

intel-microcode is mutilating initrd.img-* so it doesn't contain conf/uuid.conf that casper needs. Gonna exclude intel-microcode from the live session somehow but preserve it for the installation.

@codygarver

This comment has been minimized.

Copy link
Contributor

codygarver commented Jun 16, 2018

@codygarver codygarver closed this Jun 16, 2018

@opensensesolutions

This comment has been minimized.

Copy link

opensensesolutions commented Jul 27, 2018

I think maybe you ran into the same problem as me after an intel-microcode update, I was just using gunzip to extract it and it always worked but:
"It turns out the initrd generated by Debian's live-build (and to my surprise, accepted by the kernel) is actually the concatenation of two images:"

You can use the method described here to extract it even with the latest intel-microcode packages:
https://unix.stackexchange.com/questions/163346/why-is-it-that-my-initrd-only-has-one-directory-namely-kernel

Supposedly some of the intel-microcode patches are pretty important so you might want to include them when running live.

@codygarver codygarver modified the milestones: juno-beta1, juno-beta2 Jul 31, 2018

@codygarver

This comment has been minimized.

Copy link
Contributor

codygarver commented Jul 31, 2018

The build failure and generic error message returned today. I see there have been changes in different packages that I looked at before to figure out the workaround, so that's where I will start.

@codygarver codygarver reopened this Jul 31, 2018

@codygarver

This comment has been minimized.

Copy link
Contributor

codygarver commented Aug 1, 2018

This was fixed upstream in intel-microcode:

intel-microcode (3.20180425.1~ubuntu0.18.04.2) bionic; urgency=medium

  * Default to early instead of auto, and install all of the microcode,
    not just the one matching the current CPU, if MODULES=most is set
    in the initramfs-tools config (LP: #1778738)

 -- Julian Andres Klode <juliank@ubuntu.com>  Tue, 26 Jun 2018 16:31:30 +0200

No need for workaround disable-intel-microcode anymore so it's been dropped from the iso.

@codygarver codygarver closed this Aug 1, 2018

@codygarver

This comment has been minimized.

Copy link
Contributor

codygarver commented Aug 1, 2018

Or here:

live-build (3.0~a57-1ubuntu34.1) bionic; urgency=medium
  * ubuntu-initramfs-handling.patch: Use initramfs-tools to work with initrds,
    instead of trying to naively repack and unpack them blindly (LP: #1778811)
  * debian/control: Need to depend on initramfs-tools which isn't in chroots.
 -- Adam Conrad <adconrad@ubuntu.com>  Tue, 26 Jun 2018 16:36:32 -0600
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment