lilo loads wrong data for big initramfs (?)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
lilo (Debian) |
Fix Released
|
Unknown
|
|||
lilo (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Hardy |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
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://
1743752 vmlinuz-
1887736 vmlinuz-
and
8450482 initrd.
8871664 initrd.
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.
and now I am able to boot into 2.6.24-16-generic with the same lilo/kernel.
Changed in lilo: | |
status: | Unknown → Fix Released |
Changed in lilo: | |
status: | Fix Released → New |
Changed in lilo: | |
status: | New → Fix Released |
Roland wrote:
> I tried installing yaird and build a smaller initramfs [...] and now I am able to boot
Thank you, I am now able to boot too. Has anyone tried to use the
Some details for those using this on a -server kernel: my `uname -r` returns a -generic suffix; you'll have to symlink /boot/config- *-server and /lib/modules/ *-server. The error message was less than obvious: "unknown kernel version".
This is but an ugly workaround. I wonder if lilo's option to load the initrd into high-memory would suffice.