Ubuntu Builder initramfs -u problem

[Bob Bosak]

While in chroot of Ubuntu Builder and you try to update initramfs -u instead of going to the file in boot of the system you are trying to create, it tries to update the hosts which fails. Unless you use automatic creation you won't get iso/casper/initrd.lz if you have installed many programs while in chroot of Ubuntu builder. Just looks as if once you go above 2 gigs for an ISO this program fails every time!

[Francesco Muriana (f-muriana)]

Hello and thanks for your bug report. I cannot reproduce this error, if I type in chroot

`update-initramfs -u`

I get

`update-initramfs: Generating /boot/initrd.img-3.5.0-17-generic`

which is the kernel image of the distro I'm customizing (ubuntu quantal), and the initrd.lz is correctly created in /home/ubuntu-builder/FileSystem/boot.

[Bob Bosak (bbosak2143)]

I am not giving you a line! Am absolutely beyond honest! Sure I only have 6
months experience at linux and is also possible, I am not entering this
command correctly? Is there any kind of forum where others are building and
have some feedback. I only seek to help! I even tried outside of Ubuntu
Builder and had the same result. Is it possible you have to add the kernel
name after update-initramfs -u, such as update-initramfs -u initrd.img
3.5.0-21 generic? Unless I have problems with my version of builder? I
seemed to have misplaced the original deb I downloaded. Is it possible to
find the version number somewhere in the program? There just isn't enough
information on this and want to make sure others don't wind up spending
hours in this!

All started when I issued the command apt-get upgrade. When the kernel
updated I was left with 2 initrd images, one old one new. All commands to
correct this didn't work. I issued the command sudo nautilus outside of
Ubuntu-builder chroot and deleted the old initrd. I also found a package
that installed outside of the system which I also deleted after finding
there were no links in the system. I returned to synaptic manager and
clicked on fix broken links. Went to build and it now produced a booting
ISO but now has other problems. I know a lot about Linux but not everything
or I wouldn't be posting a problem. Instead I would be posting solutions!

On Thu, Jan 3, 2013 at 2:45 AM, Francesco Muriana <
<email address hidden>> wrote:

> Hello and thanks for your bug report. I cannot reproduce this error, if
> I type in chroot
>
> `update-initramfs -u`
>
> I get
>
> `update-initramfs: Generating /boot/initrd.img-3.5.0-17-generic`
>
> which is the kernel image of the distro I'm customizing (ubuntu
> quantal), and the initrd.lz is correctly created in /home/ubuntu-
> builder/FileSystem/boot.
>
> ** Changed in: ubuntu-builder
> Status: New => Incomplete
>
> ** Changed in: ubuntu-builder
> Importance: Undecided => Medium
>
> ** Changed in: ubuntu-builder
> Assignee: (unassigned) => Francesco Muriana (f-muriana)
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1095484
>
> Title:
> Ubuntu Builder initramfs -u problem
>
> Status in Ubuntu Builder:
> Incomplete
>
> Bug description:
> While in chroot of Ubuntu Builder and you try to update initramfs -u
> instead of going to the file in boot of the system you are trying to
> create, it tries to update the hosts which fails. Unless you use
> automatic creation you won't get iso/casper/initrd.lz if you have
> installed many programs while in chroot of Ubuntu builder. Just looks
> as if once you go above 2 gigs for an ISO this program fails every
> time!
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu-builder/+bug/1095484/+subscriptions
>

[Francesco Muriana (f-muriana)]

Well, if you manually deleted the initrd it's possible that you get errors. When you have multiple images, remove the older (from chroot) with
`apt-get remove linux-image-XXXX`
and the initrd will be removed automatically.

You you still have errors, type in chroot
`update-initramfs -u -k all`

[Bob Bosak (bbosak2143)]

Originally apt-get remove linux-image-xxxx but left behind two vmlinuz's
and initrd's. One old, one new of each. When I clicked build no initrd.lz
was created in iso/casper folder. I thank you very very much for that
command! Am going to try it right now! Sites I have been on are just not
clarifying things with it! Just hoping I get this one done as is my first
and might be able to help others that are college students as myself!
Really appreciate all your help and any!!!! Not easy to pick up as much as
I have in just a few weeks! Just tried the command and it still same as
before looks at the hosts first instead of the one you are working on!
Sometime upgrades with Linux are very painful! This time initrd.lz was not
created in iso/casper folder! Very perplexing this problem! I installed 2
gigs worth of programs and now is just nothing! Sure wish there was a
solution for it!? Any links for good information why initrd is created then
is not will be greatly appreciated! Thanks in advance!

On Thu, Jan 3, 2013 at 10:56 AM, Francesco Muriana <
<email address hidden>> wrote:

> Well, if you manually deleted the initrd it's possible that you get
> errors. When you have multiple images, remove the older (from chroot) with
> `apt-get remove linux-image-XXXX`
> and the initrd will be removed automatically.
>
> You you still have errors, type in chroot
> `update-initramfs -u -k all`
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1095484
>
> Title:
> Ubuntu Builder initramfs -u problem
>
> Status in Ubuntu Builder:
> Incomplete
>
> Bug description:
> While in chroot of Ubuntu Builder and you try to update initramfs -u
> instead of going to the file in boot of the system you are trying to
> create, it tries to update the hosts which fails. Unless you use
> automatic creation you won't get iso/casper/initrd.lz if you have
> installed many programs while in chroot of Ubuntu builder. Just looks
> as if once you go above 2 gigs for an ISO this program fails every
> time!
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu-builder/+bug/1095484/+subscriptions
>

[Bob Bosak (bbosak2143)]

I have to apologize for the whole issue! It is all my mistake. I changed
the Ubuntu name which messes everything up. Your program is very good, but
there is no solution for a mistake such as I made. Eventually, when time
permits will try to aid in a solution! Judging by what I have read in
issues, I will bet I am not the only one that has made this foolish mistake.

Once you enter the improper name, the modules get messed up which in turn
with the command update-intramfs then searches for all modules instead of
the module you are trying to update! As I have stated, I only have 8 months
using Linux. I am not expert! I have learned many things but never
everything and will remain that way no matter how far I go!

On Sat, Jan 5, 2013 at 2:23 AM, Francesco Muriana <
<email address hidden>> wrote:

> *** This bug is a duplicate of bug 1080110 ***
> https://bugs.launchpad.net/bugs/1080110
>
> ** This bug has been marked a duplicate of bug 1080110
> when assembling the image ,the md5sum is not registered in the image
> because of this there is an error in the VM
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1095484
>
> Title:
> Ubuntu Builder initramfs -u problem
>
> Status in Ubuntu Builder:
> Incomplete
>
> Bug description:
> While in chroot of Ubuntu Builder and you try to update initramfs -u
> instead of going to the file in boot of the system you are trying to
> create, it tries to update the hosts which fails. Unless you use
> automatic creation you won't get iso/casper/initrd.lz if you have
> installed many programs while in chroot of Ubuntu builder. Just looks
> as if once you go above 2 gigs for an ISO this program fails every
> time!
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu-builder/+bug/1095484/+subscriptions
>