Grub error on Fedora dual boot install

Discussions in English on using Fedora
#1

Good morning,

I just recently switched to Linux, and I already managed to solve most of the small issues I got. However, when I boot my PC (which has dual boot Fedora + Windows) it gives me efidisk:602 error: failure reading sector when I try to boot Fedora, followed by error Linux:208: need to load kernel first.
However, a simple reboot fixes the problem, and then I’m fine until I shutdown the PC.
I tried scanning the disk for errors and they’ve been fixed and to reinstall Grub, but the error is still there.
Is there anything else I could try?

#2

My guess is that your hard disk is failing.
Have you tried reading S.M.A.R.T. data from the affected disk? Gnome Disk can show them, else there is CLI tools

dnf install smartmontools

for more info on S.M.A.R.T on the command line, check out this post Fail to boot a fedora 30 machine - #4 by ferdnyc

2 Likes
#3

Hello, and thanks for the reply. It is a new disk, which should have no issue. I checked smart data, and they seem fine:

=== START OF SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

SMART/Health Information (NVMe Log 0x02)
Critical Warning:                   0x00
Temperature:                        29 Celsius
Available Spare:                    100%
Available Spare Threshold:          10%
Percentage Used:                    0%
Data Units Read:                    228.108 [116 GB]
Data Units Written:                 394.705 [202 GB]
Host Read Commands:                 2.898.900
Host Write Commands:                3.316.926
Controller Busy Time:               51
Power Cycles:                       63
Power On Hours:                     81
Unsafe Shutdowns:                   5
Media and Data Integrity Errors:    0
Error Information Log Entries:      0
Warning  Comp. Temperature Time:    0
Critical Comp. Temperature Time:    0
#4

It seems I solved it with an efi update: in the last 2 days this error didn’t appear. I’ll wait some more days to check if it happens again, and close it and mark as solved.

1 Like
#5

I confirm the EFI update completely solved the issue! The issue can be considered solved

1 Like