https://bugzilla.novell.com/show_bug.cgi?id=779534 https://bugzilla.novell.com/show_bug.cgi?id=779534#c31 --- Comment #31 from Erik Sorenson <sorenson2743@amtelecom.net> 2013-01-06 20:36:39 UTC --- Andrey, it's not clear what you want me to do after I add the new rep and update grub2. I have done the update to my production 12.2 system without problem. I even ran your script and got the same results which is not surprising since I don't think it uses any grub2 functions. So, the question is, what now? If it is meant to be applied to the M2 test partition, that's slightly problematic, since it doesn't have a loader, which I can quickly fix and boot into the minimal-X install for firstboot routine. But then what? I was always able to work around the bug by rebooting after the error message and using a live DVD to issue in a super-terminal: 1. mount /dev/sda5 /mnt 2. grub2-install --force --root-directory=/mnt /dev/sda5 Which worked. So how will I be able to test if the revised grub2 from the new repo is solving the install's bootloader problem? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.