I upgraded to 6.10 two days ago from 6.06. My newly installed kernel is 2.6.17-10.
My grub menu.lst also was translated incorrectly, leaving me with a non- booting machine. It drops me in a busybox prompt. The error was resolved by replacing the root=UUID-not-very-human- readable-string with root=/dev/hda7. FSTAB: cat /etc/fstab # /etc/fstab: static file system information. # # <file system> <mount point> <type> <options> <dump> <pass> proc /proc proc defaults 0 0 # /dev/hda7 -- converted during upgrade to edgy UUID=8ab6cfdb-6149-4b97-89ac-42e91681f91d / reiserfs defaults 0 1 # /dev/hda1 -- converted during upgrade to edgy UUID=1bf33064-2774-4739-93ce-53728123ed7d /boot ext2 defaults 0 2 # /dev/hda6 -- converted during upgrade to edgy UUID=dae1d23a-97b0-4372-8880-c10959f27fe9 /data reiserfs defaults 0 1 # /dev/hda5 -- converted during upgrade to edgy UUID=a63febd0-537a-4471-a697-a4329ece9dea none swap sw 0 0 /dev/hdc /media/dvd udf,iso9660 ro,user,noauto 0 0 /dev/hdd /media/cdrom udf,iso9660 ro,user,noauto 0 0 /dev/fd0 /media/floppy auto rw,user,noauto 0 0 /dev/casio /media/casio vfat rw,user,noauto 0 0 /dev/hp618 /media/hp618 vfat rw,user,noauto 0 0 /dev/olympus /media/olympus vfat rw,user,noauto 0 0 none /proc/bus/usb usbfs defaults 0 0 MENU.LST title Ubuntu, kernel 2.6.17-10-386 root (hd0,0) #kernel /vmlinuz-2.6.17-10-386 root=UUID=a63febd0-537a-4471-a697-a4329ece9dea ro quiet splash kernel /vmlinuz-2.6.17-10.386 root=/dev/hda7 ro quiet splash initrd /initrd.img-2.6.17-10-386 savedefault boot FDISK sudo fdisk -l /dev/hda Disk /dev/hda: 120.0 GB, 120034123776 bytes 255 heads, 63 sectors/track, 14593 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/hda1 * 1 3 24066 83 Linux /dev/hda2 4 14594 117196695+ f W95 Ext'd (LBA) /dev/hda5 4 88 682731 82 Linux swap / Solaris /dev/hda6 1277 14594 106971322+ 83 Linux /dev/hda7 89 1276 9542578+ 83 Linux Partition table entries are not in disk order This is a problem that started in 6.06 and has been carried over into 6.10. And it's probably my fault for having partitions in a wierd order? Shout if I can tell more... -- [Edgy] Wrong boot disk parameter since 2.6.17-7 https://launchpad.net/bugs/61578 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
