after installing lenny or squeeze machines cannot boot, grub2 stops at "Welcome to GRUB2!" message, do a permanent reboot loop or hang when showing the boot menu;
booting from the netinst into rescue mode and tried something but nothing other then deinstalling grub2 and installing grub-legacy helps;
with grub-legacy all machines boot is fine, our systems are inteservers with sh3210-series mainboards and areca or 3ware hardware raid-controllers;
since the option to install grub-legacy on debian lenny is no longer availiable, installing debian 'stable' is no longer possible;
i recommend to bring back the option into the debian-installer that grub-legacy can be installed instead grub2 or completely remove grub2 from lenny because it seems not to be 'stable';

Alexander Jölly wrote:
I wrote instructions here

I haven't used Debian much yet,  I just did a brief install of Lenny a
month ago but I'm guessing I am reporting this in an appropriate way.  I
did a fresh install of the Feb. 16 squeeze CD 1 alongside Windows 2000
on an old Gateway yesterday.  It went into that loop with Welcome to
Grub followed by a reboot and so on and so on.

Then I thought I'd put xubuntu 9.10 on that partition temporarily.  But
xubuntu wanted to install xubuntu beside windows and debian so I let
it.  With this setup I was able to boot into debian as well as windows
and xubuntu.  Something about your grub is wrong.

Hope this helps,

Don Tveter

IMHO these bug reports were made to the version of grub2 currently in
squeeze (and lenny) and should not prevent migration from sid of the new
version 1.98 which is a stable release (while the version in squeeze is a
snapshot).

Please try the new version of grub2 from Sid. Hopefully this will fix the
problem.

Andres

severity 570960 important
tags 570960 moreinfo
thanks
to see your message.

Alexander: could you please retest with grub2 1.98-1, currently in
testing?  If it still doesn't work, then take a backup of
/usr/sbin/grub-install, apply the following patch to
/usr/sbin/grub-install, and re-run grub-install in whatever way is
appropriate for your setup; this should produce enormous amounts of
debugging information, and it would be useful to see the last screenful
or so of it.

=== modified file 'util/grub-install.in'
--- util/grub-install.in	2010-02-03 00:24:07 +0000
+++ util/grub-install.in	2010-05-27 12:30:28 +0000
@@ -326,6 +326,7 @@ if [ "x${devabstraction_module}" = "x" ]
         fi
         echo "search.fs_uuid ${uuid} root " > ${grubdir}/load.cfg
 	echo 'set prefix=($root)'"${relative_grubdir}" >> ${grubdir}/load.cfg
+        echo 'set debug=all' >> ${grubdir}/load.cfg
 	config_opt="-c ${grubdir}/load.cfg "
         modules="$modules search_fs_uuid"
     elif [ "x${grub_drive}" != "x${install_drive}" ] ; then
@@ -336,8 +337,12 @@ if [ "x${devabstraction_module}" = "x" ]
         fi
         echo "search.fs_uuid ${uuid} root " > ${grubdir}/load.cfg
 	echo 'set prefix=($root)'"${relative_grubdir}" >> ${grubdir}/load.cfg
+        echo 'set debug=all' >> ${grubdir}/load.cfg
 	config_opt="-c ${grubdir}/load.cfg "
         modules="$modules search_fs_uuid"
+    else
+        echo 'set debug=all' > ${grubdir}/load.cfg
+        config_opt="-c ${grubdir}/load.cfg "
     fi
 else
     prefix_drive=`$grub_probe --target=drive --device ${grub_device}`

In the meantime, this seems not too widespread, so I'm going to
downgrade this bug from release-critical to important for now, until we
get more information on what's going on.

Thanks,

This sounds a lot like the MBR gap corruption we found with HighPoint
controller. Could you test the latest upstream?

tag 570960 fixed-upstream
thanks
Since no answer to this, I assume, I was right.

Hello Grub,

Can we close this bug since it has been answered?