I can confirm this on my jaunty to karmic upgrade as well. I did a network upgrade of a clean jaunty base (ssh only) installation. I'm getting the same error booting from a valid mirror set via the chainload option recommended here:
http://www.ubuntu-inside.me/2009/06/howto-upgrade-to-grub2-on-ubuntu- jaunty.html I'm also seeing a ", bss=0x0" entry being output before the Starting... message. Its also odd but fdisk is complaining that neither device has a valid partition table. Related? Not sure how you get to that state or if it's related to me using Rieser on that system, but things boot OK. r...@alphamail:~# fdisk -l Disk /dev/sda: 40.0 GB, 40020664320 bytes 255 heads, 63 sectors/track, 4865 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x000bae9f Device Boot Start End Blocks Id System /dev/sda1 * 1 4741 38082051 fd Linux raid autodetect /dev/sda2 4742 4865 996030 fd Linux raid autodetect Disk /dev/sdb: 40.0 GB, 40020664320 bytes 255 heads, 63 sectors/track, 4865 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x000954d1 Device Boot Start End Blocks Id System /dev/sdb1 * 1 4741 38082051 fd Linux raid autodetect /dev/sdb2 4742 4865 996030 fd Linux raid autodetect Disk /dev/md1: 1019 MB, 1019805696 bytes 2 heads, 4 sectors/track, 248976 cylinders Units = cylinders of 8 * 512 = 4096 bytes Disk identifier: 0x00000000 Disk /dev/md1 doesn't contain a valid partition table Disk /dev/md0: 39.0 GB, 38995951616 bytes 2 heads, 4 sectors/track, 9520496 cylinders Units = cylinders of 8 * 512 = 4096 bytes Disk identifier: 0x00000000 Disk /dev/md0 doesn't contain a valid partition table -- grub2 shows 'biosdisk read error', then boots https://bugs.launchpad.net/bugs/396564 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
