lilo won't add the new kernel 2.6.20

Bug #88219 reported by elroger
26
This bug affects 1 person
Affects Status Importance Assigned to Milestone
lilo (Ubuntu)
Invalid
High
Unassigned
Nominated for Feisty by elroger

Bug Description

Hi,
My English is bad so don't blame me for this.
Today, i've tried to upgrade my ubuntu 6.10 edgy to ubuntu 7.04 feisty.
The update can't finish because lilo can't add the kernel 2.6.20 entry.
My root partition is on xfs filesystem, reason i need to use lilo instead of grub.

when i tried sudo lilo
i get :

Added Linux *
Fatal: Empty map section

My upgrade can't finish because of this.

Tags: patch
Revision history for this message
James Troup (elmo) wrote :

I ran into the same problem on a (Intel) Macbook Pro. The problem is because something is leaving 0 byte initrd.img files around in /boot. A trivial work around is to rm or move them out of the way. However this effectively breaks upgrades from Edgy to Feisty on machines that use lilo. Either update-initramfs shouldn't be generating these 0 byte initrd.img files or lilo needs to be fixed to ignore them.

Changed in lilo:
status: Unconfirmed → Confirmed
Revision history for this message
Tollef Fog Heen (tfheen) wrote :

Milestoning for beta.

Revision history for this message
Kyle McMartin (kyle) wrote :

Someone want to give this a test? I don't feel like blowing away my bootsector...

Revision history for this message
Kyle McMartin (kyle) wrote :

The real question here is why are these initramfs not being properly generated in the first place...

Changed in lilo:
assignee: nobody → kyle
importance: Undecided → High
status: Confirmed → Fix Committed
Revision history for this message
James Troup (elmo) wrote :

Sorry, patch doesn't work, warning doesn't trigger, same error. The initramfs's which are zero size are for 2.6.17 - I assume they're like that because of the udev compatability madness

Revision history for this message
Tollef Fog Heen (tfheen) wrote :

Bringing milestone forward.

Revision history for this message
Dejan (dejan-rodiger) wrote :

I just upgraded from 6.10 to 7.04 beta through internet. I had some error's with this packages: initramfs-tools, console-setup, ubuntu-minimal, usplash, kubuntu-artwork-usplash, kubuntu-desktop, linux-image-2.6.20-14-generic, linux-image-generic, linux-restricted-modules-2.6.20-14-generic, linux-restricted-modules-generic, linux-generic, linux-image-2.6.20-13-386
linux-image-2.6.20-14-386, linux-image-386, linux-restricted-modules-2.6.20-13-386, nvidia-glx, usplash-theme-ubuntu, ubuntu-desktop

After I upgraded I tried to reboot. With my 2.6.17 kernel I wasn't able to boot (kernel-panic root something problem).
Then I tried to boot my older kernel 2.6.15-23 and I was able to boot (but because of problems with nvidia, as you see in my packages list, I was not able to boot to into X until I have changed my xorg.conf).

Then I tried to apt-get upgrade rest of the packages, and I was getting errors with initramfs-tools:
Setting up initramfs-tools (0.85g) ...
update-initramfs: Generating /boot/initrd.img-2.6.17-10-386
W: mdadm: unchecked configuration file: /etc/mdadm/mdadm.conf
W: mdadm: please read /usr/share/doc/mdadm/README.upgrading-2.5.3.gz .
W: mdadm: no arrays defined in configuration file.
W: mdadm: falling back to emergency procedure in initramfs.
ERROR lilo fails for new /boot/initrd.img-2.6.17-10-386:

Warning: '/proc/partitions' does not match '/dev' directory structure.
    Name change: '/dev/dm-0' -> '/dev/evms/hda1'
Added Linux *
Fatal: Empty map section

Finally, I think I have problem with both lilo and initramfs-tools.
lilo can't update because initrd.img-2.6.15-23-386 is zero size, but this is the only kernel I can boot.

As you see I tried all versions of initramfs-tools (from 0.69, 0.85e to 0.85g from Debian).

What should I do?

Revision history for this message
Dejan (dejan-rodiger) wrote :

OK. I commented initrd with zero size initrd.img
# initrd=/initrd.img.old
in lilo.conf and everything upgraded. I will have to check if I can boot now.

Revision history for this message
Dejan (dejan-rodiger) wrote :

Not OK.
After reboot, my system doesn't work.

If I boot my new kernel (2.6.20) I end in busybox (initramfs) prompt.
I see this messages:
mount: Mounting /root/dev on /dev/.static/dev failed:No such file or directory
usb 1-1: configuration #1 chosen from 1 choice
Done.
mount: Mounting /sys on /root/sys failed: No such file or directory
mount: Mounting /proc on /root/proc failed: No such file or directory
Traget filesystem doesnt have /sbin/init
Busy Box v1.1.3

and then messages for usb 1-2.

If I boot my old kernel, which was working before, now ends with kernel-panic: unable to mount root or something...

So, where is the problem? Lilo or initramfs-tools?
Maybe here: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/31790

Revision history for this message
Dejan (dejan-rodiger) wrote :

I am able to boot only with instruction to lilo on boot screen: root=/dev/hda1

Kyle McMartin (kyle)
Changed in lilo:
status: Fix Committed → Confirmed
Revision history for this message
Kyle McMartin (kyle) wrote :

Please test with the following patch applied.

Revision history for this message
jscc88 (jscc88-deactivatedaccount) wrote :

you have to download the kernel of www.kernel.org

and you have to get the new stable version

Changed in lilo:
assignee: kyle → sebastiancobaleda
status: Confirmed → Fix Released
Revision history for this message
Julian Alarcon (julian-alarcon) wrote :

The user Juan Sebastian Cobaleda Cano is a troll, or something. We, in the Ubuntu-Co Team are checking all his changes in Launchpad. Sorry for the problems.

Changed in lilo:
assignee: sebastiancobaleda → nobody
status: Fix Released → Confirmed
Revision history for this message
David Stansby (dstansby-deactivatedaccount) wrote :

Please could you see if this is still a problem in a newer version of Ubuntu?

Changed in lilo (Ubuntu):
status: Confirmed → Incomplete
tags: added: patch
Revision history for this message
Dejan (dejan-rodiger) wrote :

I am on Ubuntu 10.04 and everything is fine. I am using grub2 now. Thanks

Revision history for this message
David Stansby (dstansby-deactivatedaccount) wrote :

I think this should be marked as won't fix, but since I can't I'll mark it as invalid for now.

Changed in lilo (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.