There are *plenty* of posts on the internet asking what to do when grub-probe hangs apparently indefinitely.
I ran into the same problem. Running a second instance of the hanging grub with the -v option showed it hanging after printing "info: adding \hd1' -> '/dev/sdb' from device.map", instead of proceeding to the next drive. The interesting thing now is that hd0 and hd2 were zeroed by dd from /dev/zero. hd1 contained a formatted drive I just bought used (probably formatted by Windows). When accidentally booted from that drive, it showed a German error message about not finding boot partition. The command the hanging grub-probe was started with (according to ps): grub-probe --device-map=/mnt/boot/grub/boot/grub/device.map -t drive -d /dev/sde This hang happened after I tried to make that fscking grub on /dev/sde boot by grub-install --root-directory=/mnt/boot/grub /dev/sde After finding out what hanged when grub-install was invoked, I decided to zero sdb and sdd (which contained some crap data) with dd and investigate what is going on. Now the funny thing is that the hang stopped *just* *after* dd finished zeroing the drives!!! Might give a hint what is wrong with grub-probe. Maybe there is some stupid infinite loop reading the GPT tables at the beginning and the end of the drive again and again until they are in a state grub-probe understands? Maybe this information can help you to fix bug #41288, too? (Now grubinstall is complaining that it cannot read the stage1 file. I know why I never liked GRUB. It just sucks balls to have to waste so much time making it work.) _______________________________________________ Bug-grub mailing list [email protected] https://lists.gnu.org/mailman/listinfo/bug-grub
