I have been stucked at this problem about three weeks. I tried to find the reason of how this occured.
I kept the backup of this system in Vmware, this time, I moved the sytem into ext2 partitions instead of LVM plus RAID0 before. And, I have tried reinstall busybox, initramfs-tools, and build a 2.6.24.7 kernel using config file "/boot/config-2.6.24-22-generic" with common building kernel method in linux(make mrproper; make; make modules_install; mkinitramfs -o /boot/initrd.img-2.6.24.7 2.6.24.7, I modified "MODULES" to "list" in config file "/etc/initramfs-tools/initramfs.conf" because the initrd.img file will bigger than 40M if I keep "MODULES=most" in this situation ). But, all of these effort ended up with the same result as my first post above. I noticed, Ubuntu removed kernel 2.6.24-21 from the "dist-upgrade" when they recieved this bug, about three days pasted, the kernel 2.6.24-21-generic appeared in "dist-upgrade" again. And, from this on, I can't reproduced this bug. But, Ubuntu has no any response information with this bug to me, so, I don't know if my problem is caused by my mistake or Ubuntu has fixed something but has not feeded back to me. So, I am still stucking in this problem. I have added some screen snapshots for the boot error messages in VMware. If you have any clue, please let me know. Thanks very much! ** Attachment added: "testub1.JPG" http://launchpadlibrarian.net/20333465/testub1.JPG -- Booting "Segmentation fault" after updating initrd.img-* files for Hardy https://bugs.launchpad.net/bugs/297546 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
