https://bugzilla.novell.com/show_bug.cgi?id=850130 https://bugzilla.novell.com/show_bug.cgi?id=850130#c2 --- Comment #2 from Michael Chang <mchang@suse.com> 2013-11-13 12:15:57 UTC --- The grub2-branding-openSUSE looks quite innocent to me. It only touches grub.cfg changes and thus no changes to core.img location in file system. I'm no file system expert, could it be possible that the file blocks been moved silently? Using static blocks for booting is really fragile, we need to track all it's changes and update bootloader's block list, otherwise system wont boot. We'd better create bios boot partition thus offer us space to embed core.img. We can therefore eliminate such errors due to file blocks been relocated. Core.img understands file system thus can handle relocation after all .. Or any one could have idea why the blocks would go wrong .. sadly I have no clue now. :( -- 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.