Three gnu/linux distributions reside on sda.  These are Debian Squeeze (which
installed Grub2), Ubuntu 10.4 and Mepis 8.5.  If I do "update grub" the
terminal output will correctly list these 3 systems.

root@Home03:/home/beejay# update-grub
Generating grub.cfg ...
Found background image: desktop-grub.png
Found linux image: /boot/vmlinuz-2.6.32-5-amd64
Found initrd image: /boot/initrd.img-2.6.32-5-amd64
Found Ubuntu 10.04.1 LTS (10.04) on /dev/sda1
Found MEPIS 8.5 (upgradable from Debian lenny) (8.5) on /dev/sda8
done
root@Home03:/home/beejay#

This apears normal.  However grub.cfg shows:

### BEGIN /etc/grub.d/10_linux ###
menuentry 'Debian GNU/Linux, with Linux 2.6.32-5-amd64' --class debian --class
gnu-linux --class gnu --class os {
        insmod part_msdos
        insmod ext2
        set root='(hd0,msdos2)'
        search --no-floppy --fs-uuid --set aa456124-3b05-43ca-8cbf-a49698adcad7
        echo    'Loading Linux 2.6.32-5-amd64 ...'
        linux   /boot/vmlinuz-2.6.32-5-amd64 root=UUID=aa456124-3b05-43ca-8cbf-
a49698adcad7 ro  quiet
        echo    'Loading initial ramdisk ...'
        initrd  /boot/initrd.img-2.6.32-5-amd64
}
menuentry 'Debian GNU/Linux, with Linux 2.6.32-5-amd64 (recovery mode)' --class
debian --class gnu-linux --class gnu --class os {
        insmod part_msdos
        insmod ext2
        set root='(hd0,msdos2)'
        search --no-floppy --fs-uuid --set aa456124-3b05-43ca-8cbf-a49698adcad7
        echo    'Loading Linux 2.6.32-5-amd64 ...'
        linux   /boot/vmlinuz-2.6.32-5-amd64 root=UUID=aa456124-3b05-43ca-8cbf-
a49698adcad7 ro single
        echo    'Loading initial ramdisk ...'
        initrd  /boot/initrd.img-2.6.32-5-amd64
}
### END /etc/grub.d/10_linux ###

### BEGIN /etc/grub.d/20_linux_xen ###
### END /etc/grub.d/20_linux_xen ###

### BEGIN /etc/grub.d/30_os-prober ###
menuentry "MEPIS at sda1, kernel 2.6.32-25-generic (on /dev/sda1)" {
        insmod part_msdos
        insmod ext2
        set root='(hd0,msdos1)'
        search --no-floppy --fs-uuid --set 35dc10e3-517a-4236-b88e-1a5bcc7ba906
        linux /boot/vmlinuz-2.6.32-25-generic root=/dev/sda1 nomce quiet splash
vga=791
        initrd /boot/initrd.img-2.6.32-25-generic
}
menuentry "MEPIS at sda1, kernel 2.6.32-24-generic (on /dev/sda1)" {
        insmod part_msdos
        insmod ext2
        set root='(hd0,msdos1)'
        search --no-floppy --fs-uuid --set 35dc10e3-517a-4236-b88e-1a5bcc7ba906
        linux /boot/vmlinuz-2.6.32-24-generic root=/dev/sda1 nomce quiet splash
vga=791
        initrd /boot/initrd.img-2.6.32-24-generic
}
menuentry "MEPIS at sda1, kernel 2.6.32-21-generic (on /dev/sda1)" {
        insmod part_msdos
        insmod ext2
        set root='(hd0,msdos1)'
        search --no-floppy --fs-uuid --set 35dc10e3-517a-4236-b88e-1a5bcc7ba906
        linux /boot/vmlinuz-2.6.32-21-generic root=/dev/sda1 nomce quiet splash
vga=791
}
menuentry "MEMTEST (on /dev/sda1)" {
        insmod part_msdos
        insmod ext2
        set root='(hd0,msdos1)'
        search --no-floppy --fs-uuid --set 35dc10e3-517a-4236-b88e-1a5bcc7ba906
        linux /boot/memtest86+.bin
}
menuentry "MEPIS at sda8, newest kernel (on /dev/sda8)" {
        insmod part_msdos
        insmod ext2
        set root='(hd0,msdos8)'
        search --no-floppy --fs-uuid --set 4145682a-88ae-46c6-8f54-ec5361b41ebf
        linux /boot/vmlinuz root=/dev/sda8 nomce quiet splash vga
        initrd /boot/initrd.img
}
menuentry "MEPIS at sda8, kernel 2.6.32-1-mepis-smp (on /dev/sda8)" {
        insmod part_msdos
        insmod ext2
        set root='(hd0,msdos8)'
        search --no-floppy --fs-uuid --set 4145682a-88ae-46c6-8f54-ec5361b41ebf
        linux /boot/vmlinuz-2.6.32-1-mepis-smp root=/dev/sda8 nomce quiet
splash vga
        initrd /boot/initrd.img-2.6.32-1-mepis-smp
}
menuentry "MEMTEST (on /dev/sda8)" {
        insmod part_msdos
        insmod ext2
        set root='(hd0,msdos8)'
        search --no-floppy --fs-uuid --set 4145682a-88ae-46c6-8f54-ec5361b41ebf
        linux /boot/memtest86+.bin
}
### END /etc/grub.d/30_os-prober ###

