recently i installed tumbleweed in dualboot with windows onto extended partition. bootloader installed on / partition. added entry in windows bootloader and when selected(good call, otherwise i wouldn’t boot), this invoked grub from / partition and this setup worked fine for a short time.
next time i booted up and something broke and i got only to “GRUB _” hang and only thing i could do was hard shutdown.
i could boot with install image on flashdisk with option “boot to linux system”, i tried grub2-install /dev/"(name of the partition / )" --force (because block stuff…) but no change, exactly same problem.
i have linux swap partition on same extended partion, so i resized it and made separate /boot partition, pointed yast gui bootloader configurator to it, pointed windows bootloader to it and reboted, hooray, it worked.
then i rebooted again and same “GRUB _” hanging there… i have no idea whats the problem and how to solve it, grub2-install is useless, yast bootloader gui same. i tried grub2-emu and got nothing helpful. any ideas where the problem might be or how to solve it?
Looks like MBR boot you need to set the boot flag to 5 now it is set to Windows ie 4 and you should have installed grub there also. It is best to leave MBR to generic code or just Windows
thanks for reply, but no. boot flag is on sda1, and boot to windows (sda2) works fine. I added entry in windows bootloader with bcdedit to point to sda7 (/boot) and the grub is loaded, up to a point when “GRUB _” hangs on screen and nothing happens until i do hard shutdown/restart.
Where did you install grub?? I don’t trust bcdedit much particularly when second OS lives in an extended. Windows never really supported that. Normal install should put grub on extended and normally you boot to grub which will chain to Windows. (assuming fast boot is off).
ok, i take the “no trouble” part back. after zypper dup on another system(3 primary partitions windows bootloader, windows, linux) it broke there eirther. well that is unfortunate, probably nobody cares since this use-case is probably rather unusual.
so now that it is probable that something broke in recent updates, is there any way to track that down or repair grub? i still can boot (now on both systems) with usb flash using “boot to linux” option, but i would not mind having grub capable of boot.
edit:
sorry for spamming this thread, but i seem to be capable edit post only a short time after posting.
sorry for spamming this thread, but i seem to be capable edit post only a short time after posting.
That is normal about 5 min time out then it goes out to those that subscribe by email
Well since you can get to openSUSE go to Yast boot loader and force a reinstall by making a change (note you can change it back reason is to trick yast to writing the records). Note this will make grub the main boot controller. Note2 be sure to tick scan for foreign OS box in the boot loader screens to include Windows in menu. Also be sure that fast boot is off in Windows or it won’t work.
just to update, boot flag on /boot partition (be it primary or logical) makes grub2 work. so somehow it now breaks when grub2 is initialized(if that is the right verb for it) by windows bootloader, even though it used to work fine, well probably nobody cares about that.
ok, “solution” (seems to work so far, might break after some upgrades or not) - some update(or something else) changed something in the first 512b of /boot partition (or root partition when the /boot is not separated) and same 512 are supposed to be in file linux.bin used by windows. (this is covered in linked guide)