Bug#487565:

[Felix Zielcke]

Am Montag, den 28.07.2008, 21:03 +0200 schrieb Henry-Nicolas Tourneur:

> Oh, I just mean that the version of this package is the same in sid and
> in testing. I'v installed the package this afternoon and I'm using 1.96
> +20080724-2.

Fine.

> prefix = (hd1,1)(md1)/boot/grub
> root=hd1,1
> 
> The prefix looked strange to me, so I typed :
> set prefix=(md1)/boot/grub
> insmod normal
> normal
> 
> And everything works ok.

The original report was with:

invalid file '(md0)/boot/grub//normal.mod'

Not a double prefix like you have.
And this issue should be solved now, I had once a fd prefix and there it
displayed afair a doubleslash too.
So grub2 is still using it in case prefix doestn't end with / but it now
shouldn't have anymore a problem with //
If a doubleslash is still for anyone a problem then please tell us.

> Off course, such a procedure isn't usefull at every startup but I guess 
> that the problem come from the chainload because the only place where
> I found something about hd1 is menu.lst (and it is hd1,0, not hd1,1, strange).

I thought there were recently another bugreport with such a double
prefix but I can't find it now.
check that /boot/grub/grub.cfg is correctly.

> But as I'm not sure that it come from the chainload I don't want to run upgrade-from-grub-legacy,
> to avoid staying with an unbootable system.

If grub.cfg is right, then this is probable a chainloading problem.
It should work if you use grub2 in the MBR.
In case it's not then you already wrote how to fix this so you can boot
fine.