Bug#650415: Please check the grub.cfg for syntax changes on upgrade

[Goswin von Brederlow]

On Sat, Dec 29, 2012 at 11:12:22PM +0000, Martin Naughton wrote:
> Hello Goswin,
>                     What is the exact problem? Grub should be backward
> compatible with this syntax based on my configuration and i am using grub
> 1.99
> 
> In my menu entry i have without any root in the syntax.
> search --no-floppy --fs-uuid --set 2f31d97b-c633-4c76-9e3a-a50ab3f76e41
> 
> my whole example
> menuentry 'Debian GNU/Linux, with Linux 2.6.32-5-686' --class debian
> --class gnu-linux --class gnu --class os {
>         insmod part_msdos
>         insmod ext2
>         set root='(hd0,msdos1)'
>         search --no-floppy --fs-uuid --set
> 2f31d97b-c633-4c76-9e3a-a50ab3f76e41
>         echo    'Loading Linux 2.6.32-5-686 ...'
>         linux   /boot/vmlinuz-2.6.32-5-686
> root=UUID=2f31d97b-c633-4c76-9e3a-a50ab3f76e41 ro  quiet
>         echo    'Loading initial ramdisk ...'
>         initrd  /boot/initrd.img-2.6.32-5-686
> 
> 
> can you please explain more or can we close the bug?
> 
> -- 
> Regards
> Martin Naughton

The problem was that the system no longer booted untill I changed
my custom entries to use the same syntax as the generated ones.
After I changed --set=root and insmod mdraid09 the system booted again.

Maybe changing the module name for mdraid is sufficient. I can't remember
if I thried just changing one of the two things. The change in the mdraid
modules name though is certain to cause boot failures.

In case it matters my system has only lvm on raid with /usr a seperate
partition and /boot on /.

MfG
	Goswin