I have a multiboot EFI system with OpenSuSE Leap 15.4 as default OS. Windows11 is on it too and so is Mint. After wanting Windows11 to update, which always requires a number of reboots (so I must be present to choouse Windows11 after each reboot), after two or three reboots, the system suddenly came up with a grub2 error:
error: …/…/grub-core/fs/fshelp.c:258:file ‘/boot/grub2/x86_64-efi/normal.mod’ not found.
Trying to install the newer OpenSuSE Leap 15.5 was no help.
I also tried to use the well-known things like using the OpenSuSE rescue system. But even after mounting /boot/efi and using the command shim-install --config-file=/boot/grub2/grub.cfg, the error appeared to be persistent.
Show output of
efibootmgr -v
BootCurrent: 000A
Timeout: 2 seconds
BootOrder: 000A,0003,0000,0004,0014,0015,0002,0005,0001
Boot0000* opensuse HD(1,GPT,ea8276df-7b21-40ee-8432-0f1d8b530e88,0x800,0x32000)/File(\EFI\OPENSUSE\GRUBX64.EFI)
Boot0001 Hard Drive BBS(HD,0x0)/VenHw(5ce8128b-2cec-40f0-8372-80640e3dc858,0200)…GO…NO…S.a.m.s.u.n.g. .S.S.D. .9.8.0. .P.R.O. .1.T.B….,.@.r.d.=.X…A…%8…4…Gd-.;.A…MQ…L.S.5.G.X.N.X.0.R.8.1.0.4.1.4.M…BO…NO…C.T.5.0.0.M.X.5.0.0.S.S.D.1….,.@.r.d.=.X…A…>…Gd-.;.A…MQ…L.9.1.7.0.1.E.9.E.D.D.A.0. . . . . . . . …BO
Boot0002* opensuse-secureboot HD(8,GPT,eec766c5-cf2c-4ced-881a-7a80d3d8095e,0x3483a800,0xa00000)/File(\EFI\OPENSUSE\SHIM.EFI)
Boot0003* Windows Boot Manager HD(1,GPT,ea8276df-7b21-40ee-8432-0f1d8b530e88,0x800,0x32000)/File(\EFI\MICROSOFT\BOOT\BOOTMGFW.EFI)WINDOWS…x…B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}…0…
Boot0004* Garuda HD(2,GPT,642bb35e-1be3-f54e-b4d0-8c4c07352b75,0x33450800,0x2710000)/File(\EFI\GARUDA\GRUBX64.EFI)
Boot0005 CD/DVD Drive BBS(CDROM,0x0)/VenHw(5ce8128b-2cec-40f0-8372-80640e3dc858,0300)…GO…NO…T.S.S.T.c.o.r.p. .C.D.D.V.D.W. .S.H.-.S.2.2.3.C….,.@.r.d.=.X…A…>…Gd-.;.A…MQ…L. . . . . . . . . . . . .P. . .U. . . . …BO
Boot000A* ubuntu HD(1,GPT,ea8276df-7b21-40ee-8432-0f1d8b530e88,0x800,0x32000)/File(\EFI\UBUNTU\SHIMX64.EFI)
Boot0014* UEFI OS HD(2,GPT,642bb35e-1be3-f54e-b4d0-8c4c07352b75,0x33450800,0x2710000)/File(\EFI\BOOT\BOOTX64.EFI)…BO
Boot0015* opensuse HD(8,GPT,eec766c5-cf2c-4ced-881a-7a80d3d8095e,0x3483a800,0xa00000)/File(\EFI\OPENSUSE\GRUBX64.EFI)…BO
/home/vaessen $
You have a lot of boot entries and openSUSE is not even the default one. So describe in details what you do when you see this error.
And post computer text as preformatted otherwise it is hard to read.
It is exactly this:
Indeed OpenSuSE is not the default OS because, if it were, I would end up with the afore mentioned error about normal.dot not being found. This file, however, exists in the root system of OpenSuSE and that is what makes the error message so peculiar.
In the UEFI/BIOS, I made Ubuntu the default boot OS, because when doing so I will get into the grub boot menu set up by Ubuntu and that will let me, if I want, choose OpenSuSE (or Windows11, or Ubuntu itself).
The question is why the problem suddenly happened after a few reboots when updating Windows11.
What is also peculiar is that when this error messages comes, preceded by the eye pleasing message ‘Welcome to GRUB!’, I find out that normal commands like ‘help’ or ‘?’ have no meaning at all. The response is ‘Unknown command’.
I however find out that ‘ls’ works and gives a list of volumes and partitions.
When then I try to the find out the details of a certain partition by typing 'ls (hd2,gpt4), the response is that it is a ext2 Filesystem.
Yes.
Ext2.
I am quite sure that since a few years I formatted it as ext4.
When was this software updated for the last time?
When I do that from grub prompt from a normally working TW Grub menu, it reports for my EXT2:
Partition hd1,gpt3: Filesystem type ext* - Label....
When Grub’s EXT2 filesystem driver was created, EXT3 & EXT4 didn’t yet exist, so it got the name EXT2, which did. EXT4 evolved from EXT2, and so did the Grub driver, but it didn’t get a name change, since it works with any of EXTx.
Which openSUSE? You have at least three entries having “opensuse” in their name. Which one has the problem?
Are you using btrfs for root filesystem in openSUSE? Are snapshots enabled?
Thank you for the information.
I found the solution. Once again (it happened before) the Hard Disc Drive priorities in the UEFI BIOS were messed up. Perhaps I should replace the battery on my Z370-A PRO (MS-7B48) motherboard.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.