Apparently the way is to re-install the boot loader using grub2-mkconfig -o /boot/grub2/grub.cfg, or is it safer to use the “Boot Linux System” option from the install disk?
Probably I can start W10 from the “boot from installed system” install disk option or from UEFI, but I don’t want to mess the W10 install as it has activated paid-for software, and recovering the activation form the vendors is a PITA. It seems that some vendors think that hard drives never fail, motherboards never break, etc.
I don’t think there was anything that should cause this problem.
On my system, “grub.cfg” was updated. I think that’s related to the ucode update, and the rebuilding of the “initrd”. But “grub” was not reinstalled. So it should still be able to read and display its menu.
However, this could be a delayed effect from an earlier grub update. I don’t think that happens on a UEFI system. But on a legacy system, if the installed grub boot code is relying on block lists to access “core.img”, that can still work if “core.img” is removed, but can later fail when the disk sectors are re-used for something else.
In any case, you will probably need to boot into rescue mode, and reinstall grub. Ask if you need more details.
I thought I could use the instructions below from item 16.3.1 of the guide, but it refers to MBR only, and the disk is GPT, so it doesn’t apply, right?
Alternatively, you can use the Rescue System to fix the boot loader as follows. Boot your machine from the installation media. In the boot screen, choose More › Boot Linux System. Select the disk containing the installed system and kernel with the default kernel options.
When the system is booted, start YaST and switch to System › Boot Loader. Make sure that the Write generic Boot Code to** MRB** option is enabled, and press OK. This fixes the corrupted boot loader by overwriting it, or installs the boot loader if it's missing.
Could I try to boot the installed LEAP (from the install disk) and just rewrite the boot loader from Yast, if at all possible (it doesn’t seem to have this option)?
The “Boot from Linux” install disk option didn’t work, the screen got garbled and it kept beeping each 60 seconds or so.
I did boot to windows from the UEFI menu and deactivated the online licenses of certain applications, but of course I want to preserve W10 installation since reactivating it is probably a PITA - When I changed W10 from a VM to this desktop, the reactivation process by phone was awful, I had to type a gazillion codes to reactivate. And now I’m waiting for it to download a few GB of updates. Ah, the joys of windows…
I don’t think there’s anything wrong with the disk, but I could run a fs check from partition magic livecd. I’m not sure about btrfs, thou.
If I reinstall I can keep home but all my installed software in /, including updates, will be lost, right? Or if I don’t format the partition the installer smart enough to keep what is already there? I think not, because of the updated kernel.
It looks as if Leap 15.0 release date will be late May.
You can probably upgrade now to the beta. It is working pretty well, and the packman repo is already available. After that, just use “zypper dup” to keep it up-to-date until the official release, and “zypper up” after that.
Ah, made a little change in kernel parameters (console resolution) and rebooted, now the boot menu has a Windows boot manager entry.
It boot OK to W10 - by the way, what’s the problem with it, that as soon as it boot it starts hogging my bandwidth, downloading hundreds of MBytes, this after being updated only a few days ago? Really, MS? And windows update status say it is updated…
Edit: it might be MSOffice 2016 updating, I rebooted before checking that.
Anyway: booted back to LEAP, everything seems OK. Some packages from non standard repos (like wolfi’s sysinfo) need to be reinstalled. Curiously, wallpaperswitcher is working OOTB.
Now for updates and check root free space, in case previous btrf snapshots were not removed.