After a zypper up this am, I lost grub. Saw dracut message that zypper didn’t have enough space to delete grub files after update. Upon reboot, no grub, goes only to windows. Hence, I am now on windows.
I have only 100mb EFI boot partition. Inherited from long ago. Ran live gparted that showed 37mb used of the 100mb so there is space.
Question 1. How can I recover grub EFI boot partition w/o corrupting windows? Perhaps, I can reinstall grub. I need detailed instructions.
Question 2. The EFI boot partition is surrounded by small windows partitions. One side is 450 mb windows recovery partition that has 306mb used of the 450mb. On other side is small 16mb windows micro reserve partition. I will try to find if the windows recovery part can be downsized w/o corrupting windows from window blogs. fI someone knows about this let me know.
My plan would be to get grub running to get into linux. Then try to resize windows recovery partition to 250mb. Any advice would be appreciated?
COMPUTER: windows10, opensuse 15.2, dual boot. no secure boot enabled in bios, windows, or opensuse.
From leap15.2 dvd rescue mode:
fdisk -l (had to hand copy on paper and retype so couldn’t paste into code block)
"partition 1-4 all say in red, Does not start on partition boundary. This is not new.
disk /dev/loop0: 32mib
disk /dev/loop1: 14.4 mib
disk /dev/loop2: 59.4 mib
disk /dev/loop3: 46.1 mib
disk /dev/loop4: 4.1 mib
disk /dev/loop5: 82 mib
disk /dev/sdc: 596 gib
disk /dev.sdb: 2.7 tib
I recognize none of these /dev/loop partition sizes. Something really screwed up. I have one large hd (3 tb) that has linux and windows and two external drives for backup. Fdisk only found 1 though.
Live dvd Gparted still shows disk partitions as before. /root 100gig, /home about 2 terra and swap and efi boot 100mib. Windows about 980 gb
I can’t print gparted partition diagram. Perhaps I could photo it and put it up from windows. Let me know if needed.
One more, hopefully last, question. From your command list above, should I cd to /mnt after mounting root partition to /mnt. Then run all the mount --bind commands and remainder including grub2-install from inside mnt. Or should I stay in root directory and run the commands from root?
There was an update to “grub2” and to “shim” recently (perhaps 3 days ago). I have not yet installed that on my main desktop, but I have installed it on a couple of other systems where it went fine. But there are bug reports that the new “shim” does not work with some BIOS. It’s possible that you ran into this problem.
The way that you reinstalled grub2 does not use “shim”, but it is likely that it did use “shim” at the time it broke. The output that I requested will tell me whether you were using “shim”.
And I guess that I should now try updating “shim” on my main desktop to see if it breaks.
Looked at update history file in yast software management. Last update on 4/23 showed that 3 grub2 files successfully installed (they are checked as installed) plus about 20 others. I think my manual installof grub2 from rescue does not show up there.
Still does not tell me what happened to lose grub or whether to continue with zypper up.
zypper has 50+ updates and a systemd file that needs a reboot awaiting. I did not do it yet pending any advice.