My HP laptop is dual-boot uefi with Windows 10 Pro and Leap 15.1.
Windows has just been installing a big update where it said it would reboot several times to complete it. My GRUB boots into Leap by default. Now all I get on the screen is:
Welcome to GRUB!
error: unknown filesystem.
Entering rescue mode…
grub rescue>
I think Windows is still in the middle of installing its’ updates.
Does anyone know how I should go about repairing GRUB?
Normally we’d say boot your installation media, choose “More”, then choose “Boot Linux System”, from which you could go into the YaST Bootloader module to cause an update. However, that method is broken, tracked in bug 1146017.
To figure out what to do, instead on that screen, choose “Rescue System”. That will start a text mode session. Please use that to run bootinfoscript, and upload its output to https://susepaste.org/ so we can examine the state of the boot and partition configuration and subsequently provide steps to repair. Ultimately, a chroot into the installed system will be used to make the needed repair. This you may be able to get through with no further help via https://forums.opensuse.org/showthread.php/534275-How-to-reinstall-grub2-efi-bootloader instead of first running and sharing bootinfoscript output.
If something similar happened here, I would hit F12 during boot to get the firmware (BIOS) boot menu, and boot into Windows. That would be to allow Windows to complete its updates. And I would hope that fixed the problem, though I’m not at all sure that it would.
Yes, it’s an inconsistent mess out there.
Thanks nickert, I hit F9 for the boot menu and selected OS Boot Manager. It then booted into Windows and finished the update. But as you suspected, that didn’t fix GRUB, which I still have to do. The GRUB error message is the same as before.
Thanks nrickert, I hit F9 for the boot menu and selected OS Boot Manager. Windows booted and finished installing the update. But as you suspected, that didn’t fix GRUB, which still has the same error message.
Thanks mrmazda, I’ll have a go at that as it may also help others.
I tried running ‘bootinfoscript’ from the rescue shell, but it didn’t recognise the command, and I can’t see anything in /bin or /sbin which looks like it?
By the way, I found out my laptop is actually running Leap 15.0, not Leap 15.1 as I had thought.
I misremembered, thought it was in standard repos, and installed by default. It’s an information gathering script](https://github.com/arvidjaar/bootinfoscript) that needs to be downloaded.
Just type “grub error: unknown filesystem” into your preferred search engine. There are vids availible on how to fix this. It’s real simple.
I went through this last week after Windows 1903 update. MS startet to mess up grub again since 1806 update sigh.
Thanks, I may well do that, but I thought I’d check out bootinfoscript as well anyway to see what the problem is.
I’ve got an output file to bootinfoscript now, but I keep getting a 404 error when I try to use susepaste.
Sometimes the site breaks WRT uploads from the susepaste command, but the web site https://susepaste.org will continue to work. Both happened to me just minutes ago. Simply waiting a while and trying again can work sometimes.
Annoyingly I still can’t get susepaste to work. Maybe it’s because I have a VPN and WebRTC disabled, I don’t know.
Strangely enough I’ve got GRUB working again. My UEFI BIOS was set to a custom boot file, which I changed to ‘OS Boot Manager’, and hey presto GRUB is up and working again for dual boot. I don’t really understand why. In my original install I did end up with two boot partitions by mistake, so that may have something to do with it. But the fact remains that Windows screwed up the original bootloader with its update.
It seems to be broken. I’ve filed a ticket about it.
I checked https://susepaste.org a few hours ago and it was working normally, so if you can use that for your bootinfoscript output we may be able to tell why your trouble occurred, and perhaps recommend steps to avoid it reoccurring.