Grub2 intermittently fails to find boot partition

Ask Fedora
, ,
1

Hello everyone,

Since I installed the latest system updates with some new grub2 packages (2.06-42)
I have the following error at boot:

error: ../../grub-core/net/net.c:1552:disk 'hd0.gpt5' not found.
Press any key to continue...

but after a new reboot, the system starts normally.

The Windows10 installation was also impacted as I needed to reenter the bitlocker recovery key to be able to boot !

here is my partitionning:

fdisk -l
Disk /dev/nvme0n1: 953.87 GiB, 1024209543168 bytes, 2000409264 sectors
Disk model: UMIS RPETJ1T24MGE2QDQ                   
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 882AE118-492A-43D8-BE3C-BA5549923CA6

Device              Start        End    Sectors   Size Type
/dev/nvme0n1p1       2048     534527     532480   260M EFI System
/dev/nvme0n1p2     534528     567295      32768    16M Microsoft reserved
/dev/nvme0n1p3     567296  416229375  415662080 198.2G Microsoft basic data
/dev/nvme0n1p4 1998360576 2000408575    2048000  1000M Windows recovery environm
/dev/nvme0n1p5  416229376  418326527    2097152     1G Linux filesystem
/dev/nvme0n1p6  418326528 1998360575 1580034048 753.4G Linux filesystem

Partition table entries are not in disk order.


Disk /dev/mapper/luks-b119a4d4-9ddf-4929-a9ce-f420371415cd: 753.4 GiB, 808960655360 bytes, 1580001280 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/zram0: 8 GiB, 8589934592 bytes, 2097152 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

And the installed kernel is kernel-5.17.11-300.fc36.x86_64.
I’m also have secure boot activated…

So Is it possible the latest grub2 update has some bugs ?

Thanks for any hint.

Cheers,

Julien.

2

Is there any chance you had a USB stick plugged in on the times it failed? It looks like grub is using hdX instead of UUID, so the disk order that your BIOS picks may affect whether or not grub will grok it that way.

3

Hi Scott,

No, nothing was plugged at that time.
But I will try to understand why grub2 is not using the UUID to identify the partitions.
As I did a fresh F36 install, I guess it’s not the default…

But thanks for the hint.

Julien

4

A quick update here,

I did not rebooted a lot lastly (fearing this error), but it seems to be gone.
I’m not sure what I did for that, probably nothing.

So I’ll mark it as resolved.

Cheers.

1 Like