I also have the same problem on a Packard Bell with Windows Vista, having just installed Ubuntu 10.10
### BEGIN /etc/grub.d/30_os-prober ### menuentry "Windows Vista (loader) (on /dev/sda1)" { insmod part_msdos insmod ntfs set root='(hd0,msdos1)' search --no-floppy --fs-uuid --set 64bce3a1bce36bcc chainloader +1 } menuentry "Windows Recovery Environment (loader) (on /dev/sda2)" { insmod part_msdos insmod ntfs set root='(hd0,msdos2)' search --no-floppy --fs-uuid --set bc3c53c13c5374fc drivemap -s (hd0) ${root} chainloader +1 } ### END /etc/grub.d/30_os-prober ###
In reality, Vista is on sda2, Recovery is on sda1
I also have the same problem on a Packard Bell with Windows Vista, having just installed Ubuntu 10.10
### BEGIN /etc/grub. d/30_os- prober ### d/30_os- prober ###
menuentry "Windows Vista (loader) (on /dev/sda1)" {
insmod part_msdos
insmod ntfs
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set 64bce3a1bce36bcc
chainloader +1
}
menuentry "Windows Recovery Environment (loader) (on /dev/sda2)" {
insmod part_msdos
insmod ntfs
set root='(hd0,msdos2)'
search --no-floppy --fs-uuid --set bc3c53c13c5374fc
drivemap -s (hd0) ${root}
chainloader +1
}
### END /etc/grub.
In reality, Vista is on sda2, Recovery is on sda1