Public bug reported:
Binary package hint: lilo
I just updated an x86-64 system from gutsy to hardy, and the boot of
2.6.24-16-generic hung after the line
checking if image is initramfs...it isn't (bad gzip magic numbers);
looks like an initrd
I was able to boot successfully with the old 2.6.22-14-generic
kernel/initramfs left over from the gutsy install. I checked the
2.6.24-16-generic initramfs and gzip was happy with it (and it looked
like a valid cpio archive after I tested uncompressing it).
My system is using LVM on software RAID-1 and using lilo (version
1:22.8-3.1ubuntu1 is installed) as a bootloader. So either lilo is
loading the wrong data into memory or the kernel has a bug in
recognizing the initramfs. Given that almost everyone uses initramfs
now, while grub has largely replaced lilo, a lilo bug seems more likely
to me.
Based on <http://lkml.org/lkml/2006/9/24/50> I made the wild guess that
I was hitting some lilo size limit -- and indeed, the 2.6.24 stuff is
slightly bigger than the 2.6.22 stuff:
1743752 vmlinuz-2.6.22-14-generic
1887736 vmlinuz-2.6.24-16-generic
and
8450482 initrd.img-2.6.22-14-generic
8871664 initrd.img-2.6.24-16-generic
regenerating the 2.6.24-16-generic initramfs with update-initramfs
didn't help. However, I tried installing yaird and built a smaller
initramfs:
2287987 initrd.img-2.6.24-16-generic
and now I am able to boot into 2.6.24-16-generic with the same
lilo/kernel.
** Affects: lilo (Ubuntu)
Importance: Undecided
Status: New
--
lilo loads wrong data for big initramfs (?)
https://bugs.launchpad.net/bugs/221664
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