The error is at

menuentry "MEPIS at sda1, kernel 2.6.32-24-generic (on /dev/sda1)" {
        insmod part_msdos
        insmod ext2
        set root='(hd0,msdos1)'
        search --no-floppy --fs-uuid --set 35dc10e3-517a-4236-b88e-1a5bcc7ba906
        linux /boot/vmlinuz-2.6.32-24-generic root=/dev/sda1 nomce quiet splash
vga=791
        initrd /boot/initrd.img-2.6.32-24-generic
}
menuentry "MEPIS at sda1, kernel 2.6.32-21-generic (on /dev/sda1)" {
        insmod part_msdos
        insmod ext2
        set root='(hd0,msdos1)'
        search --no-floppy --fs-uuid --set 35dc10e3-517a-4236-b88e-1a5bcc7ba906
        linux /boot/vmlinuz-2.6.32-21-generic root=/dev/sda1 nomce quiet splash
vga=791
}
menuentry "MEMTEST (on /dev/sda1)" {
        insmod part_msdos
        insmod ext2
        set root='(hd0,msdos1)'
        search --no-floppy --fs-uuid --set 35dc10e3-517a-4236-b88e-1a5bcc7ba906
        linux /boot/memtest86+.bin

This in fact is Ubuntu 10.4 LTS, installed on sda1.  If I select menu entries
on sda1 (titled "Mepis")  on the Grub menu that is the system that will boot.
The boot instructions are correct, the title is wrong.

I have purged and reinstalled grub2 several times.  The error is persistent.

My Debian squeeze was installed just after the system was declared frozen.
Grub2 worked perfectly until early this week when I did apt-get update && apt-
get dist-upgrade.

Following that upgrade grub2 malfunctioned.

I posted this a few minutes ago on the Debian forum:

As noted above I did post a bug report on the failure of update-grub to
configure the grub menu properly.

I recently tried removing and reinstalling grub2 once again.  (I had done
this several times earlier with no success.)

As I watched the version numbers were the same, 1.98 in both cases, but the
number following the "+" sign was different.

So the new grub2 is 1.98+20100b04-10

Frankly I have no idea what that means. What I do know is that I once again
let grub2 produce yet another grub,cfg and voila! Suddenly I have a properly
listed Grub2 menu! The titles are correct and everything works.

There have been no other changes on my system other than to remove and
reinstall grub2 one more time.

I can only conjecture because I do not know enough to be insightful. I
suspect the dev team working on grub2 has made some subtle changes and those
may have resolved the situation?

Did you receive the project I sent you ?