I attempted to fix the situation with sudo apt-get install linux-image-2.6.31-21-generic --reinstall
and voila, Ubuntu doesn't boot at all. I get the Windows bootloader, select Ubuntu (remember, this is a Wubi system), then Grub2 beeps about weird errors and gives me a shell. The shell has (hd0,1)/ubuntu/disks/root.disk mounted on (loop0), and I can do things like ls /boot/grub, cat /boot/grub/grub.cfg (full of binary garbage!), and even boot the OS by typing fun-and-user-friendly- commands like linux /boot/vmlinuz-2.6.31-19-generic root=/dev/sda1 loop=/ubuntu/disks/root.disk ro initrd /boot/initrd-2.6.31-19-generic boot If I try -21-generic instead of -19-generic, Linux fails to boot (after complaining that initrd could not be uncompressed and then failing to mount the root filesystem and panicking). If I boot from a LiveCD, mount the NTFS filesystem, then loop-mount /media/disk/ubuntu/disks/root.disk, I can look at /boot/grub/grub.cfg (it looks fine, no binary garbage in sight) or unpack the initrd with cd /tmp; zcat /boot/initrd-2.6.31-21-generic|cpio -i (again, no errors). Could it be that grub2's ext4 support is buggy? I now think that the original bug (post-inst looping forever) is not the cause of my sister's boot problems, and will file a new bug. -- post-inst script loops forever, repeatedly finding the same kernel image https://bugs.launchpad.net/bugs/549691 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
